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
| ||
|
Date: Wed, 10 Dec 2014 11:35:59 -0600 From: Rob Herring <robherring2@...il.com> To: Pavel Machek <pavel@....cz> Cc: Pali Rohár <pali.rohar@...il.com>, Sebastian Reichel <sre@...ian.org>, Sebastian Reichel <sre@...g0.de>, kernel list <linux-kernel@...r.kernel.org>, linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>, linux-omap <linux-omap@...r.kernel.org>, Tony Lindgren <tony@...mide.com>, khilman@...nel.org, Aaro Koskinen <aaro.koskinen@....fi>, Ivaylo Dimitrov <ivo.g.dimitrov.75@...il.com>, "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>, Rob Herring <robh+dt@...nel.org>, Pawel Moll <pawel.moll@....com>, Mark Rutland <mark.rutland@....com>, Ian Campbell <ijc+devicetree@...lion.org.uk>, Kumar Gala <galak@...eaurora.org> Subject: Re: BCM2048 bluetooth connected over OMAP serial On Wed, Dec 10, 2014 at 10:43 AM, Pavel Machek <pavel@....cz> wrote: > Hi! > > So, there's bluetooth chip that's connected to the SoC by UART and some > GPIOs. What would be right representation in the device tree? > Something like this? > > bluetooth { > compatible = "broadcom,bcm2048"; > uart = <&uart2>; > reset-gpios = <&gpio3 27 GPIO_ACTIVE_HIGH>; /* want 91 */ > host-wakeup-gpios = <&gpio4 5 GPIO_ACTIVE_HIGH>; /* want 101 */ > bluetooth-wakeup-gpios = <&gpio2 5 GPIO_ACTIVE_HIGH>; /* want 37 */ > chip-type = <3>; > bt-sysclk = <2>; > reset-gpio-shared = <0>; > }; > > Is there some way to prevent OMAP tty driver from binding to the > device and exporting the device to userspace? Isn't the normal way for BT to work is the uart is exposed to userspace and the BT stack is all in userspace? This is how other Broadcom BT/WiFi combo parts work. Rob -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists