Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758151AbaLJRgZ (ORCPT ); Wed, 10 Dec 2014 12:36:25 -0500 Received: from mail-wg0-f45.google.com ([74.125.82.45]:55807 "EHLO mail-wg0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757620AbaLJRgX (ORCPT ); Wed, 10 Dec 2014 12:36:23 -0500 MIME-Version: 1.0 In-Reply-To: <20141210164333.GA3154@amd> References: <20141210164333.GA3154@amd> From: Rob Herring Date: Wed, 10 Dec 2014 11:35:59 -0600 Message-ID: Subject: Re: BCM2048 bluetooth connected over OMAP serial To: Pavel Machek Cc: =?UTF-8?Q?Pali_Roh=C3=A1r?= , Sebastian Reichel , Sebastian Reichel , kernel list , linux-arm-kernel , linux-omap , Tony Lindgren , khilman@kernel.org, Aaro Koskinen , Ivaylo Dimitrov , "devicetree@vger.kernel.org" , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 10, 2014 at 10:43 AM, Pavel Machek 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/