Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751739AbdFIRhC (ORCPT ); Fri, 9 Jun 2017 13:37:02 -0400 Received: from mx2.suse.de ([195.135.220.15]:58531 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751527AbdFIRhA (ORCPT ); Fri, 9 Jun 2017 13:37:00 -0400 Subject: Re: [linux-sunxi] Re: [PATCH v2] arm64: allwinner: a64: Add initial NanoPi A64 support To: Andre Przywara , jagan@openedev.com, Jagan Teki Cc: maxime.ripard@free-electrons.com, Mark Rutland , devicetree@vger.kernel.org, Catalin Marinas , linux-sunxi@googlegroups.com, Sean Wang , Will Deacon , linux-kernel@vger.kernel.org, Chen-Yu Tsai , Rob Herring , Jagan Teki , Michael Trimarchi , linux-arm-kernel@lists.infradead.org, Icenowy Zheng References: <1497012052-14027-1-git-send-email-jteki@openedev.com> <1497012052-14027-2-git-send-email-jteki@openedev.com> <20170609145141.aknbsis25vmy3rj6@flea.home> <3049841d-36f0-a761-fbed-57971462697c@openedev.com> <3b4dda48-c403-88c4-5c89-63753f508d76@arm.com> From: =?UTF-8?Q?Andreas_F=c3=a4rber?= Organization: SUSE Linux GmbH Message-ID: Date: Fri, 9 Jun 2017 19:36:56 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <3b4dda48-c403-88c4-5c89-63753f508d76@arm.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1339 Lines: 36 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)