Linux wireless drivers development
 help / color / mirror / Atom feed
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,
	Angus Ainslie <angus@akkea.ca>
Subject: [PATCH v2 0/3] Add BCM43752 chipset support
Date: Wed, 11 Aug 2021 08:28:01 -0700	[thread overview]
Message-ID: <20210811152804.2379405-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 v1:

Add bluetooth patchram definition

Angus Ainslie (3):
  brcmfmac: add 43752 device ids
  brcmfmac: add initializers for the 43752
  brcmfmac: 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


             reply	other threads:[~2021-08-11 15:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11 15:28 Angus Ainslie [this message]
2021-08-11 15:28 ` [PATCH v2 1/3] brcmfmac: add 43752 device ids Angus Ainslie
2021-08-11 15:28 ` [PATCH v2 2/3] brcmfmac: add initializers for the 43752 Angus Ainslie
2021-08-12 11:36   ` Arend van Spriel
2021-08-11 15:28 ` [PATCH v2 3/3] brcmfmac: add patch ram for bluetooth Angus Ainslie
2021-08-12 11:40   ` Arend van Spriel
2021-08-12 11:42     ` Arend van Spriel
2021-08-12 13:01       ` Angus Ainslie

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=20210811152804.2379405-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-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