All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Angus Ainslie <angus@akkea.ca>
Cc: kernel@puri.sm, Arend van Spriel <aspriel@gmail.com>,
	Franky Lin <franky.lin@broadcom.com>,
	linux-wireless@vger.kernel.org,
	brcm80211-dev-list.pdl@broadcom.com,
	linux-bluetooth@vger.kernel.org, Angus Ainslie <angus@akkea.ca>
Subject: Re: [PATCH v3 1/2] brcmfmac: add 43752 SDIO ids and initialization
Date: Sat, 21 Aug 2021 16:59:46 +0000 (UTC)	[thread overview]
Message-ID: <20210821165946.33227C43616@smtp.codeaurora.org> (raw)
In-Reply-To: <20210812165218.2508258-2-angus@akkea.ca>

Angus Ainslie <angus@akkea.ca> wrote:

> Add HW and SDIO ids for use with the SparkLan AP6275S
> Add the firmware mapping structures for the BRCM43752 chipset.
> The 43752 needs some things setup similar to the 43012 chipset.
> The WATERMARK shows better performance when initialized to the 4373 value.
> 
> Signed-off-by: Angus Ainslie <angus@akkea.ca>

Patch applied to wireless-drivers-next.git, thanks.

d2587c57ffd8 brcmfmac: add 43752 SDIO ids and initialization

-- 
https://patchwork.kernel.org/project/linux-wireless/patch/20210812165218.2508258-2-angus@akkea.ca/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


  parent reply	other threads:[~2021-08-21 16:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-12 16:52 [PATCH v3 0/2] Add BCM43752 chipset support Angus Ainslie
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   ` Kalle Valo [this message]
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=20210821165946.33227C43616@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=angus@akkea.ca \
    --cc=aspriel@gmail.com \
    --cc=brcm80211-dev-list.pdl@broadcom.com \
    --cc=franky.lin@broadcom.com \
    --cc=kernel@puri.sm \
    --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.