Re: [EXT] Re: [PATCH v6 3/3] Bluetooth: NXP: Add protocol support for NXP Bluetooth chipsets

[Francesco Dolcini <francesco@dolcini.it>]

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?

> > > +#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).

> Hope this helps!
Yes, thanks!

Francesco