linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Arend van Spriel <arend@broadcom.com>
Subject: [PATCH 0/8] brcmfmac: new USB devices, vendor command, and cleanup
Date: Sat, 21 Jun 2014 12:11:11 +0200	[thread overview]
Message-ID: <1403345479-13467-1-git-send-email-arend@broadcom.com> (raw)

The patch series add driver support for new USB device. These are 11ac fullmac
devices with USB3.0 interface. Also opting for the vendor-specific netlink
command instead of cfg80211 testmode. The remaining patches are small cleanup
patches.

This series is intended for 3.17 and applies to the master branch of the
wireless-next repository.

Arend van Spriel (3):
  brcmfmac: clear ht info during attach phase
  brcmfmac: correct logging levels in btcoex source
  brcmfmac: reduce log level in fwil if firmware returns error

Daniel Kim (1):
  brcmfmac: Don't control mpc setting during scan operation

Franky Lin (1):
  brcmfmac: replace cfg80211 testmode with vendor command

Hante Meuleman (3):
  brcmfmac: Add 43569 USB support.
  brcmfmac: Add USB device 43566 to supported devices.
  brcmfmac: Change USB probe routine to support Composite USB

 drivers/net/wireless/brcm80211/brcmfmac/Makefile   |    3 +-
 drivers/net/wireless/brcm80211/brcmfmac/btcoex.c   |   38 ++--
 drivers/net/wireless/brcm80211/brcmfmac/dhd.h      |   10 -
 .../net/wireless/brcm80211/brcmfmac/dhd_common.c   |    7 +
 drivers/net/wireless/brcm80211/brcmfmac/fwil.c     |    2 +-
 drivers/net/wireless/brcm80211/brcmfmac/usb.c      |  214 +++++++++-----------
 drivers/net/wireless/brcm80211/brcmfmac/vendor.c   |  115 +++++++++++
 drivers/net/wireless/brcm80211/brcmfmac/vendor.h   |   64 ++++++
 .../net/wireless/brcm80211/brcmfmac/wl_cfg80211.c  |   56 ++---
 9 files changed, 326 insertions(+), 183 deletions(-)
 create mode 100644 drivers/net/wireless/brcm80211/brcmfmac/vendor.c
 create mode 100644 drivers/net/wireless/brcm80211/brcmfmac/vendor.h

-- 
1.7.9.5


             reply	other threads:[~2014-06-21 10:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-21 10:11 Arend van Spriel [this message]
2014-06-21 10:11 ` [PATCH 1/8] brcmfmac: Add 43569 USB support Arend van Spriel
2014-06-21 10:11 ` [PATCH 2/8] brcmfmac: Add USB device 43566 to supported devices Arend van Spriel
2014-06-21 15:55   ` Rafał Miłecki
2014-06-21 16:56     ` Arend van Spriel
2014-06-21 10:11 ` [PATCH 3/8] brcmfmac: clear ht info during attach phase Arend van Spriel
2014-06-21 10:11 ` [PATCH 4/8] brcmfmac: Change USB probe routine to support Composite USB Arend van Spriel
2014-06-21 10:11 ` [PATCH 5/8] brcmfmac: replace cfg80211 testmode with vendor command Arend van Spriel
2014-06-21 10:11 ` [PATCH 6/8] brcmfmac: correct logging levels in btcoex source Arend van Spriel
2014-06-21 10:11 ` [PATCH 7/8] brcmfmac: Don't control mpc setting during scan operation Arend van Spriel
2014-06-21 10:11 ` [PATCH 8/8] brcmfmac: reduce log level in fwil if firmware returns error Arend van Spriel
2014-06-21 15:58 ` [PATCH 0/8] brcmfmac: new USB devices, vendor command, and cleanup Rafał Miłecki
2014-06-21 16:48   ` Arend van Spriel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1403345479-13467-1-git-send-email-arend@broadcom.com \
    --to=arend@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).