Hi, Am 09.06.2017 um 17:36 schrieb Andre Przywara: > On 09/06/17 16:26, Jagan Teki wrote: >> On Friday 09 June 2017 08:21 PM, Maxime Ripard wrote: >>> On Fri, Jun 09, 2017 at 12:40:52PM +0000, Jagan Teki wrote: >>>> +&uart1 { >>>> + pinctrl-names = "default"; >>>> + pinctrl-0 = <&uart1_pins>, <&uart1_rts_cts_pins>; >>>> + status = "okay"; >>>> +}; >>> >>> And [what is connected] on that UART? >> >> uart1 for SDIO (Wifi connector, with RTS/CTS), this along with mmc1 > > To be precise, UART1 (with h/w handshake) is connected to the Bluetooth > part of the WiFi/BT chip, which is soldered on that board. Regardless of > the actual *WiFi* support state BT should work already - at least it did > when I tried this a few months ago on the Pine64 (although this involved > some userland heavy lifting). > Not sure what the approach here is in regard to the power supply and > wake-up GPIOs, shall they be described in this node as well or is that > up for userspace to control? You should use a serdev based Bluetooth driver by adding a sub-node, and it should take care of any reset GPIOs etc. for you. Question is which driver is needed here and what state it is in. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html