1. 23 5月, 2013 1 次提交
  2. 11 4月, 2013 1 次提交
  3. 26 3月, 2013 1 次提交
  4. 03 1月, 2013 1 次提交
    • J
      mac80211: split TX aggregation stop action · 18b559d5
      Johannes Berg 提交于
      When TX aggregation is stopped, there are a few
      different cases:
       - connection with the peer was dropped
       - session stop was requested locally
       - session stop was requested by the peer
       - connection was dropped while a session is stopping
      
      The behaviour in these cases should be different, if
      the connection is dropped then the driver should drop
      all frames, otherwise the frames may continue to be
      transmitted, aggregated in the case of a locally
      requested session stop or unaggregated in the case of
      the peer requesting session stop.
      
      Split these different cases so that the driver can
      act accordingly; however, treat local and remote stop
      the same way and ask the driver to not send frames as
      aggregated packets any more.
      
      In the case of connection drop, the stop callback the
      driver is otherwise supposed to call is no longer
      required.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      18b559d5
  5. 22 11月, 2012 1 次提交
  6. 10 11月, 2012 1 次提交
    • J
      mac80211: clarify interface iteration and make it configurable · 8b2c9824
      Johannes Berg 提交于
      During hardware restart, all interfaces are iterated even
      though they haven't been re-added to the driver, document
      this behaviour. The same also happens during resume, which
      is even more confusing since all of the interfaces were
      previously removed from the driver. Make this optional so
      drivers relying on the current behaviour can still use it,
      but to let drivers that don't want this behaviour disable
      it.
      
      Also convert all API users, keeping the old semantics
      except in hwsim, where the new normal ones are desired.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      8b2c9824
  7. 30 10月, 2012 1 次提交
  8. 12 9月, 2012 1 次提交
  9. 10 9月, 2012 1 次提交
    • J
      mac80211: add key flag for management keys · e548c49e
      Johannes Berg 提交于
      Mark keys that might be used to receive management
      frames so drivers can fall back on software crypto
      for them if they don't support hardware offload.
      As the new flag is only set correctly for RX keys
      and the existing IEEE80211_KEY_FLAG_SW_MGMT flag
      can only affect TX, also rename the latter to
      IEEE80211_KEY_FLAG_SW_MGMT_TX.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      e548c49e
  10. 22 8月, 2012 1 次提交
  11. 31 7月, 2012 1 次提交
  12. 18 7月, 2012 2 次提交
  13. 27 6月, 2012 2 次提交
  14. 21 6月, 2012 1 次提交
  15. 16 3月, 2012 1 次提交
  16. 28 2月, 2012 1 次提交
  17. 25 1月, 2012 1 次提交
  18. 20 12月, 2011 2 次提交
  19. 08 12月, 2011 1 次提交
    • N
      ath9k: use config.enable_ani to check if ani should be performed · 4279425c
      Nikolay Martynov 提交于
        Currently in ath9k code there is an attempt which is meant to
      disable ANI for ar9100 and ar9340. But it doesn't really achieve
      this. All it does is disable ANI init and setup (i.e. calls to
      ath9k_hw_ani_setup and ath9k_hw_ani_init). Since ath9k_hw_ani_setup is
      not called ah->config.ani_poll_interval is never initialized (i.e. it
      is always zero) and ath_ani_calibrate always executes ANI procedures
      (over uninitialized ANI parameters).
        Moreover, ath_ani_calibrate is being called each 1ms because
      common->ani.timer is set to zero interval because
      ah->config.ani_poll_interval==0 (and thus smallest value of all
      intervals). Normally it should not be called this often.
        This patch changes the code so config.enable_ani is used to check if
      ANI should be performed.
        config.enable_ani is initialized to true by default. This patch sets
      it to false for ar9100 and ar9340.
      Signed-off-by: NNikolay Martynov <mar.kolya@gmail.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      4279425c
  20. 04 10月, 2011 1 次提交
    • E
      mac80211: pass vif param to conf_tx() callback · 8a3a3c85
      Eliad Peller 提交于
      tx params should be configured per interface.
      add ieee80211_vif param to the conf_tx callback,
      and change all the drivers that use this callback.
      
      The following spatch was used:
      @rule1@
      struct ieee80211_ops ops;
      identifier conf_tx_op;
      @@
      	ops.conf_tx = conf_tx_op;
      
      @rule2@
      identifier rule1.conf_tx_op;
      identifier hw, queue, params;
      @@
      	conf_tx_op (
      -		struct ieee80211_hw *hw,
      +		struct ieee80211_hw *hw, struct ieee80211_vif *vif,
      		u16 queue,
      		const struct ieee80211_tx_queue_params *params) {...}
      Signed-off-by: NEliad Peller <eliad@wizery.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      8a3a3c85
  21. 28 9月, 2011 1 次提交
  22. 15 9月, 2011 1 次提交
  23. 30 8月, 2011 1 次提交
    • L
      ath9k: Fix a smatch warnings · 1ba45b9e
      Larry Finger 提交于
      Smatch shows the following warnings:
      
        CHECK   drivers/net/wireless/ath/ath9k/htc_drv_main.c
      drivers/net/wireless/ath/ath9k/htc_drv_main.c +1315 ath9k_htc_configure_filter(27) warn: inconsistent returns mutex:&priv->mutex: locked (1303) unlocked (1315)
      
        CHECK   drivers/net/wireless/ath/ath9k/ar9003_eeprom.c
      drivers/net/wireless/ath/ath9k/ar9003_eeprom.c +3321 ar9300_eeprom_restore_internal(20) warn: returning -1 instead of -ENOMEM is sloppy
      Signed-off-by: NLarry Finger <Larry.Finger@lwfinger.net>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      1ba45b9e
  24. 26 8月, 2011 1 次提交
  25. 08 7月, 2011 1 次提交
  26. 20 5月, 2011 6 次提交
  27. 30 4月, 2011 1 次提交
  28. 29 4月, 2011 1 次提交
  29. 26 4月, 2011 4 次提交