From: Angus Ainslie <angus@akkea.ca>
To: kernel@puri.sm
Cc: Arend van Spriel <aspriel@gmail.com>,
Franky Lin <franky.lin@broadcom.com>,
Kalle Valo <kvalo@codeaurora.org>,
linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
linux-bluetooth@vger.kernel.org, Angus Ainslie <angus@akkea.ca>
Subject: [PATCH v3 0/2] Add BCM43752 chipset support
Date: Thu, 12 Aug 2021 09:52:16 -0700 [thread overview]
Message-ID: <20210812165218.2508258-1-angus@akkea.ca> (raw)
The SparkLan AP6275 SDIO M.2 card contains a BCM43752 based module and these
patches were tested with that card.
This was tested on the 5.13 kernel with a minor substition BRCMF_FW_DEF for
BRCMF_FW_CLM_DEF.
It should apply and build on the wireless-next branch.
Changes since v2:
Squashed patches 1 and 2.
Fixed bluetooth patch subject.
Changes since v1:
Add bluetooth patchram definition
Angus Ainslie (2):
brcmfmac: add 43752 SDIO ids and initialization
btbcm: add patch ram for bluetooth
drivers/bluetooth/btbcm.c | 1 +
drivers/net/wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c | 1 +
drivers/net/wireless/broadcom/brcm80211/brcmfmac/chip.c | 3 +++
drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c | 8 ++++++--
.../net/wireless/broadcom/brcm80211/include/brcm_hw_ids.h | 1 +
include/linux/mmc/sdio_ids.h | 1 +
6 files changed, 13 insertions(+), 2 deletions(-)
--
2.25.1
next reply other threads:[~2021-08-12 16:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 16:52 Angus Ainslie [this message]
2021-08-12 16:52 ` [PATCH v3 1/2] brcmfmac: add 43752 SDIO ids and initialization Angus Ainslie
2021-08-12 17:29 ` Add BCM43752 chipset support bluez.test.bot
2021-08-21 16:59 ` [PATCH v3 1/2] brcmfmac: add 43752 SDIO ids and initialization Kalle Valo
2021-08-12 16:52 ` [PATCH v3 2/2] btbcm: add patch ram for bluetooth Angus Ainslie
2021-08-16 15:58 ` Marcel Holtmann
2021-08-16 21:58 ` Arend van Spriel
2021-08-19 15:26 ` Marcel Holtmann
2021-08-19 15:43 ` 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=20210812165218.2508258-1-angus@akkea.ca \
--to=angus@akkea.ca \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=franky.lin@broadcom.com \
--cc=kernel@puri.sm \
--cc=kvalo@codeaurora.org \
--cc=linux-bluetooth@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.