linux-kernel - bluetooth serdev driver for wi2wi w2cbw003?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:   Fri, 26 Oct 2018 22:14:13 +0200
From:   "H. Nikolaus Schaller" <hns@...delico.com>
To:     Marcel Holtmann <marcel@...tmann.org>,
        Johan Hedberg <johan.hedberg@...il.com>
Cc:     "open list:BLUETOOTH DRIVERS" <linux-bluetooth@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Discussions about the Letux Kernel 
        <letux-kernel@...nphoenux.org>
Subject: bluetooth serdev driver for wi2wi w2cbw003?

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