All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: Angus Ainslie <angus@akkea.ca>,
	kernel@puri.sm, 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
Subject: Re: [PATCH v3 2/2] btbcm: add patch ram for bluetooth
Date: Thu, 19 Aug 2021 17:26:42 +0200	[thread overview]
Message-ID: <5766C95B-D5A4-463C-A87F-41B35BF82046@holtmann.org> (raw)
In-Reply-To: <1cd0e008-9239-f430-7294-865d34795a2f@broadcom.com>

Hi Arend,

>> Bluetooth on the BCM43752 needs a patchram file to function correctly.
>> 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 */
> 
> Noticed Marcel applied this one already, but as I asked in earlier patch I would like to know why the commit message says 43752 but this entry says 4362? Still confused.

seems I missed that part. Can you look internally what this hardware is and we fix it?

Regards

Marcel


  reply	other threads:[~2021-08-19 15:26 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   ` [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 [this message]
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=5766C95B-D5A4-463C-A87F-41B35BF82046@holtmann.org \
    --to=marcel@holtmann.org \
    --cc=angus@akkea.ca \
    --cc=arend.vanspriel@broadcom.com \
    --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.