Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Arend van Spriel <aspriel@gmail.com>
To:     Marcel Holtmann <marcel@holtmann.org>,
        Arend van Spriel <arend.vanspriel@broadcom.com>
CC:     Angus Ainslie <angus@akkea.ca>, <kernel@puri.sm>,
        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>
Date:   Thu, 19 Aug 2021 17:43:38 +0200
Message-ID: <17b5f150410.279b.9696ff82abe5fb6502268bdc3b0467d4@gmail.com>
In-Reply-To: <5766C95B-D5A4-463C-A87F-41B35BF82046@holtmann.org>
References: <20210812165218.2508258-1-angus@akkea.ca>
 <20210812165218.2508258-3-angus@akkea.ca>
 <1cd0e008-9239-f430-7294-865d34795a2f@broadcom.com>
 <5766C95B-D5A4-463C-A87F-41B35BF82046@holtmann.org>
User-Agent: AquaMail/1.30.1-1828 (build: 103001000)
Subject: Re: [PATCH v3 2/2] btbcm: add patch ram for bluetooth
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="us-ascii"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On August 19, 2021 5:26:42 PM Marcel Holtmann <marcel@holtmann.org> wrote:

> 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?

I will check although not internally as this is probably a Cypress chipset. 
Anyway, I will follow up on this.

Regards,
Arend