Re: shared hci transport

[Marcel Holtmann <marcel@holtmann.org>]

Hi Pavan,

please don't do top-posting on this mailing list. We want proper inline
quoting.

> sure.
> the bcm4325 has uart transport for BT [so I can make use of hci_h4, say by hciattach - like bcm2035].
> The FM core understands hci-vendor specific command.
> 
> for example, I send HCI_VS opcode=0x20 to set the power of Rx to On.[The power on sequence also involves download of a firmware which is nothing but a file with ~10/20 hci-vendor specific commands with different opcodes].
> opcode 0x0a (say) to set the frequency and similarly in opcode 0x1d [audio enable] I give an data arguement 0x01 or 0x02 to say to FM Rx to put out audio on either it's analog lines or digital [i2s] lines..
> 
> Currently my fm stack, application is making use of hci_open_dev, send_cmd kind of hci lib calls to send commands.
> 
> Now what should be my approach to send in same sort of commands from the kernel space ?

For the firmware loading part, we have to change this whole driver model
and add an init stage that allows configuration etc.

I am not sold on the whole in-kernel approach for FM yet. We need to
talk more about it. Especially since vendor commands and messing with
the flow control is tricky.

Regards

Marcel