<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux-stable.git/drivers/net/wireless/ath, branch v4.7</title>
<subtitle>Linux kernel stable tree</subtitle>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux-stable.git/'/>
<entry>
<title>ath9k: fix GPIO mask for AR9462 and AR9565</title>
<updated>2016-06-14T13:21:31+00:00</updated>
<author>
<name>Miaoqing Pan</name>
<email>miaoqing@codeaurora.org</email>
</author>
<published>2016-06-07T12:47:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux-stable.git/commit/?id=e024111f6946f45cf1559a8c6fd48d2d0f696d07'/>
<id>e024111f6946f45cf1559a8c6fd48d2d0f696d07</id>
<content type='text'>
The incorrect GPIO mask cause kernel warning, when AR9462 access GPIO11.
Also fix the mask for AR9565.

WARNING: CPU: 1 PID: 199 at ../drivers/net/wireless/ath/ath9k/hw.c:2778 ath9k_hw_gpio_get+0x1a9/0x1b0 [ath9k_hw]
CPU: 1 PID: 199 Comm: kworker/u16:9 Not tainted 4.7.0-rc1-next-20160530+ #5
Hardware name: Acer TravelMate P243/BA40_HC, BIOS V1.01 04/20/2012
Workqueue: events_power_efficient rfkill_poll
 0000000000000000 ffff88002cf73d28 ffffffff813b8ddc 0000000000000000
 0000000000000000 ffff88002cf73d68 ffffffff8107a331 00000ada00000086
 ffff880148d9c018 000000000000000b ffff880147e68720 0000000000000200
Call Trace:
 [&lt;ffffffff813b8ddc&gt;] dump_stack+0x63/0x87
 [&lt;ffffffff8107a331&gt;] __warn+0xd1/0xf0
 [&lt;ffffffff8107a41d&gt;] warn_slowpath_null+0x1d/0x20
 [&lt;ffffffffc0775b19&gt;] ath9k_hw_gpio_get+0x1a9/0x1b0 [ath9k_hw]
 [&lt;ffffffffc047f3e4&gt;] ath9k_rfkill_poll_state+0x34/0x60 [ath9k]
 [&lt;ffffffffc06dbb53&gt;] ieee80211_rfkill_poll+0x33/0x40 [mac80211]
 [&lt;ffffffffc03ad65a&gt;] cfg80211_rfkill_poll+0x2a/0xc0 [cfg80211]
 [&lt;ffffffff817c5514&gt;] rfkill_poll+0x24/0x50
 [&lt;ffffffff81093183&gt;] process_one_work+0x153/0x3f0
 [&lt;ffffffff8109393b&gt;] worker_thread+0x12b/0x4b0
 [&lt;ffffffff81093810&gt;] ? rescuer_thread+0x340/0x340
 [&lt;ffffffff81099129&gt;] kthread+0xc9/0xe0
 [&lt;ffffffff817d8f1f&gt;] ret_from_fork+0x1f/0x40
 [&lt;ffffffff81099060&gt;] ? kthread_park+0x60/0x60

Fixes: a01ab81b09c5 ("ath9k: define correct GPIO numbers and bits mask")
Reported-by: Sudip Mukherjee &lt;sudip.mukherjee@codethink.co.uk&gt;
Tested-by: Sudip Mukherjee &lt;sudip.mukherjee@codethink.co.uk&gt;
Signed-off-by: Miaoqing Pan &lt;miaoqing@codeaurora.org&gt;
Signed-off-by: Kalle Valo &lt;kvalo@qca.qualcomm.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The incorrect GPIO mask cause kernel warning, when AR9462 access GPIO11.
Also fix the mask for AR9565.

WARNING: CPU: 1 PID: 199 at ../drivers/net/wireless/ath/ath9k/hw.c:2778 ath9k_hw_gpio_get+0x1a9/0x1b0 [ath9k_hw]
CPU: 1 PID: 199 Comm: kworker/u16:9 Not tainted 4.7.0-rc1-next-20160530+ #5
Hardware name: Acer TravelMate P243/BA40_HC, BIOS V1.01 04/20/2012
Workqueue: events_power_efficient rfkill_poll
 0000000000000000 ffff88002cf73d28 ffffffff813b8ddc 0000000000000000
 0000000000000000 ffff88002cf73d68 ffffffff8107a331 00000ada00000086
 ffff880148d9c018 000000000000000b ffff880147e68720 0000000000000200
Call Trace:
 [&lt;ffffffff813b8ddc&gt;] dump_stack+0x63/0x87
 [&lt;ffffffff8107a331&gt;] __warn+0xd1/0xf0
 [&lt;ffffffff8107a41d&gt;] warn_slowpath_null+0x1d/0x20
 [&lt;ffffffffc0775b19&gt;] ath9k_hw_gpio_get+0x1a9/0x1b0 [ath9k_hw]
 [&lt;ffffffffc047f3e4&gt;] ath9k_rfkill_poll_state+0x34/0x60 [ath9k]
 [&lt;ffffffffc06dbb53&gt;] ieee80211_rfkill_poll+0x33/0x40 [mac80211]
 [&lt;ffffffffc03ad65a&gt;] cfg80211_rfkill_poll+0x2a/0xc0 [cfg80211]
 [&lt;ffffffff817c5514&gt;] rfkill_poll+0x24/0x50
 [&lt;ffffffff81093183&gt;] process_one_work+0x153/0x3f0
 [&lt;ffffffff8109393b&gt;] worker_thread+0x12b/0x4b0
 [&lt;ffffffff81093810&gt;] ? rescuer_thread+0x340/0x340
 [&lt;ffffffff81099129&gt;] kthread+0xc9/0xe0
 [&lt;ffffffff817d8f1f&gt;] ret_from_fork+0x1f/0x40
 [&lt;ffffffff81099060&gt;] ? kthread_park+0x60/0x60

Fixes: a01ab81b09c5 ("ath9k: define correct GPIO numbers and bits mask")
Reported-by: Sudip Mukherjee &lt;sudip.mukherjee@codethink.co.uk&gt;
Tested-by: Sudip Mukherjee &lt;sudip.mukherjee@codethink.co.uk&gt;
Signed-off-by: Miaoqing Pan &lt;miaoqing@codeaurora.org&gt;
Signed-off-by: Kalle Valo &lt;kvalo@qca.qualcomm.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ath10k: fix deadlock while processing rx_in_ord_ind</title>
<updated>2016-06-14T12:06:17+00:00</updated>
<author>
<name>Rajkumar Manoharan</name>
<email>rmanohar@qti.qualcomm.com</email>
</author>
<published>2016-06-09T06:03:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux-stable.git/commit/?id=e50525bef593c3dd0564df676c567d77f7c20322'/>
<id>e50525bef593c3dd0564df676c567d77f7c20322</id>
<content type='text'>
commit 5c86d97bcc1d ("ath10k: combine txrx and replenish task")
introduced deadlock while processing rx in order indication message
for qca6174 based devices. While merging replenish and txrx tasklets,
replenish task should be called out of htt rx ring locking since it
is also try to acquire the same lock.

Unfortunately this issue is not exposed by other solutions (qca988x,
qca99x0 &amp; qca4019), as rx_in_ord_ind message is specific to qca6174
based devices. This patch fixes

=============================================
[ INFO: possible recursive locking detected ]
4.7.0-rc2-wt-ath+ #1353 Tainted: G            E
---------------------------------------------
swapper/3/0 is trying to acquire lock:
 (&amp;(&amp;htt-&gt;rx_ring.lock)-&gt;rlock){+.-...}, at: [&lt;f8d7ef19&gt;]
ath10k_htt_rx_msdu_buff_replenish+0x29/0x90 [ath10k_core]

but task is already holding lock:
 (&amp;(&amp;htt-&gt;rx_ring.lock)-&gt;rlock){+.-...}, at: [&lt;f8d82cab&gt;]
ath10k_htt_txrx_compl_task+0x21b/0x250 [ath10k_core]

other info that might help us debug this:
 Possible unsafe locking scenario:

       CPU0
       ----
  lock(&amp;(&amp;htt-&gt;rx_ring.lock)-&gt;rlock);
  lock(&amp;(&amp;htt-&gt;rx_ring.lock)-&gt;rlock);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

1 lock held by swapper/3/0:
 #0:  (&amp;(&amp;htt-&gt;rx_ring.lock)-&gt;rlock){+.-...}, at: [&lt;f8d82cab&gt;]
ath10k_htt_txrx_compl_task+0x21b/0x250 [ath10k_core]

Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=119151
Fixes: 5c86d97bcc1d ("ath10k: combine txrx and replenish task")
Reported-by: Mike Lothian &lt;mike@fireburn.co.uk&gt;
Signed-off-by: Rajkumar Manoharan &lt;rmanohar@qti.qualcomm.com&gt;
Signed-off-by: Kalle Valo &lt;kvalo@qca.qualcomm.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
commit 5c86d97bcc1d ("ath10k: combine txrx and replenish task")
introduced deadlock while processing rx in order indication message
for qca6174 based devices. While merging replenish and txrx tasklets,
replenish task should be called out of htt rx ring locking since it
is also try to acquire the same lock.

Unfortunately this issue is not exposed by other solutions (qca988x,
qca99x0 &amp; qca4019), as rx_in_ord_ind message is specific to qca6174
based devices. This patch fixes

=============================================
[ INFO: possible recursive locking detected ]
4.7.0-rc2-wt-ath+ #1353 Tainted: G            E
---------------------------------------------
swapper/3/0 is trying to acquire lock:
 (&amp;(&amp;htt-&gt;rx_ring.lock)-&gt;rlock){+.-...}, at: [&lt;f8d7ef19&gt;]
ath10k_htt_rx_msdu_buff_replenish+0x29/0x90 [ath10k_core]

but task is already holding lock:
 (&amp;(&amp;htt-&gt;rx_ring.lock)-&gt;rlock){+.-...}, at: [&lt;f8d82cab&gt;]
ath10k_htt_txrx_compl_task+0x21b/0x250 [ath10k_core]

other info that might help us debug this:
 Possible unsafe locking scenario:

       CPU0
       ----
  lock(&amp;(&amp;htt-&gt;rx_ring.lock)-&gt;rlock);
  lock(&amp;(&amp;htt-&gt;rx_ring.lock)-&gt;rlock);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

1 lock held by swapper/3/0:
 #0:  (&amp;(&amp;htt-&gt;rx_ring.lock)-&gt;rlock){+.-...}, at: [&lt;f8d82cab&gt;]
ath10k_htt_txrx_compl_task+0x21b/0x250 [ath10k_core]

Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=119151
Fixes: 5c86d97bcc1d ("ath10k: combine txrx and replenish task")
Reported-by: Mike Lothian &lt;mike@fireburn.co.uk&gt;
Signed-off-by: Rajkumar Manoharan &lt;rmanohar@qti.qualcomm.com&gt;
Signed-off-by: Kalle Valo &lt;kvalo@qca.qualcomm.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ath10k: fix crash related to printing features</title>
<updated>2016-06-07T11:35:55+00:00</updated>
<author>
<name>Ben Greear</name>
<email>greearb@candelatech.com</email>
</author>
<published>2016-06-02T14:59:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux-stable.git/commit/?id=8d0a0710ea0d22881fdb40eb79d346a98cc64ae6'/>
<id>8d0a0710ea0d22881fdb40eb79d346a98cc64ae6</id>
<content type='text'>
This looks like a regression from commit c4cdf753ed42 ("ath10k: move
fw_features to struct ath10k_fw_file"), we were printing the features from a
wrong struct.

Fixes: c4cdf753ed42 ("ath10k: move fw_features to struct ath10k_fw_file")
Signed-off-by:  Ben Greear &lt;greearb@candelatech.com&gt;
[kvalo@qca.qualcomm.com: improve commit log]
Signed-off-by: Kalle Valo &lt;kvalo@qca.qualcomm.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This looks like a regression from commit c4cdf753ed42 ("ath10k: move
fw_features to struct ath10k_fw_file"), we were printing the features from a
wrong struct.

Fixes: c4cdf753ed42 ("ath10k: move fw_features to struct ath10k_fw_file")
Signed-off-by:  Ben Greear &lt;greearb@candelatech.com&gt;
[kvalo@qca.qualcomm.com: improve commit log]
Signed-off-by: Kalle Valo &lt;kvalo@qca.qualcomm.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ath10k: fix deadlock when peer cannot be created</title>
<updated>2016-06-06T17:18:45+00:00</updated>
<author>
<name>Ben Greear</name>
<email>greearb@candelatech.com</email>
</author>
<published>2016-04-01T21:12:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux-stable.git/commit/?id=fee48cf8374569a3888fd8c8536283e6067f0cfb'/>
<id>fee48cf8374569a3888fd8c8536283e6067f0cfb</id>
<content type='text'>
We must not attempt to send WMI packets while holding the data-lock,
as it may deadlock:

BUG: sleeping function called from invalid context at drivers/net/wireless/ath/ath10k/wmi.c:1824
in_atomic(): 1, irqs_disabled(): 0, pid: 2878, name: wpa_supplicant

=============================================
[ INFO: possible recursive locking detected ]
4.4.6+ #21 Tainted: G        W  O
---------------------------------------------
wpa_supplicant/2878 is trying to acquire lock:
 (&amp;(&amp;ar-&gt;data_lock)-&gt;rlock){+.-...}, at: [&lt;ffffffffa0721511&gt;] ath10k_wmi_tx_beacons_iter+0x26/0x11a [ath10k_core]

but task is already holding lock:
 (&amp;(&amp;ar-&gt;data_lock)-&gt;rlock){+.-...}, at: [&lt;ffffffffa070251b&gt;] ath10k_peer_create+0x122/0x1ae [ath10k_core]

other info that might help us debug this:
 Possible unsafe locking scenario:

       CPU0
       ----
  lock(&amp;(&amp;ar-&gt;data_lock)-&gt;rlock);
  lock(&amp;(&amp;ar-&gt;data_lock)-&gt;rlock);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

4 locks held by wpa_supplicant/2878:
 #0:  (rtnl_mutex){+.+.+.}, at: [&lt;ffffffff816493ca&gt;] rtnl_lock+0x12/0x14
 #1:  (&amp;ar-&gt;conf_mutex){+.+.+.}, at: [&lt;ffffffffa0706932&gt;] ath10k_add_interface+0x3b/0xbda [ath10k_core]
 #2:  (&amp;(&amp;ar-&gt;data_lock)-&gt;rlock){+.-...}, at: [&lt;ffffffffa070251b&gt;] ath10k_peer_create+0x122/0x1ae [ath10k_core]
 #3:  (rcu_read_lock){......}, at: [&lt;ffffffffa062f304&gt;] rcu_read_lock+0x0/0x66 [mac80211]

stack backtrace:
CPU: 3 PID: 2878 Comm: wpa_supplicant Tainted: G        W  O    4.4.6+ #21
Hardware name: To be filled by O.E.M. To be filled by O.E.M./ChiefRiver, BIOS 4.6.5 06/07/2013
 0000000000000000 ffff8801fcadf8f0 ffffffff8137086d ffffffff82681720
 ffffffff82681720 ffff8801fcadf9b0 ffffffff8112e3be ffff8801fcadf920
 0000000100000000 ffffffff82681720 ffffffffa0721500 ffff8801fcb8d348
Call Trace:
 [&lt;ffffffff8137086d&gt;] dump_stack+0x81/0xb6
 [&lt;ffffffff8112e3be&gt;] __lock_acquire+0xc5b/0xde7
 [&lt;ffffffffa0721500&gt;] ? ath10k_wmi_tx_beacons_iter+0x15/0x11a [ath10k_core]
 [&lt;ffffffff8112d0d0&gt;] ? mark_lock+0x24/0x201
 [&lt;ffffffff8112e908&gt;] lock_acquire+0x132/0x1cb
 [&lt;ffffffff8112e908&gt;] ? lock_acquire+0x132/0x1cb
 [&lt;ffffffffa0721511&gt;] ? ath10k_wmi_tx_beacons_iter+0x26/0x11a [ath10k_core]
 [&lt;ffffffffa07214eb&gt;] ? ath10k_wmi_cmd_send_nowait+0x1ce/0x1ce [ath10k_core]
 [&lt;ffffffff816f9e2b&gt;] _raw_spin_lock_bh+0x31/0x40
 [&lt;ffffffffa0721511&gt;] ? ath10k_wmi_tx_beacons_iter+0x26/0x11a [ath10k_core]
 [&lt;ffffffffa0721511&gt;] ath10k_wmi_tx_beacons_iter+0x26/0x11a [ath10k_core]
 [&lt;ffffffffa07214eb&gt;] ? ath10k_wmi_cmd_send_nowait+0x1ce/0x1ce [ath10k_core]
 [&lt;ffffffffa062eb18&gt;] __iterate_interfaces+0x9d/0x13d [mac80211]
 [&lt;ffffffffa062f609&gt;] ieee80211_iterate_active_interfaces_atomic+0x32/0x3e [mac80211]
 [&lt;ffffffffa07214eb&gt;] ? ath10k_wmi_cmd_send_nowait+0x1ce/0x1ce [ath10k_core]
 [&lt;ffffffffa071fa9f&gt;] ath10k_wmi_tx_beacons_nowait.isra.13+0x14/0x16 [ath10k_core]
 [&lt;ffffffffa0721676&gt;] ath10k_wmi_cmd_send+0x71/0x242 [ath10k_core]
 [&lt;ffffffffa07023f6&gt;] ath10k_wmi_peer_delete+0x3f/0x42 [ath10k_core]
 [&lt;ffffffffa0702557&gt;] ath10k_peer_create+0x15e/0x1ae [ath10k_core]
 [&lt;ffffffffa0707004&gt;] ath10k_add_interface+0x70d/0xbda [ath10k_core]
 [&lt;ffffffffa05fffcc&gt;] drv_add_interface+0x123/0x1a5 [mac80211]
 [&lt;ffffffffa061554b&gt;] ieee80211_do_open+0x351/0x667 [mac80211]
 [&lt;ffffffffa06158aa&gt;] ieee80211_open+0x49/0x4c [mac80211]
 [&lt;ffffffff8163ecf9&gt;] __dev_open+0x88/0xde
 [&lt;ffffffff8163ef6e&gt;] __dev_change_flags+0xa4/0x13a
 [&lt;ffffffff8163f023&gt;] dev_change_flags+0x1f/0x54
 [&lt;ffffffff816a5532&gt;] devinet_ioctl+0x2b9/0x5c9
 [&lt;ffffffff816514dd&gt;] ? copy_to_user+0x32/0x38
 [&lt;ffffffff816a6115&gt;] inet_ioctl+0x81/0x9d
 [&lt;ffffffff816a6115&gt;] ? inet_ioctl+0x81/0x9d
 [&lt;ffffffff81621cf8&gt;] sock_do_ioctl+0x20/0x3d
 [&lt;ffffffff816223c4&gt;] sock_ioctl+0x222/0x22e
 [&lt;ffffffff8121cf95&gt;] do_vfs_ioctl+0x453/0x4d7
 [&lt;ffffffff81625603&gt;] ? __sys_recvmsg+0x4c/0x5b
 [&lt;ffffffff81225af1&gt;] ? __fget_light+0x48/0x6c
 [&lt;ffffffff8121d06b&gt;] SyS_ioctl+0x52/0x74
 [&lt;ffffffff816fa736&gt;] entry_SYSCALL_64_fastpath+0x16/0x7a

Signed-off-by: Ben Greear &lt;greearb@candelatech.com&gt;
Signed-off-by: Kalle Valo &lt;kvalo@qca.qualcomm.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
We must not attempt to send WMI packets while holding the data-lock,
as it may deadlock:

BUG: sleeping function called from invalid context at drivers/net/wireless/ath/ath10k/wmi.c:1824
in_atomic(): 1, irqs_disabled(): 0, pid: 2878, name: wpa_supplicant

=============================================
[ INFO: possible recursive locking detected ]
4.4.6+ #21 Tainted: G        W  O
---------------------------------------------
wpa_supplicant/2878 is trying to acquire lock:
 (&amp;(&amp;ar-&gt;data_lock)-&gt;rlock){+.-...}, at: [&lt;ffffffffa0721511&gt;] ath10k_wmi_tx_beacons_iter+0x26/0x11a [ath10k_core]

but task is already holding lock:
 (&amp;(&amp;ar-&gt;data_lock)-&gt;rlock){+.-...}, at: [&lt;ffffffffa070251b&gt;] ath10k_peer_create+0x122/0x1ae [ath10k_core]

other info that might help us debug this:
 Possible unsafe locking scenario:

       CPU0
       ----
  lock(&amp;(&amp;ar-&gt;data_lock)-&gt;rlock);
  lock(&amp;(&amp;ar-&gt;data_lock)-&gt;rlock);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

4 locks held by wpa_supplicant/2878:
 #0:  (rtnl_mutex){+.+.+.}, at: [&lt;ffffffff816493ca&gt;] rtnl_lock+0x12/0x14
 #1:  (&amp;ar-&gt;conf_mutex){+.+.+.}, at: [&lt;ffffffffa0706932&gt;] ath10k_add_interface+0x3b/0xbda [ath10k_core]
 #2:  (&amp;(&amp;ar-&gt;data_lock)-&gt;rlock){+.-...}, at: [&lt;ffffffffa070251b&gt;] ath10k_peer_create+0x122/0x1ae [ath10k_core]
 #3:  (rcu_read_lock){......}, at: [&lt;ffffffffa062f304&gt;] rcu_read_lock+0x0/0x66 [mac80211]

stack backtrace:
CPU: 3 PID: 2878 Comm: wpa_supplicant Tainted: G        W  O    4.4.6+ #21
Hardware name: To be filled by O.E.M. To be filled by O.E.M./ChiefRiver, BIOS 4.6.5 06/07/2013
 0000000000000000 ffff8801fcadf8f0 ffffffff8137086d ffffffff82681720
 ffffffff82681720 ffff8801fcadf9b0 ffffffff8112e3be ffff8801fcadf920
 0000000100000000 ffffffff82681720 ffffffffa0721500 ffff8801fcb8d348
Call Trace:
 [&lt;ffffffff8137086d&gt;] dump_stack+0x81/0xb6
 [&lt;ffffffff8112e3be&gt;] __lock_acquire+0xc5b/0xde7
 [&lt;ffffffffa0721500&gt;] ? ath10k_wmi_tx_beacons_iter+0x15/0x11a [ath10k_core]
 [&lt;ffffffff8112d0d0&gt;] ? mark_lock+0x24/0x201
 [&lt;ffffffff8112e908&gt;] lock_acquire+0x132/0x1cb
 [&lt;ffffffff8112e908&gt;] ? lock_acquire+0x132/0x1cb
 [&lt;ffffffffa0721511&gt;] ? ath10k_wmi_tx_beacons_iter+0x26/0x11a [ath10k_core]
 [&lt;ffffffffa07214eb&gt;] ? ath10k_wmi_cmd_send_nowait+0x1ce/0x1ce [ath10k_core]
 [&lt;ffffffff816f9e2b&gt;] _raw_spin_lock_bh+0x31/0x40
 [&lt;ffffffffa0721511&gt;] ? ath10k_wmi_tx_beacons_iter+0x26/0x11a [ath10k_core]
 [&lt;ffffffffa0721511&gt;] ath10k_wmi_tx_beacons_iter+0x26/0x11a [ath10k_core]
 [&lt;ffffffffa07214eb&gt;] ? ath10k_wmi_cmd_send_nowait+0x1ce/0x1ce [ath10k_core]
 [&lt;ffffffffa062eb18&gt;] __iterate_interfaces+0x9d/0x13d [mac80211]
 [&lt;ffffffffa062f609&gt;] ieee80211_iterate_active_interfaces_atomic+0x32/0x3e [mac80211]
 [&lt;ffffffffa07214eb&gt;] ? ath10k_wmi_cmd_send_nowait+0x1ce/0x1ce [ath10k_core]
 [&lt;ffffffffa071fa9f&gt;] ath10k_wmi_tx_beacons_nowait.isra.13+0x14/0x16 [ath10k_core]
 [&lt;ffffffffa0721676&gt;] ath10k_wmi_cmd_send+0x71/0x242 [ath10k_core]
 [&lt;ffffffffa07023f6&gt;] ath10k_wmi_peer_delete+0x3f/0x42 [ath10k_core]
 [&lt;ffffffffa0702557&gt;] ath10k_peer_create+0x15e/0x1ae [ath10k_core]
 [&lt;ffffffffa0707004&gt;] ath10k_add_interface+0x70d/0xbda [ath10k_core]
 [&lt;ffffffffa05fffcc&gt;] drv_add_interface+0x123/0x1a5 [mac80211]
 [&lt;ffffffffa061554b&gt;] ieee80211_do_open+0x351/0x667 [mac80211]
 [&lt;ffffffffa06158aa&gt;] ieee80211_open+0x49/0x4c [mac80211]
 [&lt;ffffffff8163ecf9&gt;] __dev_open+0x88/0xde
 [&lt;ffffffff8163ef6e&gt;] __dev_change_flags+0xa4/0x13a
 [&lt;ffffffff8163f023&gt;] dev_change_flags+0x1f/0x54
 [&lt;ffffffff816a5532&gt;] devinet_ioctl+0x2b9/0x5c9
 [&lt;ffffffff816514dd&gt;] ? copy_to_user+0x32/0x38
 [&lt;ffffffff816a6115&gt;] inet_ioctl+0x81/0x9d
 [&lt;ffffffff816a6115&gt;] ? inet_ioctl+0x81/0x9d
 [&lt;ffffffff81621cf8&gt;] sock_do_ioctl+0x20/0x3d
 [&lt;ffffffff816223c4&gt;] sock_ioctl+0x222/0x22e
 [&lt;ffffffff8121cf95&gt;] do_vfs_ioctl+0x453/0x4d7
 [&lt;ffffffff81625603&gt;] ? __sys_recvmsg+0x4c/0x5b
 [&lt;ffffffff81225af1&gt;] ? __fget_light+0x48/0x6c
 [&lt;ffffffff8121d06b&gt;] SyS_ioctl+0x52/0x74
 [&lt;ffffffff816fa736&gt;] entry_SYSCALL_64_fastpath+0x16/0x7a

Signed-off-by: Ben Greear &lt;greearb@candelatech.com&gt;
Signed-off-by: Kalle Valo &lt;kvalo@qca.qualcomm.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge tag 'wireless-drivers-next-for-davem-2016-05-13' of git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next</title>
<updated>2016-05-20T23:40:35+00:00</updated>
<author>
<name>David S. Miller</name>
<email>davem@davemloft.net</email>
</author>
<published>2016-05-20T23:40:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux-stable.git/commit/?id=56025caa821d8e398b7cff2c45fb1e3e769549d7'/>
<id>56025caa821d8e398b7cff2c45fb1e3e769549d7</id>
<content type='text'>
Kalle Valo says:

====================
wireless-drivers patches for 4.7

Major changes:

iwlwifi

* remove IWLWIFI_DEBUG_EXPERIMENTAL_UCODE kconfig option
* work for RX multiqueue continues
* dynamic queue allocation work continues
* add Luca as maintainer
* a bunch of fixes and improvements all over

brcmfmac

* add 4356 sdio support

ath6kl

* add ability to set debug uart baud rate with a module parameter

wil6210

* add debugfs file to configure firmware led functionality
====================

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Kalle Valo says:

====================
wireless-drivers patches for 4.7

Major changes:

iwlwifi

* remove IWLWIFI_DEBUG_EXPERIMENTAL_UCODE kconfig option
* work for RX multiqueue continues
* dynamic queue allocation work continues
* add Luca as maintainer
* a bunch of fixes and improvements all over

brcmfmac

* add 4356 sdio support

ath6kl

* add ability to set debug uart baud rate with a module parameter

wil6210

* add debugfs file to configure firmware led functionality
====================

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ath10k: Fix survey reporting with QCA4019</title>
<updated>2016-05-11T19:53:10+00:00</updated>
<author>
<name>Vasanthakumar Thiagarajan</name>
<email>vthiagar@qti.qualcomm.com</email>
</author>
<published>2016-05-09T18:57:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux-stable.git/commit/?id=ee9ca147c59c0ee128bbf7fc079ee49401070086'/>
<id>ee9ca147c59c0ee128bbf7fc079ee49401070086</id>
<content type='text'>
In QCA4019, cycle counter wraparound in same fashion
as QCA988X. When the cycle counter wraparound it
resets to 0x7fffffff. Set has_shifted_cc_wraparound to
true for QCA4019 to enable the code path to handle cycle
counter wraparound for consistent survey report.

Signed-off-by: Vasanthakumar Thiagarajan &lt;vthiagar@qti.qualcomm.com&gt;
Signed-off-by: Kalle Valo &lt;kvalo@qca.qualcomm.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
In QCA4019, cycle counter wraparound in same fashion
as QCA988X. When the cycle counter wraparound it
resets to 0x7fffffff. Set has_shifted_cc_wraparound to
true for QCA4019 to enable the code path to handle cycle
counter wraparound for consistent survey report.

Signed-off-by: Vasanthakumar Thiagarajan &lt;vthiagar@qti.qualcomm.com&gt;
Signed-off-by: Kalle Valo &lt;kvalo@qca.qualcomm.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ath10k: suppress warnings when getting wmi peer_rate_code_list event</title>
<updated>2016-05-11T19:53:06+00:00</updated>
<author>
<name>Vasanthakumar Thiagarajan</name>
<email>vthiagar@qti.qualcomm.com</email>
</author>
<published>2016-05-09T18:57:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux-stable.git/commit/?id=36bd39bb0ae8544e3f5b9c1af45f39f51075611b'/>
<id>36bd39bb0ae8544e3f5b9c1af45f39f51075611b</id>
<content type='text'>
In 10.4, fw sends WMI PEER_RATECODE_LIST_EVENTID after successful
peer_assoc cmd. As of now this event is not of much use and not
implemented. Change the debug level and messsage as appropriate
to suppress "Unknown eventid: 36898".

Signed-off-by: Vasanthakumar Thiagarajan &lt;vthiagar@qti.qualcomm.com&gt;
Signed-off-by: Kalle Valo &lt;kvalo@qca.qualcomm.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
In 10.4, fw sends WMI PEER_RATECODE_LIST_EVENTID after successful
peer_assoc cmd. As of now this event is not of much use and not
implemented. Change the debug level and messsage as appropriate
to suppress "Unknown eventid: 36898".

Signed-off-by: Vasanthakumar Thiagarajan &lt;vthiagar@qti.qualcomm.com&gt;
Signed-off-by: Kalle Valo &lt;kvalo@qca.qualcomm.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>wil6210: add support for device led configuration</title>
<updated>2016-05-11T19:45:20+00:00</updated>
<author>
<name>Maya Erez</name>
<email>qca_merez@qca.qualcomm.com</email>
</author>
<published>2016-05-09T18:57:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux-stable.git/commit/?id=10d599ad84a1b98450c8867ce548ea4bf0f6df1a'/>
<id>10d599ad84a1b98450c8867ce548ea4bf0f6df1a</id>
<content type='text'>
Add the ability to configure the device led to be used for notifying
the AP activity (60G device supports leds 0-2).
The host can also configure the blinking frequency of the led in
three states.

Signed-off-by: Maya Erez &lt;qca_merez@qca.qualcomm.com&gt;
Signed-off-by: Kalle Valo &lt;kvalo@qca.qualcomm.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Add the ability to configure the device led to be used for notifying
the AP activity (60G device supports leds 0-2).
The host can also configure the blinking frequency of the led in
three states.

Signed-off-by: Maya Erez &lt;qca_merez@qca.qualcomm.com&gt;
Signed-off-by: Kalle Valo &lt;kvalo@qca.qualcomm.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ath9k: Fix symbol overlap window for half/quarter channels</title>
<updated>2016-05-09T18:12:01+00:00</updated>
<author>
<name>Helmut Schaa</name>
<email>helmut.schaa@googlemail.com</email>
</author>
<published>2016-04-29T13:06:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux-stable.git/commit/?id=41842dc1f072d69ca40f36ce5032ccfd23488f51'/>
<id>41842dc1f072d69ca40f36ce5032ccfd23488f51</id>
<content type='text'>
Since commit cd6cfd7311a385144a2f9c74f692ae2df3ae033f
"ath9k: do not set half/quarter channel flags in AR_PHY_MODE" the
condition "rfMode &amp; (AR_PHY_MODE_QUARTER | AR_PHY_MODE_HALF)" would
never evaluate to true.

Fix this by using the available IS_CHAN_HALF_RATE and IS_CHAN_QUARTER_RATE
marcros instead.

Signed-off-by: Helmut Schaa &lt;helmut.schaa@googlemail.com&gt;
Cc: Felix Fietkau &lt;nbd@openwrt.org&gt;
Acked-by: Felix Fietkau &lt;nbd@openwrt.org&gt;
Signed-off-by: Kalle Valo &lt;kvalo@qca.qualcomm.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Since commit cd6cfd7311a385144a2f9c74f692ae2df3ae033f
"ath9k: do not set half/quarter channel flags in AR_PHY_MODE" the
condition "rfMode &amp; (AR_PHY_MODE_QUARTER | AR_PHY_MODE_HALF)" would
never evaluate to true.

Fix this by using the available IS_CHAN_HALF_RATE and IS_CHAN_QUARTER_RATE
marcros instead.

Signed-off-by: Helmut Schaa &lt;helmut.schaa@googlemail.com&gt;
Cc: Felix Fietkau &lt;nbd@openwrt.org&gt;
Acked-by: Felix Fietkau &lt;nbd@openwrt.org&gt;
Signed-off-by: Kalle Valo &lt;kvalo@qca.qualcomm.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ath9k: Simplify ar9003_hw_tx99_set_txpower</title>
<updated>2016-05-09T17:46:51+00:00</updated>
<author>
<name>Helmut Schaa</name>
<email>helmut.schaa@googlemail.com</email>
</author>
<published>2016-04-28T14:45:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux-stable.git/commit/?id=b0291715d31c891bcb5de936271881f58600f7c1'/>
<id>b0291715d31c891bcb5de936271881f58600f7c1</id>
<content type='text'>
There's no need to keep the same for loop twice in the code.
Move the txpower cap before the loop to reduce code complexity.

Signed-off-by: Helmut Schaa &lt;helmut.schaa@googlemail.com&gt;
Signed-off-by: Kalle Valo &lt;kvalo@qca.qualcomm.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
There's no need to keep the same for loop twice in the code.
Move the txpower cap before the loop to reduce code complexity.

Signed-off-by: Helmut Schaa &lt;helmut.schaa@googlemail.com&gt;
Signed-off-by: Kalle Valo &lt;kvalo@qca.qualcomm.com&gt;
</pre>
</div>
</content>
</entry>
</feed>
