From: Neeraj sanjay kale <neeraj.sanjaykale@nxp.com>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"marcel@holtmann.org" <marcel@holtmann.org>,
"johan.hedberg@gmail.com" <johan.hedberg@gmail.com>,
"luiz.dentz@gmail.com" <luiz.dentz@gmail.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"jirislaby@kernel.org" <jirislaby@kernel.org>,
"alok.a.tiwari@oracle.com" <alok.a.tiwari@oracle.com>,
"hdanton@sina.com" <hdanton@sina.com>,
"ilpo.jarvinen@linux.intel.com" <ilpo.jarvinen@linux.intel.com>,
"leon@kernel.org" <leon@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
Amitkumar Karwar <amitkumar.karwar@nxp.com>,
Rohit Fule <rohit.fule@nxp.com>, Sherry Sun <sherry.sun@nxp.com>
Subject: RE: [EXT] Re: [PATCH v6 3/3] Bluetooth: NXP: Add protocol support for NXP Bluetooth chipsets
Date: Fri, 10 Mar 2023 13:51:48 +0000 [thread overview]
Message-ID: <AM9PR04MB8603DA275FB41A5A22491D3AE7BA9@AM9PR04MB8603.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <ZAsp9fm779DR0Vuz@francesco-nb.int.toradex.com>
Hi Francesco
>
> On Fri, Mar 10, 2023 at 12:09:09PM +0000, Neeraj sanjay kale wrote:
> > > > +#define FIRMWARE_W8987 "nxp/uartuart8987_bt.bin"
> > > > +#define FIRMWARE_W8997 "nxp/uartuart8997_bt_v4.bin"
> > > > +#define FIRMWARE_W9098 "nxp/uartuart9098_bt_v1.bin"
> > > > +#define FIRMWARE_IW416 "nxp/uartiw416_bt_v0.bin"
> > > > +#define FIRMWARE_IW612 "nxp/uartspi_n61x_v1.bin.se"
> > >
> > > Where are this files coming from? Where can I download those?
> > > Is loading a combo firmware from the mwifiex driver supported?
> > We are working on submitting these files to linux-firmware. They will
> > be available under nxp/ directory once merged.
>
> What about the combo firmware that would be downloaded by mwifiex
> driver? How is this supposed to interact with it?
If combo firmware is loaded by the mwifiex, then this driver would not detect any bootloader signatures, and would skip FW downloading and move on. Please check the nxp_setup() function.
>
> > > > +#define HCI_NXP_PRI_BAUDRATE 115200 #define
> HCI_NXP_SEC_BAUDRATE
> > > > +3000000
> > > What if the UART device does not support 3000000 baudrate (think at
> > > limitation on the clock source/divider of the UART)? Shouldn't this
> > > be configurable?
> > We have noted this requirement and decided to design and implement on
> > this in upcoming patches along with other new features. We have a
> > number of customers out there who have been using these chips as well
> > as the legacy Marvell chips, which need FW download at 3000000
> > baudrate, and so far there were no issues reported. Using a lower
> > standard baudrate affects the time it takes to download the FW, which
> > we are trying to keep strictly under 5 seconds.
>
> ok, just for you to know our hardware, using NXP SoC, will not work with this
> baudrate (no way to have it given the clock tree we have).
Got it! We will work on this requirement for sure and come up with something soon in the next patch for this driver.
FYI, firmware download takes around 20 seconds at 115200 baudrate, which is highly unacceptable by many customers. 😊
Thanks,
Neeraj
prev parent reply other threads:[~2023-03-10 13:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 15:45 [PATCH v6 0/3] Add support for NXP bluetooth chipsets Neeraj Sanjay Kale
2023-03-01 15:45 ` [PATCH v6 1/3] serdev: Add method to assert break signal over tty UART port Neeraj Sanjay Kale
2023-03-01 16:38 ` Add support for NXP bluetooth chipsets bluez.test.bot
2023-03-01 15:45 ` [PATCH v6 2/3] dt-bindings: net: bluetooth: Add NXP bluetooth support Neeraj Sanjay Kale
2023-03-01 15:45 ` [PATCH v6 3/3] Bluetooth: NXP: Add protocol support for NXP Bluetooth chipsets Neeraj Sanjay Kale
2023-03-02 14:43 ` Ilpo Järvinen
2023-03-06 17:43 ` Neeraj sanjay kale
2023-03-07 11:43 ` Ilpo Järvinen
2023-03-10 18:33 ` Neeraj sanjay kale
2023-03-13 9:08 ` Ilpo Järvinen
2023-03-13 14:17 ` [EXT] " Neeraj sanjay kale
2023-03-06 14:56 ` Francesco Dolcini
2023-03-10 12:09 ` [EXT] " Neeraj sanjay kale
2023-03-10 13:00 ` Francesco Dolcini
2023-03-10 13:51 ` Neeraj sanjay kale [this message]
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=AM9PR04MB8603DA275FB41A5A22491D3AE7BA9@AM9PR04MB8603.eurprd04.prod.outlook.com \
--to=neeraj.sanjaykale@nxp.com \
--cc=alok.a.tiwari@oracle.com \
--cc=amitkumar.karwar@nxp.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=francesco@dolcini.it \
--cc=gregkh@linuxfoundation.org \
--cc=hdanton@sina.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=johan.hedberg@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--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 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.