Linux wireless drivers development
 help / color / mirror / Atom feed
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Angus Ainslie <angus@akkea.ca>, 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
Subject: Re: [PATCH v2 3/3] brcmfmac: add patch ram for bluetooth
Date: Thu, 12 Aug 2021 13:40:15 +0200	[thread overview]
Message-ID: <d7d7fa89-916e-203a-8e7d-07cf88aa3fd1@broadcom.com> (raw)
In-Reply-To: <20210811152804.2379405-4-angus@akkea.ca>

[-- Attachment #1: Type: text/plain, Size: 1689 bytes --]

On 8/11/2021 5:28 PM, Angus Ainslie wrote:
> Bluetooth on the BCM43752 needs a patchram file to function correctly.

this patch is dealing with bluetooth so you should add the proper 
mailing list.

> Signed-off-by: Angus Ainslie <angus@akkea.ca>
> ---
>   drivers/bluetooth/btbcm.c | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/bluetooth/btbcm.c b/drivers/bluetooth/btbcm.c
> index e5d706ed55ea..e4182acee488 100644
> --- a/drivers/bluetooth/btbcm.c
> +++ b/drivers/bluetooth/btbcm.c
> @@ -387,6 +387,7 @@ struct bcm_subver_table {
>   };
>   
>   static const struct bcm_subver_table bcm_uart_subver_table[] = {
> +	{ 0x1111, "BCM4362A2"	},	/* 000.017.017 */

This seems odd. 4362 vs 43752? What is the story here?

Regards,
Arend

>   	{ 0x4103, "BCM4330B1"	},	/* 002.001.003 */
>   	{ 0x410d, "BCM4334B0"	},	/* 002.001.013 */
>   	{ 0x410e, "BCM43341B0"	},	/* 002.001.014 */
> 

-- 
This electronic communication and the information and any files transmitted 
with it, or attached to it, are confidential and are intended solely for 
the use of the individual or entity to whom it is addressed and may contain 
information that is confidential, legally privileged, protected by privacy 
laws, or otherwise restricted from disclosure to anyone else. If you are 
not the intended recipient or the person responsible for delivering the 
e-mail to the intended recipient, you are hereby notified that any use, 
copying, distributing, dissemination, forwarding, printing, or copying of 
this e-mail is strictly prohibited. If you received this e-mail in error, 
please return the e-mail to the sender, delete it from your computer, and 
destroy any printed copy of it.

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4219 bytes --]

  reply	other threads:[~2021-08-12 11:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11 15:28 [PATCH v2 0/3] Add BCM43752 chipset support Angus Ainslie
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 [this message]
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=d7d7fa89-916e-203a-8e7d-07cf88aa3fd1@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --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=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