From: Janaki Ramaiah Thota <quic_janathot@quicinc.com>
To: Johan Hovold <johan@kernel.org>
Cc: Doug Anderson <dianders@chromium.org>,
Johan Hovold <johan+linaro@kernel.org>,
Marcel Holtmann <marcel@holtmann.org>,
"Luiz Augusto von Dentz" <luiz.dentz@gmail.com>,
Matthias Kaehlcke <mka@chromium.org>,
<linux-bluetooth@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<stable@vger.kernel.org>, Stephen Boyd <swboyd@chromium.org>,
<quic_mohamull@quicinc.com>, <quic_hbandi@quicinc.com>
Subject: Re: [PATCH] Bluetooth: qca: fix invalid device address check
Date: Fri, 26 Apr 2024 11:53:45 +0530 [thread overview]
Message-ID: <bb0e1baf-7e64-463a-8638-d403c7a29317@quicinc.com> (raw)
In-Reply-To: <Zip9vMHa2x-uW-pf@hovoldconsulting.com>
On 4/25/2024 9:28 PM, Johan Hovold wrote:
> Hi Janaki,
>
> On Thu, Apr 25, 2024 at 08:31:50PM +0530, Janaki Ramaiah Thota wrote:
>
>> Apologies for the delay. As of now, we have observed the following
>> values in the upstream firmware files for default BD addresses.
>> We will confirm ASAP if there are any changes.
>>
>> ---------------------------------------------------------
>> | BDA | Chipset |
>> ---------------------------------------------------------
>> | 20 00 00 10 80 39 | WCN3988 with ROM Version 0x0200 |
>> ---------------------------------------------------------
>> | 00 08 74 12 80 39 | WCN3988 with ROM Version 0x0201 |
>> ---------------------------------------------------------
>> | 00 07 64 21 90 39 | WCN3990 |
>> ---------------------------------------------------------
>
> Thanks a lot for these. I see now that the default Trogdor address Doug
> reported (39:98:00:00:5a:ad) appears to comes from the fw too:
>
> $ od -x crnv32.bin | grep 5aad
>
> 0000020 0000 0000 5aad 0000 3998 0008 0008 0000
>
> which means that patch I sent this morning should be all that is needed
> for those machines at least.
>
Yes correct, it will work for Trogdor
> Can you please confirm that all the WCN39xx have OTP storage for an
> address that an OEM can choose to use?
>
We are checking with internal FW team, will confirm on it.
> If that's not the case then we could simplify things by always marking
> their addresses as invalid, but I assume that they all have address
> storage.
>
> Johan
-Janakiram
next prev parent reply other threads:[~2024-04-26 6:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 9:15 Johan Hovold
2024-04-16 15:10 ` patchwork-bot+bluetooth
2024-04-22 17:50 ` Doug Anderson
2024-04-23 9:08 ` Johan Hovold
2024-04-23 15:09 ` Doug Anderson
2024-04-25 8:40 ` Johan Hovold
2024-04-25 15:01 ` Janaki Ramaiah Thota
2024-04-25 15:58 ` Johan Hovold
2024-04-26 6:23 ` Janaki Ramaiah Thota [this message]
2024-04-26 10:42 ` Janaki Ramaiah Thota
2024-04-26 12:45 ` Johan Hovold
2024-04-26 14:15 ` Johan Hovold
2024-04-25 15:22 ` Doug Anderson
2024-04-25 16:13 ` Johan Hovold
2024-04-25 16:19 ` Doug Anderson
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=bb0e1baf-7e64-463a-8638-d403c7a29317@quicinc.com \
--to=quic_janathot@quicinc.com \
--cc=dianders@chromium.org \
--cc=johan+linaro@kernel.org \
--cc=johan@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=mka@chromium.org \
--cc=quic_hbandi@quicinc.com \
--cc=quic_mohamull@quicinc.com \
--cc=stable@vger.kernel.org \
--cc=swboyd@chromium.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
all inboxes | Powered by JetHome®