From: Arend van Spriel <arend@broadcom.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Arend van Spriel <arend@broadcom.com>
Subject: [PATCH V2 0/7] brcmfmac: nvram loading and code rework
Date: Sun, 16 Aug 2015 08:55:32 +0200 [thread overview]
Message-ID: <1439708139-7527-1-git-send-email-arend@broadcom.com> (raw)
This series comprises of following changes:
- support NVRAM loading for bcm47xx platform.
- revise announced interface combinations and validate against it.
- new debugfs entry for msgbuf protocol layer used with PCIe devices.
- couple of PCIe fixes.
- support more firmware events (for bcm4339 firmware).
The series is intended for v4.3 kernel and applies to the master branch
of the wireless-drivers-next repository.
Arend van Spriel (3):
brcmfmac: correct interface combination info
brcmfmac: make use of cfg80211_check_combinations()
brcmfmac: bump highest event number for 4339 firmware
Franky Lin (2):
brcmfmac: add debugfs entry for msgbuf statistics
brcmfmac: block the correct flowring when backup queue overflow
Hante Meuleman (2):
brcmfmac: Add support for host platform NVRAM loading.
brcmfmac: Increase nr of supported flowrings.
drivers/net/wireless/brcm80211/brcmfmac/cfg80211.c | 195 ++++++++++++++++-----
drivers/net/wireless/brcm80211/brcmfmac/firmware.c | 40 +++--
drivers/net/wireless/brcm80211/brcmfmac/flowring.c | 48 ++---
drivers/net/wireless/brcm80211/brcmfmac/flowring.h | 20 +--
drivers/net/wireless/brcm80211/brcmfmac/fweh.h | 10 +-
drivers/net/wireless/brcm80211/brcmfmac/msgbuf.c | 67 ++++++-
drivers/net/wireless/brcm80211/brcmfmac/msgbuf.h | 2 +-
7 files changed, 289 insertions(+), 93 deletions(-)
--
1.9.1
next reply other threads:[~2015-08-16 6:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-16 6:55 Arend van Spriel [this message]
2015-08-16 6:55 ` [PATCH V2 1/7] brcmfmac: Add support for host platform NVRAM loading Arend van Spriel
2015-08-19 16:38 ` Rafał Miłecki
2015-08-19 20:55 ` Arend van Spriel
2015-08-20 19:50 ` Arend van Spriel
2015-08-24 19:28 ` Kalle Valo
2015-08-16 6:55 ` [PATCH V2 2/7] brcmfmac: correct interface combination info Arend van Spriel
2015-08-19 21:49 ` Rafał Miłecki
2015-08-19 21:59 ` Arend van Spriel
2015-08-16 6:55 ` [PATCH V2 3/7] brcmfmac: Increase nr of supported flowrings Arend van Spriel
2015-08-19 21:56 ` Rafał Miłecki
2015-08-24 14:15 ` Arend van Spriel
2015-08-24 20:02 ` Rafał Miłecki
2015-08-29 8:13 ` Arend van Spriel
2015-08-29 9:38 ` Rafał Miłecki
2015-08-29 10:48 ` Arend van Spriel
2015-08-20 16:16 ` Rafał Miłecki
2015-08-20 16:39 ` Arend van Spriel
2015-08-16 6:55 ` [PATCH V2 4/7] brcmfmac: add debugfs entry for msgbuf statistics Arend van Spriel
2015-08-16 6:55 ` [PATCH V2 5/7] brcmfmac: make use of cfg80211_check_combinations() Arend van Spriel
2015-08-16 6:55 ` [PATCH V2 6/7] brcmfmac: block the correct flowring when backup queue overflow Arend van Spriel
2015-08-16 6:55 ` [PATCH V2 7/7] brcmfmac: bump highest event number for 4339 firmware Arend van Spriel
2015-08-16 15:10 ` [PATCH V2 0/7] brcmfmac: nvram loading and code rework Rafał Miłecki
2015-08-17 8:01 ` Arend van Spriel
2015-08-17 14:25 ` Rafał Miłecki
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=1439708139-7527-1-git-send-email-arend@broadcom.com \
--to=arend@broadcom.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
/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).