<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/net/wireless, branch v3.19</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.19</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v3.19'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2015-01-19T12:32:29Z</updated>
<entry>
<title>ath9k: fix race condition in irq processing during hardware reset</title>
<updated>2015-01-19T12:32:29Z</updated>
<author>
<name>Felix Fietkau</name>
<email>nbd@openwrt.org</email>
</author>
<published>2015-01-14T13:17:36Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=e3f31175a3eeb492a6ab788e4fa136c19b43aab4'/>
<id>urn:sha1:e3f31175a3eeb492a6ab788e4fa136c19b43aab4</id>
<content type='text'>
To fix invalid hardware accesses, the commit 872b5d814f99 ("ath9k: do not
access hardware on IRQs during reset") made the irq handler ignore interrupts
emitted after queueing a hardware reset (which disables the IRQ). This left a
small time window for the IRQ to get re-enabled by the tasklet, which caused
IRQ storms.  Instead of returning IRQ_NONE when ATH_OP_HW_RESET is set, disable
the IRQ entirely for the duration of the reset.

Signed-off-by: Felix Fietkau &lt;nbd@openwrt.org&gt;
Signed-off-by: Kalle Valo &lt;kvalo@codeaurora.org&gt;
</content>
</entry>
<entry>
<title>Merge tag 'iwlwifi-for-kalle-2015-01-15' of https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes</title>
<updated>2015-01-19T07:47:28Z</updated>
<author>
<name>Kalle Valo</name>
<email>kvalo@codeaurora.org</email>
</author>
<published>2015-01-19T07:47:28Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=7b05520160a3252577f9a258609499b73f3bdef1'/>
<id>urn:sha1:7b05520160a3252577f9a258609499b73f3bdef1</id>
<content type='text'>
* one fix for rfkill while scheduled scan is running.
  Linus's system hit this issue. WiFi would be unavailable
  after this has happpened because of bad state in cfg80211.
</content>
</entry>
<entry>
<title>iwlwifi: mvm: abort scheduled scan upon RFKILL</title>
<updated>2015-01-18T20:04:37Z</updated>
<author>
<name>Emmanuel Grumbach</name>
<email>emmanuel.grumbach@intel.com</email>
</author>
<published>2015-01-18T19:39:30Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=90ea15c1148bb1517e400ed14bb875e330aead2e'/>
<id>urn:sha1:90ea15c1148bb1517e400ed14bb875e330aead2e</id>
<content type='text'>
When we have an active scheduled scan, and the RFKILL
interrupt kicks in, the stack will cancel the scheduled
scan as part of the down flow. But cancelling scheduled
scan usually implies sending a command to the firwmare
which has been killed as part of the RFKILL interrupt
handling.
Because of that, we returned an error to mac80211 when
it asked to stop the scheduled scan and didn't notify the
end of the scheduled scan. Besides a fat warning, this led
to a situation in which cfg80211 would refuse any new scan
request.

To disentangle this, fake that the scheduled scan has been
stopped without sending the command to the firwmare, return
0 after having properly let cfg80211 know that the scan
has been cancelled.

This is basically the same as:
commit 9b520d84957d63348e87c0f2cbd21d86e1e8f2f2
Author: Emmanuel Grumbach &lt;emmanuel.grumbach@intel.com&gt;
Date:   Tue Nov 4 15:54:11 2014 +0200

    iwlwifi: mvm: abort scan upon RFKILL

    This code existed but not for all the different FW APIs
    we support.
    Fix this.

but for the scheduled scan case.

Link: http://permalink.gmane.org/gmane.linux.kernel.wireless.general/133232
Reported-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Signed-off-by: Emmanuel Grumbach &lt;emmanuel.grumbach@intel.com&gt;
</content>
</entry>
<entry>
<title>Merge tag 'iwlwifi-for-kalle-2015-01-13' of https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes</title>
<updated>2015-01-15T12:06:07Z</updated>
<author>
<name>Kalle Valo</name>
<email>kvalo@codeaurora.org</email>
</author>
<published>2015-01-15T12:06:07Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=781f51d4c2038b694a774b070dcd93ea22d10655'/>
<id>urn:sha1:781f51d4c2038b694a774b070dcd93ea22d10655</id>
<content type='text'>
* A fix for scan that fixes a firmware assertion
* A fix that improves roaming behavior. Same fix has been tested for
  a while in iwldvm. This is a bit of a work around, but the real fix
  should be in mac80211 and will come later.
* A fix for BARs that avoids a WARNING.
</content>
</entry>
<entry>
<title>iwlwifi: mvm: set the tx cmd tid for BAR frame correctly</title>
<updated>2015-01-13T06:53:23Z</updated>
<author>
<name>Eyal Shapira</name>
<email>eyal@wizery.com</email>
</author>
<published>2014-12-31T16:34:56Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=9b3b43d8d1300c36ba5945c12fd505409eaf4807'/>
<id>urn:sha1:9b3b43d8d1300c36ba5945c12fd505409eaf4807</id>
<content type='text'>
BAR tx cmd tid was set to non qos (8). This is wrong as BAR
should be sent with the tid of the BA session.
This led to a corruption in the firmware. The visible
effect of this from the driver side is the BA notification
that comes back after the BAR. It was botched and led to the
WARNING below.

------------[ cut here ]------------
WARNING: CPU: 2 PID: 17707 at /home/tester/workspace_hostap/iwlwifi/drivers/net/wireless/iwlwifi/mvm/tx.c:976 iwl_mvm_rx_ba_notif+0x4ba/0x4d0 [iwlmvm]()
Q 4500, tid 8, flow 65535
Modules linked in: iwlmvm(O) mac80211(O) iwlwifi(O) cfg80211(O) compat(O) netconsole configfs ctr ccm arc4 autofs4 microcode bnep rfcomm snd_hda_codec_hdmi snd_hda_codec_idt snd_hda_codec_generic snd_hda_intel joydev snd_hda_codec uvcvideo videobuf2_core snd_hwdep videodev snd_pcm videobuf2_vmalloc videobuf2_memops i915 snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device drm_kms_helper dell_wmi dell_laptop drm btusb bluetooth snd psmouse i2c_algo_bit sparse_keymap wmi soundcore 6lowpan_iphc dcdbas serio_raw video lpc_ich ppdev mac_hid parport_pc nfsd nfs_acl auth_rpcgss nfs fscache binfmt_misc lockd sunrpc lp parport msdos sdhci_pci sdhci mmc_core ahci libahci e1000e ptp pps_core [last unloaded: compat]
CPU: 2 PID: 17707 Comm: irq/46-iwlwifi Tainted: G        W  O 3.14.17-patched #4
Hardware name: Dell Inc. Latitude E6430/0CPWYR, BIOS A09 12/13/2012
 00000000 00000000 ebd49d6c c1616221 f985dbdc ebd49d9c c1044e44 f9861df4
 ebd49dc8 0000452b f985dbdc 000003d0 f98395da f98395da ebd49f10 eaf3d8a4
 0000ffff ebd49db4 c1044f03 00000009 ebd49dac f9861df4 ebd49dc8 ebd49e64
Call Trace:
 [&lt;c1616221&gt;] dump_stack+0x41/0x52
 [&lt;c1044e44&gt;] warn_slowpath_common+0x84/0xa0
 [&lt;f98395da&gt;] ? iwl_mvm_rx_ba_notif+0x4ba/0x4d0 [iwlmvm]
 [&lt;f98395da&gt;] ? iwl_mvm_rx_ba_notif+0x4ba/0x4d0 [iwlmvm]
 [&lt;c1044f03&gt;] warn_slowpath_fmt+0x33/0x40
 [&lt;f98395da&gt;] iwl_mvm_rx_ba_notif+0x4ba/0x4d0 [iwlmvm]
 [&lt;c10e3952&gt;] ? ring_buffer_unlock_commit+0xa2/0xd0
 [&lt;c10e9767&gt;] ? trace_buffer_unlock_commit+0x37/0x50
 [&lt;f98568a3&gt;] ? iwl_tm_mvm_send_rx+0x53/0x90 [iwlmvm]
 [&lt;f98327a8&gt;] iwl_mvm_rx_dispatch+0x108/0x130 [iwlmvm]
 [&lt;f9eac7e7&gt;] iwl_pcie_irq_handler+0xf17/0x15b0 [iwlwifi]
 [&lt;c10994c1&gt;] irq_thread_fn+0x21/0x50
 [&lt;c109926c&gt;] irq_thread+0xec/0x110
 [&lt;c10994a0&gt;] ? irq_thread_dtor+0xb0/0xb0
 [&lt;c10993f0&gt;] ? irq_finalize_oneshot.part.34+0xc0/0xc0
 [&lt;c1099180&gt;] ? wake_threads_waitq+0x40/0x40
 [&lt;c1062fdb&gt;] kthread+0x9b/0xb0
 [&lt;c1627137&gt;] ret_from_kernel_thread+0x1b/0x28
 [&lt;c1062f40&gt;] ? flush_kthread_worker+0x90/0x90
---[ end trace 5e0f67374816db17 ]---

Signed-off-by: Eyal Shapira &lt;eyalx.shapira@intel.com&gt;
Reviewed-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
Signed-off-by: Emmanuel Grumbach &lt;emmanuel.grumbach@intel.com&gt;
</content>
</entry>
<entry>
<title>iwlwifi: mvm: drop non VO frames when flushing</title>
<updated>2015-01-12T14:34:26Z</updated>
<author>
<name>Emmanuel Grumbach</name>
<email>emmanuel.grumbach@intel.com</email>
</author>
<published>2015-01-12T14:34:26Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=4e6c48e0984e28d064ee8fbc292aee7b7920c507'/>
<id>urn:sha1:4e6c48e0984e28d064ee8fbc292aee7b7920c507</id>
<content type='text'>
This change has already been implemented in iwldvm:

commit a260e7b3f0307878b99d57ed1406cf2d497923b8
Author: Emmanuel Grumbach &lt;emmanuel.grumbach@intel.com&gt;
Date:   Sun Oct 5 09:11:14 2014 +0300

    iwlwifi: dvm: drop non VO frames when flushing

Since I added the flush() callback implementation in mvm,
we got reports that the queues are stuck while roaming
or suspending.
This commit above helped much for iwldvm, implement the
same behavior for iwlmvm.

CC: &lt;stable@vger.kernel.org&gt; [3.16+]
Fixes: c5b0e7c0565a ("iwlwifi: mvm: implement mac80211's flush callback")
Signed-off-by: Emmanuel Grumbach &lt;emmanuel.grumbach@intel.com&gt;
</content>
</entry>
<entry>
<title>iwlwifi: mvm: fix EBS on single scan</title>
<updated>2015-01-12T07:56:19Z</updated>
<author>
<name>David Spinadel</name>
<email>david.spinadel@intel.com</email>
</author>
<published>2014-12-01T21:30:07Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=1f9c418fd94c97c82dc0454fdadece37238f23e7'/>
<id>urn:sha1:1f9c418fd94c97c82dc0454fdadece37238f23e7</id>
<content type='text'>
EBS error detection isn't supported by all FWs, so turn it on
only if the FW advertises such support.

Signed-off-by: David Spinadel &lt;david.spinadel@intel.com&gt;
Reviewed-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
Signed-off-by: Emmanuel Grumbach &lt;emmanuel.grumbach@intel.com&gt;
</content>
</entry>
<entry>
<title>Merge tag 'iwlwifi-for-kalle-2015-01-05' of https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes</title>
<updated>2015-01-05T10:07:04Z</updated>
<author>
<name>Kalle Valo</name>
<email>kvalo@codeaurora.org</email>
</author>
<published>2015-01-05T10:07:04Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=c702674f99e612a22cf6e8f9b4bec341257970c0'/>
<id>urn:sha1:c702674f99e612a22cf6e8f9b4bec341257970c0</id>
<content type='text'>
* fix for 7265D NVM check
* fixes for scan: fix long scanning times and network
	discovery
* new firmware API for iwlmvm supported devices
* fixes in rate control
</content>
</entry>
<entry>
<title>iwlwifi: bump firmware API for mvm devices to 12</title>
<updated>2015-01-05T09:02:37Z</updated>
<author>
<name>Emmanuel Grumbach</name>
<email>emmanuel.grumbach@intel.com</email>
</author>
<published>2015-01-05T07:42:40Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=91f491fd7dfbae6e5ce5887293723d818adf7d5d'/>
<id>urn:sha1:91f491fd7dfbae6e5ce5887293723d818adf7d5d</id>
<content type='text'>
This allows 3160 / 7260 / 7265 / 7265D / 8000 devices to
use the latest version of the firmware.

Signed-off-by: Emmanuel Grumbach &lt;emmanuel.grumbach@intel.com&gt;
</content>
</entry>
<entry>
<title>iwlwifi: mvm: scan dwell time corrections</title>
<updated>2015-01-05T09:02:37Z</updated>
<author>
<name>David Spinadel</name>
<email>david.spinadel@intel.com</email>
</author>
<published>2014-12-29T13:43:48Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=720daf20cce18cfbdfd7904977f25e089aad63fe'/>
<id>urn:sha1:720daf20cce18cfbdfd7904977f25e089aad63fe</id>
<content type='text'>
Use only basic dwell time (10 ms for active scan and 110 for passive),
regardless of the number of the probes and the band, if it is
supported by the FW. The FW will add 3 ms for each probe sent and 10
ms for low band channels.
Add a TLV flag to indicate such support in FW.

This fix is needed to fix few bugs regarding scans that take too much time.

Signed-off-by: David Spinadel &lt;david.spinadel@intel.com&gt;
Signed-off-by: Emmanuel Grumbach &lt;emmanuel.grumbach@intel.com&gt;
</content>
</entry>
</feed>
