Skip to content

K
Kernel

openeuler / Kernel
1 年多 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 07 11月, 2012 1 次提交
  3. 05 11月, 2012 2 次提交
  5. 01 11月, 2012 1 次提交
    • E
      iwlwifi: handle RFKILL logic in the transport layer · f946b529
      由 Emmanuel Grumbach 提交于 
      No HCMD can be sent while RFKILL is asserted. If a SYNC
command is running while RFKILL is asserted the fw will
silently discard it. This means that the driver needs to
wake the process that sleeps on the CMD_SYNC.

Since the RFKILL interrupt is handled in the transport layer
and the code that sleeps in CMD_SYNC is also in the transport
layer, all this logic can be handled there.
This simplifies the work of the op_mode.

So the transport layer will now return -ERFKILL when a CMD
is sent and RFKILL is asserted. This will be the case even
when the CMD is SYNC. The transport layer will return
-ERFKILL straight away.
Signed-off-by: NEmmanuel Grumbach <emmanuel.grumbach@intel.com>
Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      f946b529
  7. 29 10月, 2012 1 次提交
  9. 23 10月, 2012 1 次提交
  11. 16 10月, 2012 7 次提交
  13. 19 9月, 2012 1 次提交
  15. 11 9月, 2012 6 次提交
  17. 06 9月, 2012 1 次提交
  19. 05 9月, 2012 1 次提交
  21. 24 8月, 2012 1 次提交
  23. 22 8月, 2012 2 次提交
  25. 26 7月, 2012 2 次提交
    • E
      iwlwifi: get the correct HCMD in the response handler · 96791422
      由 Emmanuel Grumbach 提交于 
      Until now, the response handler of a Host Command got the
exact same pointer that was also given to the DMA engine.
We almost never need to the Host Command that was sent while
handling its response, but when we do need it, we see that
the command has been modified.

This mystery has been elucidated. The FH (our DMA engine)
writes its meta data on the buffer in the DRAM. Of course it
copies the buffer to the NIC first. This was known to happen
for Tx command, but as a matter of fact, it happens to all
TFD brought by the FH which doesn't care much about what it
brings from DRAM to internal SRAM.

So copy the Host Command to yet another buffer so that we
can properly pass the buffer that was sent originally to the
fw. Do that only if it was request by the user since very
few flows need to get the HCMD sent in the response handler.
Signed-off-by: NEmmanuel Grumbach <emmanuel.grumbach@intel.com>
Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      96791422
    • M
      iwlwifi: rework the iwlwifi debugfs structure · 9da987ac
      由 Meenakshi Venkataraman 提交于 
      The generic part of the driver now creates all debugfs
directories. It creates a root directory directly in
the the root of the debugfs filesystem and within that
directories for each device, named after the device ID
of the devices iwlwifi is attached to.

In the cfg80211/mac80211 directory there's now a link
to the toplevel iwlwifi debugfs directory to make it
easier to find the debugfs files.
Signed-off-by: NMeenakshi Venkataraman <meenakshi.venkataraman@intel.com>
Reviewed-by: NEmmanuel Grumbach <emmanuel.grumbach@intel.com>
Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      9da987ac
  27. 12 7月, 2012 1 次提交
  29. 09 7月, 2012 1 次提交
  31. 03 7月, 2012 1 次提交
  33. 29 6月, 2012 1 次提交
  35. 25 6月, 2012 1 次提交
  37. 18 6月, 2012 4 次提交
  39. 13 6月, 2012 4 次提交