1. 07 Jan, 2013 4 commits
  2. 03 Dec, 2012 1 commit
  3. 30 Nov, 2012 4 commits
  4. 26 Nov, 2012 2 commits
    • Johannes Berg's avatar
      cfg80211: pass a channel definition struct · 683b6d3b
      Johannes Berg authored
      Instead of passing a channel pointer and channel type
      to all functions and driver methods, pass a new channel
      definition struct. Right now, this struct contains just
      the control channel and channel type, but for VHT this
      will change.
      Also, add a small inline cfg80211_get_chandef_type() so
      that drivers don't need to use the _type field of the
      new structure all the time, which will change.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
    • Johannes Berg's avatar
      cfg80211: remove remain-on-channel channel type · 42d97a59
      Johannes Berg authored
      As mwifiex (and mac80211 in the software case) are the
      only drivers actually implementing remain-on-channel
      with channel type, userspace can't be relying on it.
      This is the case, as it's used only for P2P operations
      right now.
      Rather than adding a flag to tell userspace whether or
      not it can actually rely on it, simplify all the code
      by removing the ability to use different channel types.
      Leave only the validation of the attribute, so that if
      we extend it again later (with the needed capability
      flag), it can't break userspace sending invalid data.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
  5. 16 Nov, 2012 3 commits
  6. 14 Nov, 2012 3 commits
    • Bing Zhao's avatar
      mwifiex: process RX packets in SDIO IRQ thread directly · 601216e1
      Bing Zhao authored
      ksdioirqd has higher priority than kworker. Process RX packets
      in SDIO IRQ thread (ksdioirqd/mmcX) directly instead of deferring
      the work to kworker to avoid the extra latency.
      This improves TCP throughput 15~20% on an ARM platform with SDIO
      2.0 controller.
      Signed-off-by: default avatarBing Zhao <bzhao@marvell.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
    • Avinash Patil's avatar
      mwifiex: add multi-queue support · 47411a06
      Avinash Patil authored
      This patch adds support for multiple TX queues inside mwifiex
      driver. Four different queues according to WMM access categories
      are defined for each virtual interface. When a packet is
      received from netdev for transmission, tx pending count for
      particular queue is incremented and if tx pending count has
      reached upper water-mark, this queue is stopped instead of
      stopping all queues. Similarly when a packet is successfully
      transmitted from device, tx pending count is decremented per
      queue and if pending count falls below lower water-mark, queue
      operations are again resumed. This ensures that not all
      tranmission is blocked if traffic with particular TOS value
      suddenly increases.
      Also wake all queues after association/IBSS_join/uAP_BSS_start
      to enable traffic on all queues.
      Signed-off-by: default avatarAvinash Patil <patila@marvell.com>
      Signed-off-by: default avatarBing Zhao <bzhao@marvell.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
    • Amitkumar Karwar's avatar
      mwifiex: add support for SDIO card reset · d31ab357
      Amitkumar Karwar authored
      When command timeout happens due to a bug in firmware/hardware,
      the timeout handler just prints some debug information. User is
      unable to reload the driver in this case.
      Inspired by 9a821f5d
       "libertas: add sd8686 reset_card support",
      this patch adds card reset support for SDIO interface when
      command timeout happens. If the SDIO host contoller supports
      MMC_POWER_OFF|UP|ON operations, the chip will be reset and the
      firmware will be re-downloaded.
      Signed-off-by: default avatarAmitkumar Karwar <akarwar@marvell.com>
      Signed-off-by: default avatarBing Zhao <bzhao@marvell.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
  7. 30 Oct, 2012 1 commit
    • Johannes Berg's avatar
      cfg80211: allow per interface TX power setting · c8442118
      Johannes Berg authored
      The TX power setting is currently per wiphy (hardware
      device) but with multi-channel capabilities that doesn't
      make much sense any more.
      Allow drivers (and mac80211) to advertise support for
      per-interface TX power configuration. When the TX power
      is configured for the wiphy, the wdev will be NULL and
      the driver can still handle that, but when a wdev is
      given the TX power can be set only for that wdev now.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
  8. 29 Oct, 2012 7 commits
  9. 24 Oct, 2012 2 commits
  10. 19 Oct, 2012 2 commits
  11. 18 Oct, 2012 2 commits
    • Arend van Spriel's avatar
      wireless: drivers: make use of WLAN_EID_VENDOR_SPECIFIC · 04b2312a
      Arend van Spriel authored
      The include file linux/ieee80211.h contains three definitions for
      the same thing in enum ieee80211_eid due to historic changes:
      /* Information Element IDs */
      enum ieee80211_eid {
          WLAN_EID_WPA = 221,
          WLAN_EID_GENERIC = 221,
      The standard refers to this as "vendor specific" element so the
      other two definitions are better not used. This patch changes the
      wireless drivers to use one definition, ie. WLAN_EID_VENDOR_SPECIFIC.
      Cc: Jouni Malinen <j@w1.fi>
      Cc: Dan Williams <dcbw@redhat.com>
      Cc: Larry Finger <Larry.Finger@lwfinger.net>
      Acked-by: Kalle Valo <kvalo@qca.qualcomm.com> [ath6kl]
      Acked-by: Bing Zhao <bzhao@marvell.com> [mwifiex]
      Acked-by: Stanislav Yakovlev <stas.yakovlev@gmail.com> [ipw2x00]
      Signed-off-by: default avatarArend van Spriel <arend@broadcom.com>
      [change libipw as well]
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
    • Johannes Berg's avatar
      wireless: use OR operation to set wiphy features · b292219f
      Johannes Berg authored
      The next patch will introduce a flag that is set
      by default in cfg80211 so drivers and mac80211
      need to use |= to set features they have so that
      they don't clear the already-set feature.
      We could set the flag in wiphy_register() instead
      of wiphy_new() to avoid this patch, but then the
      drivers couldn't *unset* flags they don't want to
      use even though the implementation is generic.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
  12. 08 Oct, 2012 4 commits
  13. 28 Sep, 2012 5 commits