From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sherry Sun <sherry.sun@nxp.com>,
Neeraj Sanjay Kale <neeraj.sanjaykale@nxp.com>,
"marcel@holtmann.org" <marcel@holtmann.org>,
"luiz.dentz@gmail.com" <luiz.dentz@gmail.com>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>
Cc: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Amitkumar Karwar <amitkumar.karwar@nxp.com>,
Manjeet Gupta <manjeet.gupta@nxp.com>
Subject: Re: [PATCH v1 2/2] Bluetooth: btnxpuart: Add support for 4M baudrate
Date: Tue, 17 Jun 2025 08:43:19 +0200 [thread overview]
Message-ID: <6fe27c9d-4641-4aba-9e34-686a4d7f1fa8@kernel.org> (raw)
In-Reply-To: <DB9PR04MB8429D531C76CD31AF66864419273A@DB9PR04MB8429.eurprd04.prod.outlook.com>
On 17/06/2025 04:53, Sherry Sun wrote:
>> @@ -992,7 +997,7 @@ static int nxp_recv_fw_req_v1(struct hci_dev *hdev,
>> struct sk_buff *skb)
>> nxpdev->helper_downloaded = true;
>> serdev_device_wait_until_sent(nxpdev->serdev, 0);
>> serdev_device_set_baudrate(nxpdev->serdev,
>> - HCI_NXP_SEC_BAUDRATE);
>> +
>> HCI_NXP_SEC_BAUDRATE_3M);
>
> Hi Neeraj,
>
> Does this mean that some legacy BT chips using nxp_recv_fw_req_v1() don't support 4Mbps?
> If so, please add comments in the commit message.
If that's true this is implied by compatible and entire property should
be dropped.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-06-17 6:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 15:09 [PATCH v1 1/2] dt-bindings: net: bluetooth: nxp: Add support for 4M baudrate Neeraj Sanjay Kale
2025-06-16 15:09 ` [PATCH v1 2/2] Bluetooth: btnxpuart: " Neeraj Sanjay Kale
2025-06-17 2:53 ` Sherry Sun
2025-06-17 6:43 ` Krzysztof Kozlowski [this message]
2025-06-17 9:57 ` Neeraj Sanjay Kale
2025-06-16 16:26 ` [PATCH v1 1/2] dt-bindings: net: bluetooth: nxp: " Krzysztof Kozlowski
2025-06-17 9:52 ` Neeraj Sanjay Kale
2025-06-17 9:56 ` Neeraj Sanjay Kale
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=6fe27c9d-4641-4aba-9e34-686a4d7f1fa8@kernel.org \
--to=krzk@kernel.org \
--cc=amitkumar.karwar@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=manjeet.gupta@nxp.com \
--cc=marcel@holtmann.org \
--cc=neeraj.sanjaykale@nxp.com \
--cc=robh@kernel.org \
--cc=sherry.sun@nxp.com \
/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