1. 01 2月, 2016 5 次提交
  2. 08 1月, 2016 2 次提交
  3. 21 12月, 2015 4 次提交
  4. 20 12月, 2015 1 次提交
  5. 16 12月, 2015 1 次提交
    • S
      iwlwifi: mvm: change protocol offload flows · c97dab40
      Sara Sharon 提交于
      RFC4862 states that "In all cases, a node MUST NOT respond to
      a Neighbor Solicitation for a tentative address".
      Currently the driver configures the NS offload and does not wait
      for address to become permanent, thus violating the RFC.
      Just removing the address from the address list is not good enough
      for all cases, since the NS messages are needed for the duplicate
      address detection and should not be discarded.
      
      For d0i3 disable NS offload. Put tentative address in the address
      list so the NS packet will not be filtered out by ucode.
      For D3 the platform will not wake from NS packets - so enable
      NS offload while removing the tentative address from the list.
      
      Given that now NS offload might be disabled, and that the ucode
      uses the IP data for other puroposes (L3 filtering) add two
      independent flags indicating if IPv4\IPv6 data is valid.
      Signed-off-by: NSara Sharon <sara.sharon@intel.com>
      Signed-off-by: NEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      c97dab40
  6. 13 12月, 2015 3 次提交
    • L
      iwlwifi: replace d0i3_mode and wowlan_d0i3 with more generic variables · b7282643
      Luca Coelho 提交于
      The d0i3_mode variable is used to distinguish between transports that
      handle d0i3 entry during suspend by themselves (i.e. the slave
      transports) and those which rely on the op_mode layer to do it.  The
      reason why the former do it by themselves is that they need to
      transition from d0i3 in runtime_suspend into d0i3 in system-wide
      suspend and this transition needs to happen before the op_mode's
      suspend flow is called.
      
      The wowlan_d0i3 element is also a bit confusing, because it just
      reflects the wowlan->any value for the trans to understand.  This is a
      bit unclear in the code and not generic enough for future use.
      
      To make it clearer and to generalize the platform power mode settings,
      introduce two variables to indicate the platform power management
      modes used by the transport.
      
      Additionally, in order not to take too big a step in one patch, treat
      this new variables semantically in the same way as the old d0i3_mode
      element, introducing a iwl_mvm_enter_d0i3_on_suspend() function to
      help with that.
      
      This commit also adds the foundation for a new concept where the
      firmware configuration state (i.e. D0, D3 or D0i3) is abstracted from
      the platform PM mode we are in (i.e. runtime suspend or system-wide
      suspend).
      Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      Signed-off-by: NEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      b7282643
    • E
      iwlwifi: avoid d0i3 commands when no/init ucode is loaded · 08f0d23d
      Eliad Peller 提交于
      d0i3 commands are not supported in the init image, so take
      a reference to ensure we don't enter d0i3 during init image,
      and additional checks to prevent d0i3 commands when no
      fw image is loaded.
      
      Add a few WARN_ON_ONCE to the d0i3 enter/exit commands
      to ensure we send d0i3 commands only when the normal
      ucode is loaded.
      Signed-off-by: NEliad Peller <eliadx.peller@intel.com>
      Signed-off-by: NEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      08f0d23d
    • A
      iwlwifi: mvm: configure scheduled scan according to traffic conditions · 355346ba
      Avraham Stern 提交于
      Change scan configuration (dwell time, suspend time etc.) according
      to traffic conditions. This is useful for scans that are managed by
      the FW (e.g. scheduled scan).
      Signed-off-by: NAvraham Stern <avraham.stern@intel.com>
      Signed-off-by: NEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      355346ba
  7. 02 12月, 2015 2 次提交
  8. 26 11月, 2015 8 次提交
  9. 18 11月, 2015 1 次提交
  10. 25 10月, 2015 1 次提交
  11. 05 10月, 2015 6 次提交
  12. 04 10月, 2015 1 次提交
  13. 28 8月, 2015 3 次提交
  14. 16 8月, 2015 1 次提交
  15. 05 8月, 2015 1 次提交