On Wed, Dec 10, 2014 at 10:43 AM, Pavel Machek <pavel@xxxxxx> 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-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
