<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/net/wireless/ath, branch v3.9</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v3.9</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v3.9'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2013-04-12T17:22:09Z</updated>
<entry>
<title>ath9k_hw: change AR9580 initvals to fix a stability issue</title>
<updated>2013-04-12T17:22:09Z</updated>
<author>
<name>Felix Fietkau</name>
<email>nbd@openwrt.org</email>
</author>
<published>2013-04-10T13:26:06Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=f09a878511997c25a76bf111a32f6b8345a701a5'/>
<id>urn:sha1:f09a878511997c25a76bf111a32f6b8345a701a5</id>
<content type='text'>
The hardware parsing of Control Wrapper Frames needs to be disabled, as
it has been causing spurious decryption error reports. The initvals for
other chips have been updated to disable it, but AR9580 was left out for
some reason.

Cc: stable@vger.kernel.org
Signed-off-by: Felix Fietkau &lt;nbd@openwrt.org&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>ath9k_htc: accept 1.x firmware newer than 1.3</title>
<updated>2013-04-08T18:35:03Z</updated>
<author>
<name>Felix Fietkau</name>
<email>nbd@openwrt.org</email>
</author>
<published>2013-04-07T19:10:48Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=319e7bd96aca64a478f3aad40711c928405b8b77'/>
<id>urn:sha1:319e7bd96aca64a478f3aad40711c928405b8b77</id>
<content type='text'>
Since the firmware has been open sourced, the minor version has been
bumped to 1.4 and the API/ABI will stay compatible across further 1.x
releases.

Signed-off-by: Felix Fietkau &lt;nbd@openwrt.org&gt;
Cc: stable@vger.kernel.org
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>ath9k: fix DFS detector called in softirq context</title>
<updated>2013-04-08T18:35:03Z</updated>
<author>
<name>Zefir Kurtisi</name>
<email>zefir.kurtisi@neratec.com</email>
</author>
<published>2013-04-02T10:51:48Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=5d8cd3b16ec7b56d7502ff1ae21ae6596d2f96e9'/>
<id>urn:sha1:5d8cd3b16ec7b56d7502ff1ae21ae6596d2f96e9</id>
<content type='text'>
Signed-off-by: Zefir Kurtisi &lt;zefir.kurtisi@neratec.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>ath9k: Re-enable interrupts after a channel change failure</title>
<updated>2013-04-03T18:31:57Z</updated>
<author>
<name>Robert Shade</name>
<email>robert.shade@gmail.com</email>
</author>
<published>2013-04-02T23:52:45Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=f50b1cd37446ad32c432f0f73bbed67a1c076eae'/>
<id>urn:sha1:f50b1cd37446ad32c432f0f73bbed67a1c076eae</id>
<content type='text'>
ath_complete_reset will not be called if ath9k_hw_reset
is unsuccessful, so we need to re-enable intertupts to
balence the previous ath_prepare_reset call.  Also schedule a
reset as a best effort method to recover the chip from
whatever state caused the channel change failure.

Fixes https://bugzilla.kernel.org/show_bug.cgi?id=55771

Signed-off-by: Robert Shade &lt;robert.shade@gmail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>ath9k: avoid queueing hw check work when suspended</title>
<updated>2013-03-27T15:07:05Z</updated>
<author>
<name>Luis R. Rodriguez</name>
<email>mcgrof@do-not-panic.com</email>
</author>
<published>2013-03-25T18:27:46Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=7fc0357479eeff4ca808c4d8c09bc7631f576b8d'/>
<id>urn:sha1:7fc0357479eeff4ca808c4d8c09bc7631f576b8d</id>
<content type='text'>
The following issue was reported.

WARNING: at net/mac80211/util.c:599 ieee80211_can_queue_work.isra.7+0x32/0x40 [mac80211]()
Hardware name: iMac12,1
queueing ieee80211 work while going to suspend
Pid: 0, comm: swapper/0 Tainted: PF          O 3.8.2-206.fc18.x86_64 #1
Call Trace: Mar 16 09:39:17 Parags-iMac kernel: [ 3993.642992]  &lt;IRQ&gt;
[&lt;ffffffff8105e61f&gt;] warn_slowpath_common+0x7f/0xc0
[&lt;ffffffffa0581420&gt;] ? ath_start_rx_poll+0x70/0x70 [ath9k]
&lt;ffffffff8105e716&gt;] warn_slowpath_fmt+0x46/0x50
[&lt;ffffffffa045b542&gt;] ieee80211_can_queue_work.isra.7+0x32/0x40

Fix this by avoiding to queue the work if our device has
already been marked as suspended or stopped.

Reported-by: Parag Warudkar &lt;parag.lkml@gmail.com&gt;
Tested-by: Parag Warudkar &lt;parag.lkml@gmail.com&gt;
Cc: stable@vger.kernel.org
Signed-off-by: Luis R. Rodriguez &lt;mcgrof@do-not-panic.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>ath9k: limit tx path hang check to normal data queues</title>
<updated>2013-03-18T19:20:35Z</updated>
<author>
<name>Felix Fietkau</name>
<email>nbd@openwrt.org</email>
</author>
<published>2013-03-15T15:18:44Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=01d4ab96d2e7fceaad204e5a8710ce34e229b8c5'/>
<id>urn:sha1:01d4ab96d2e7fceaad204e5a8710ce34e229b8c5</id>
<content type='text'>
The beacon and multicast-buffer queues are managed by the beacon
tasklet, and the generic tx path hang check does not help in any way
here. Running it on those queues anyway can introduce some race
conditions leading to unnecessary chip resets.

Cc: stable@vger.kernel.org
Signed-off-by: Felix Fietkau &lt;nbd@openwrt.org&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>ath9k_hw: revert chainmask to user configuration after calibration</title>
<updated>2013-03-18T19:20:34Z</updated>
<author>
<name>Felix Fietkau</name>
<email>nbd@openwrt.org</email>
</author>
<published>2013-03-15T13:53:31Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=74632d11a133b5baf6b9d622dd19d2f944d93d94'/>
<id>urn:sha1:74632d11a133b5baf6b9d622dd19d2f944d93d94</id>
<content type='text'>
The commit 'ath9k_hw: fix calibration issues on chainmask that don't
include chain 0' changed the hardware chainmask to the chip chainmask
for the duration of the calibration, but the revert to user
configuration in the reset path runs too early.

That causes some issues with limiting the number of antennas (including
spurious failure in hardware-generated packets).

Fix this by reverting the chainmask after the essential parts of the
calibration that need the workaround, and before NF calibration is run.

Signed-off-by: Felix Fietkau &lt;nbd@openwrt.org&gt;
Reported-by: Wojciech Dubowik &lt;Wojciech.Dubowik@neratec.com&gt;
Tested-by: Wojciech Dubowik &lt;Wojciech.Dubowik@neratec.com&gt;
Cc: stable@vger.kernel.org
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless into for-davem</title>
<updated>2013-03-01T18:52:03Z</updated>
<author>
<name>John W. Linville</name>
<email>linville@tuxdriver.com</email>
</author>
<published>2013-03-01T18:52:03Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=98b7ff9a4977e4f4f451c30288b197ad79e5ab7f'/>
<id>urn:sha1:98b7ff9a4977e4f4f451c30288b197ad79e5ab7f</id>
<content type='text'>
</content>
</entry>
<entry>
<title>ath9k_hw: improve reset reliability after errors</title>
<updated>2013-02-27T19:12:52Z</updated>
<author>
<name>Felix Fietkau</name>
<email>nbd@openwrt.org</email>
</author>
<published>2013-02-25T19:51:07Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=3412f2f086ea7531378fabe756bd4a1109994ae6'/>
<id>urn:sha1:3412f2f086ea7531378fabe756bd4a1109994ae6</id>
<content type='text'>
On many different chips, important aspects of the MAC state are not
fully cleared by a warm reset. This can show up as tx/rx hangs, those
annoying "DMA failed to stop in 10 ms..." messages or other quirks.

On AR933x, the chip can occasionally get stuck in a way that only a
driver unload/reload or a reboot would bring it back to life.

With this patch, a full reset is issued when bringing the chip out of
FULL-SLEEP state (after idle), or if either Rx or Tx was not shut down
properly. This makes the DMA related error messages disappear completely
in my tests on AR933x, and the chip does not get stuck anymore.

Cc: stable@vger.kernel.org
Signed-off-by: Felix Fietkau &lt;nbd@openwrt.org&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>ath9k_htc: fix signal strength handling issues</title>
<updated>2013-02-27T19:12:51Z</updated>
<author>
<name>Felix Fietkau</name>
<email>nbd@openwrt.org</email>
</author>
<published>2013-02-22T20:37:25Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=838f427955dcfd16858b0108ce29029da0d56a4e'/>
<id>urn:sha1:838f427955dcfd16858b0108ce29029da0d56a4e</id>
<content type='text'>
The ath9k commit 2ef167557c0a26c88162ecffb017bfcc51eb7b29
(ath9k: fix signal strength reporting issues) fixed an issue where the
reported per-frame signal strength reported to mac80211 was being
overwritten with an internal average. The same issue is also present
in ath9k_htc.
In addition to preventing the driver from overwriting the value, this
commit also ensures that the internal average (which is used for ANI)
only tracks beacons of the AP that we're connected to.

Signed-off-by: Felix Fietkau &lt;nbd@openwrt.org&gt;
Cc: stable@vger.kernel.org
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
</feed>
