linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* bluetooth serdev driver for wi2wi w2cbw003?
@ 2018-10-26 20:14 H. Nikolaus Schaller
  0 siblings, 0 replies; only message in thread
From: H. Nikolaus Schaller @ 2018-10-26 20:14 UTC (permalink / raw)
  To: Marcel Holtmann, Johan Hedberg
  Cc: open list:BLUETOOTH DRIVERS, LKML, Discussions about the Letux Kernel

Hi,
what is the best strategy to support the above mentioned
bluetooth (+ wlan combo) chip by a serdev driver?

We have the chip up and running for long time with using
hciattach on the serial port (and no vendor specific
functions like firmware download). And our own out-of-tree
driver to control the power on/off.

But we now want to be able to use hcicontrol hci0 up/down
to control a regulator like the hci_ll.c driver is doing
with a gpio.

Which means we would like to use this DT:

&uart1 {
	pinctrl-names = "default";
	pinctrl-0 = <&uart1_pins>;

	bluetooth: bluetooth {
		compatible = "wi2wi,w2cbw003-bt";
		vdd-supply = <&vaux4>;
	};
};

Does such a driver already exist so that we just have to add
.compatible = "wi2wi,w2cbw003-bt" or should we start to
make one based on by hci_ll.c by removing firmware download
and special ti protocol handling?

Other maybe relevant information from the w2cbw003 data sheet:
- Bluetooth technology based on CSR BC04-ROM
- Data rate up to 3 Mbps for Bluetooth EDR
- It uses a standard HCI interface – any commercial stack or profile supporting the standard interface will work with W2CBW003.

Any directions are welcome.

BR and thanks,
Nikolaus


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2018-10-26 20:20 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-10-26 20:14 bluetooth serdev driver for wi2wi w2cbw003? H. Nikolaus Schaller

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).