From: Francesco Dolcini <francesco@dolcini.it>
To: Neeraj Sanjay Kale <neeraj.sanjaykale@nxp.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, amitkumar.karwar@nxp.com,
rohit.fule@nxp.com, sherry.sun@nxp.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] Bluetooth: btnxpuart: Add support for IW624 chipset
Date: Thu, 10 Aug 2023 18:46:48 +0200 [thread overview]
Message-ID: <ZNUUeD2Zr1SfTODT@francesco-nb.int.toradex.com> (raw)
In-Reply-To: <20230810094802.832652-1-neeraj.sanjaykale@nxp.com>
Hello,
On Thu, Aug 10, 2023 at 03:18:02PM +0530, Neeraj Sanjay Kale wrote:
> This adds support for NXP IW624 chipset in btnxpuart driver
> by adding FW name and bootloader signature. Based on the
> loader version bits 7:6 of the bootloader signature, the
> driver can choose between selecting secure and non-secure
> FW files.
> For cmd5 payload during FW download, this chip has addresses
> of few registers offset by 1, so added boot_reg_offset to
> handle the chip specific offset.
>
> Signed-off-by: Neeraj Sanjay Kale <neeraj.sanjaykale@nxp.com>
> ---
> drivers/bluetooth/btnxpuart.c | 44 ++++++++++++++++++++++++-----------
> 1 file changed, 31 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/bluetooth/btnxpuart.c b/drivers/bluetooth/btnxpuart.c
> index ee6f6c872a34..b42572ca63af 100644
> --- a/drivers/bluetooth/btnxpuart.c
> +++ b/drivers/bluetooth/btnxpuart.c
...
> @@ -547,7 +553,7 @@ static int nxp_download_firmware(struct hci_dev *hdev)
> serdev_device_set_flow_control(nxpdev->serdev, false);
> nxpdev->current_baudrate = HCI_NXP_PRI_BAUDRATE;
>
> - /* Wait till FW is downloaded and CTS becomes low */
> + /* Wait till FW is downloaded */
> err = wait_event_interruptible_timeout(nxpdev->fw_dnld_done_wait_q,
> !test_bit(BTNXPUART_FW_DOWNLOADING,
> &nxpdev->tx_state),
> @@ -558,16 +564,11 @@ static int nxp_download_firmware(struct hci_dev *hdev)
> }
>
> serdev_device_set_flow_control(nxpdev->serdev, true);
> - err = serdev_device_wait_for_cts(nxpdev->serdev, 1, 60000);
> - if (err < 0) {
> - bt_dev_err(hdev, "CTS is still high. FW Download failed.");
> - return err;
> - }
this seems like an unrelated change, and it's moving from a 60secs
timeout polling CTS to nothing.
What's the reason for this? Should be this a separate commit with a
proper explanation?
Francesco
next prev parent reply other threads:[~2023-08-10 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 9:48 Neeraj Sanjay Kale
2023-08-10 16:46 ` Francesco Dolcini [this message]
2023-08-10 18:02 ` Neeraj sanjay kale
2023-08-10 18:35 ` Francesco Dolcini
2023-08-11 6:19 ` Neeraj sanjay kale
2023-08-11 7:38 ` Francesco Dolcini
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=ZNUUeD2Zr1SfTODT@francesco-nb.int.toradex.com \
--to=francesco@dolcini.it \
--cc=amitkumar.karwar@nxp.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=neeraj.sanjaykale@nxp.com \
--cc=rohit.fule@nxp.com \
--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
all inboxes | Powered by JetHome®