Skip to content

K
Kernel

openeuler / Kernel
接近 2 年 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 31 8月, 2018 2 次提交
  3. 07 8月, 2018 1 次提交
  5. 02 8月, 2018 2 次提交
  7. 26 7月, 2018 1 次提交
  9. 25 7月, 2018 1 次提交
  11. 29 5月, 2018 1 次提交
    • G
      iwlwifi: add csr configuration for 6300 devices · 0513c083
      由 Golan Ben Ami 提交于 
      Recently we have switched the csr addresses and values configuration
from a single configuration to all devices to a per-device configuration.
Doing that, the configuration for 6300 devices wasn't set.
This missing definition introduced a kernel panic once trying to access
the csr's.

Add the missing 6300 csr configuration.

While at it, add a checker that the csr values were indeed
configured, and bail out more gracefully if not.

Fixes: a8cbb46f ("iwlwifi: allow different csr flags for different device families")
Signed-off-by: NGolan Ben Ami <golan.ben.ami@intel.com>
Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      0513c083
  13. 29 3月, 2018 1 次提交
  15. 16 3月, 2018 1 次提交
    • L
      iwlwifi: add shared clock PHY config flag for some devices · 86a2b204
      由 Luca Coelho 提交于 
      Some devices use a shared clock which is very sensitive to variations
and cause trouble in some situations.  We need to set a bit in the phy
configuration to indicate that to the FW.  To make this generic, add a
extra_phy_config_flags element to the device configuration and OR it
into the phy_cfg before sending it to the firmware.  And also create a
set of configurations for devices that use shared clocks and need this
extra bit to be set.

Fixes: c62446d2 ("iwlwifi: add new 9460 series PCI IDs")
Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      86a2b204
  17. 05 12月, 2017 1 次提交
  19. 28 11月, 2017 1 次提交
  21. 16 11月, 2017 1 次提交
    • L
      iwlwifi: fix PCI IDs and configuration mapping for 9000 series · dbc89253
      由 Luca Coelho 提交于 
      A lot of PCI IDs were missing and there were some problems with the
configuration and firmware selection for devices on the 9000 series.
Fix the firmware selection by adding files for the B-steps; add
configuration for some integrated devices; and add a bunch of PCI IDs
(mostly for integrated devices) that were missing from the driver's
list.

Without this patch, a lot of devices will not be recognized or will
try to load the wrong firmware file.

Cc: stable@vger.kernel.org # 4.13
Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      dbc89253
  23. 03 11月, 2017 3 次提交
  25. 18 10月, 2017 1 次提交
  27. 06 10月, 2017 8 次提交
  29. 18 8月, 2017 2 次提交
  31. 01 8月, 2017 2 次提交
  33. 30 6月, 2017 1 次提交
  35. 29 6月, 2017 3 次提交
  37. 23 6月, 2017 1 次提交
    • J
      iwlwifi: pcie: don't report RF-kill enabled while shutting down · 326477e4
      由 Johannes Berg 提交于 
      When toggling the RF-kill pin quickly in succession, the driver can
get rather confused because it might be in the process of shutting
down, expecting all commands to go through quickly due to rfkill,
but the transport already thinks the device is accessible again,
even though it previously shut it down. This leads to bugs, and I
even observed a kernel panic.

Avoid this by making the PCIe code only report that the radio is
enabled again after the higher layers actually decided to shut it
off.

This also pulls out this common RF-kill checking code into a common
function called by both transport generations and also moves it to
the direct method - in the internal helper we don't really care
about the RF-kill status anymore since we won't report it up until
the stop anyway.
Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      326477e4
  39. 02 6月, 2017 1 次提交
  41. 20 4月, 2017 2 次提交
  43. 11 4月, 2017 1 次提交
  45. 07 2月, 2017 2 次提交
    • J
      iwlwifi: pcie: fix another RF-kill race · 23aeea94
      由 Johannes Berg 提交于 
      When resuming, it's possible for the following scenario to occur:

 * iwl_pci_resume() enables the RF-kill interrupt
 * iwl_pci_resume() reads the RF-kill state (e.g. to 'radio enabled')
 * RF_KILL interrupt triggers, and iwl_pcie_irq_handler() reads the
   state, now 'radio disabled', and acquires the &trans_pcie->mutex.
 * iwl_pcie_irq_handler() further calls iwl_trans_pcie_rf_kill() to
   indicate to the higher layers that the radio is now disabled (and
   stops the device while at it)
 * iwl_pcie_irq_handler() drops the mutex
 * iwl_pci_resume() continues, acquires the mutex and calls the higher
   layers to indicate that the radio is enabled.

At this point, the device is stopped but the higher layers think it's
available, and can call deeply into the driver to try to enable it.
However, this will fail since the device is actually disabled.
Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      23aeea94
    • S
      iwlwifi: support two phys for a000 devices · 5594d80e
      由 Sara Sharon 提交于 
      Support differentiating between two phys for a000 devices
in order to load the correct firmware.
Eventually when moving completely to the new phy we will be
able to remove this.
Signed-off-by: NSara Sharon <sara.sharon@intel.com>
Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      5594d80e