1. 11 Feb, 2013 5 commits
  2. 04 Feb, 2013 1 commit
    • Johannes Berg's avatar
      mac80211: always allow calling ieee80211_connection_loss() · 682bd38b
      Johannes Berg authored
      With multi-channel, there's a corner case where a driver
      doesn't receive a beacon soon enough to be able to sync
      its timers with the AP. In this case, the only recovery
      (after trying again) is to disconnect from the AP. Allow
      calling ieee80211_connection_loss() for such cases. To
      make that possible, modify the work function to not rely
      on the IEEE80211_HW_CONNECTION_MONITOR flag but use new
      state kept in the interface instead.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      682bd38b
  3. 31 Jan, 2013 3 commits
    • Johannes Berg's avatar
      mac80211: start auth/assoc timeout on frame status · 1672c0e3
      Johannes Berg authored
      When sending authentication/association frames they
      might take a bit of time to go out because we may
      have to synchronise with the AP, in particular in
      the case where it's really a P2P GO. In this case
      the 200ms fixed timeout could potentially be too
      short if the beacon interval is relatively large.
      
      For drivers that report TX status we can do better.
      Instead of starting the timeout directly, start it
      only when the frame status arrives. Since then the
      frame was out on the air, we can wait shorter (the
      typical response time is supposed to be 30ms, wait
      100ms.) Also, if the frame failed to be transmitted
      try again right away instead of waiting.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      1672c0e3
    • Emmanuel Grumbach's avatar
      mac80211: inform the driver about update of dtim_period · c65dd147
      Emmanuel Grumbach authored
      Currently, when the driver requires the DTIM period,
      mac80211 will wait to hear a beacon before association.
      This behavior is suboptimal since some drivers may be
      able to deal with knowing the DTIM period after the
      association, if they get it at all.
      
      To address this, notify the drivers with bss_info_changed
      with the new BSS_CHANGED_DTIM_PERIOD flag when the DTIM
      becomes known. This might be when changing to associated,
      or later when the entire association was done with only
      probe response information.
      
      Rename the hardware flag for the current behaviour to
      IEEE80211_HW_NEED_DTIM_BEFORE_ASSOC to more accurately
      reflect its behaviour. IEEE80211_HW_NEED_DTIM_PERIOD is
      no longer accurate as all drivers get the DTIM period
      now, just not before association.
      Signed-off-by: default avatarEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      c65dd147
    • Johannes Berg's avatar
      cfg80211/mac80211: support reporting wakeup reason · cd8f7cb4
      Johannes Berg authored
      When waking up from WoWLAN, it is useful to know
      what triggered the wakeup. Support reporting the
      wakeup reason(s) in cfg80211 (and a pass-through
      in mac80211) to allow userspace to know.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      cd8f7cb4
  4. 29 Jan, 2013 1 commit
  5. 24 Jan, 2013 1 commit
  6. 18 Jan, 2013 3 commits
  7. 16 Jan, 2013 2 commits
  8. 03 Jan, 2013 3 commits
    • Johannes Berg's avatar
      wireless: use __aligned · 1c06ef98
      Johannes Berg authored
      Use __aligned(...) instead of __attribute__((aligned(...)))
      in mac80211 and cfg80211.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      1c06ef98
    • Johannes Berg's avatar
      mac80211: split TX aggregation stop action · 18b559d5
      Johannes Berg authored
      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: default avatarJohannes Berg <johannes.berg@intel.com>
      18b559d5
    • Johannes Berg's avatar
      mac80211: fix channel context iteration · 8a61af65
      Johannes Berg authored
      During suspend/resume channel contexts might be
      iterated even if they haven't been re-added to
      the driver, keep track of this and skip them in
      iteration. Also use the new status for sanity
      checks.
      
      Also clarify the fact that during HW restart all
      contexts are iterated over (thanks Eliad.)
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      8a61af65
  9. 05 Dec, 2012 1 commit
  10. 03 Dec, 2012 1 commit
  11. 30 Nov, 2012 1 commit
  12. 27 Nov, 2012 1 commit
  13. 26 Nov, 2012 4 commits
  14. 21 Nov, 2012 1 commit
  15. 19 Nov, 2012 2 commits
  16. 13 Nov, 2012 1 commit
  17. 09 Nov, 2012 2 commits
    • Johannes Berg's avatar
      mac80211: clarify interface iteration and make it configurable · 8b2c9824
      Johannes Berg authored
      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: default avatarJohannes Berg <johannes.berg@intel.com>
      8b2c9824
    • Johannes Berg's avatar
      mac80211: call driver method when restart completes · 9214ad7f
      Johannes Berg authored
      When the driver requests a restart (reconfiguration) it
      gets all the normal method calls, but can't really tell
      why they're happening. Call a new restart_complete op
      in the driver when the restart completes, so it could
      keep its own state about the restart and clear it there.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      9214ad7f
  18. 06 Nov, 2012 1 commit
  19. 30 Oct, 2012 1 commit
    • Johannes Berg's avatar
      mac80211: handle TX power per virtual interface · 1ea6f9c0
      Johannes Berg authored
      Even before channel contexts/multi-channel, having a
      single global TX power limit was already problematic,
      in particular if two managed interfaces connected to
      two APs with different power constraints. The channel
      context introduction completely broke this though and
      in fact I had disabled TX power configuration there
      for drivers using channel contexts.
      
      Change everything to track TX power per interface so
      that different user settings and different channel
      maxima are treated correctly. Also continue tracking
      the global TX power though for compatibility with
      applications that attempt to configure the wiphy's
      TX power globally.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      1ea6f9c0
  20. 26 Oct, 2012 1 commit
  21. 23 Oct, 2012 1 commit
  22. 18 Oct, 2012 1 commit
  23. 17 Oct, 2012 2 commits