Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp6476997imm; Mon, 23 Jul 2018 19:41:07 -0700 (PDT) X-Google-Smtp-Source: AAOMgpcyj4VmK9dGHYcQjtr1H9CA2Gffxt/IOs57dnOPxbN+3OKN30Z5cx6QpZ6KzAkzk6jElOKN X-Received: by 2002:a17:902:5a83:: with SMTP id r3-v6mr14960108pli.78.1532400067350; Mon, 23 Jul 2018 19:41:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1532400067; cv=none; d=google.com; s=arc-20160816; b=i2Ycu1Jz9KiLM5pWKL0FQ4zi4VljmKemd3MZp9gbans0huoo824TB1Xn4vNAJA2tfs C1M9+MjYVkEAPqDC1jpKTjOHUVQyB5FbI27KbD8G9+Ntwn8lZcLp2nzjulxach6QYcIp ZBvUYjuN1KV+z88RXq941ic2YLI+LrgM8tQifO7UKz3ltqvW8WS4+pAmo+poYbZxoCZv NCZYzGFoxRdhYJy1Vcffo62XEvlj32Mw89Sx8/CiM81Pxk5TUZcZ6KN53F9CUHv2gorX 54MvRqjXP7XG36NvsRTb5VxuiBkXIXIvvvn5Qe7elG1Zr2MiaU1dr5P0Ko7mrj+xbV41 boWA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:from:cc:to:subject :content-transfer-encoding:mime-version:references:in-reply-to:date :arc-authentication-results; bh=c6dBJ3X5qHSmUjEFjAT3OC9YXcSwH4FDO9s+aJzKebE=; b=IpJWs3yLV976e+pu7u0u3/B3hc7m1A3jdyqJN7bUvN+ec4DoNP36QQhMTKoCwakrgm Wisn8jlwHWx2YBHNebMDQ9F+YtsjbExOrfOXkagE3Kbqib0MIo4JrEprbVIvx61gSOaU 09Kc1lhfkpYwlo6IwMeVPUlUeHBsQCLKxUvdS2+qCMw/fN3ET8S/HvbEKqSHURJ2KrT4 MQ5MeKFeM6Mj2Jt0/U9VRXj9V5pqSHTlUehi1yjVvNjNeZCgJIxnNSbx8Vxgeb6l2joO IOwkfS/2HUhAAjzz1kxsOeiUTB/reBC/o6tgLKCrFV2nvNxC0aBWxwV+BuJQ16LYO07w NjzA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 8-v6si11544025pfw.89.2018.07.23.19.40.52; Mon, 23 Jul 2018 19:41:07 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388391AbeGXDnj convert rfc822-to-8bit (ORCPT + 99 others); Mon, 23 Jul 2018 23:43:39 -0400 Received: from hermes.aosc.io ([199.195.250.187]:60470 "EHLO hermes.aosc.io" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388284AbeGXDnj (ORCPT ); Mon, 23 Jul 2018 23:43:39 -0400 Received: from localhost (localhost [127.0.0.1]) (Authenticated sender: icenowy@aosc.io) by hermes.aosc.io (Postfix) with ESMTPSA id 23B689F312; Tue, 24 Jul 2018 02:39:21 +0000 (UTC) Date: Tue, 24 Jul 2018 10:39:10 +0800 In-Reply-To: References: <20180724011551.49603-1-icenowy@aosc.io> <20180724011551.49603-4-icenowy@aosc.io> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT Subject: Re: [linux-sunxi] Re: [PATCH 3/3] arm64: allwinner: dts: h6: add Wi-Fi support for Pine H64 model A/B To: wens@csie.org, Chen-Yu Tsai CC: Maxime Ripard , linux-arm-kernel , devicetree , linux-kernel , linux-sunxi From: Icenowy Zheng Message-ID: <9F54A9DF-CB83-407E-802C-4B30CBE193AD@aosc.io> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 于 2018年7月24日 GMT+08:00 上午10:37:51, Chen-Yu Tsai 写到: >On Tue, Jul 24, 2018 at 10:28 AM, Icenowy Zheng >wrote: >> >> >> 于 2018年7月24日 GMT+08:00 上午10:26:02, Chen-Yu Tsai 写到: >>>On Tue, Jul 24, 2018 at 10:23 AM, Icenowy Zheng >>>wrote: >>>> >>>> >>>> 于 2018年7月24日 GMT+08:00 上午10:21:59, Chen-Yu Tsai 写到: >>>>>On Tue, Jul 24, 2018 at 9:15 AM, Icenowy Zheng >>>wrote: >>>>>> The Pine H64 model A has a Wi-Fi module connector and the model B >>>has >>>>>an >>>>>> on-board RTL8723BS Wi-Fi module. >>>>>> >>>>>> Add support for them. For model A, as it's not defaultly present, >>>>>keep >>>>>> it disabled now. >>>>> >>>>>Nope. Pine64 actually has two WiFi/BT modules. And they require >>>>>different >>>>>device tree snippets for both the WiFi and BT side. This is better >>>>>resolved >>>>>with device tree overlays. >>>>> >>>>>I have both, though I've yet found time to work on them. >>>> >>>> I have also both. >>>> >>>> The skeleton here can get the Wi-Fi of both to work. >>> >>>Cool. Then I can put away my RTL module for now. :) >> >> P.S. SDIO is auto detectable, and for BCM chips, the OOB interrupt >> is only a bonus function and it can fall back to standard in-band >> interrupt (which doesn't need special binding, and is currently >> used by mainline r8723bs driver.) > >Correct. With BT you'll have serdev device nodes with different >compatibles. Then you'll have to resort to overlays, and you'd probably >end up adding WiFi OOB interrupt bits as well. > >So the question remaining is: should we enable the MMC part, along >with power sequencing and regulator supplies, by default? Thinking >more about it, I'm actually OK with it. The board connectors are >clearly marked as being for a WiFi+BT module. The whole space on >the board is surrounded by a box in silkscreen. Sorry for the >initial nack. > >Maxime, any thoughts? I remember he refused it for Pine A64. > >>> >>>ChenYu >>> >>>> >>>>> >>>>>ChenYu >>>>> >>>>>> Signed-off-by: Icenowy Zheng >>>>>> --- >>>>>> .../allwinner/sun50i-h6-pine-h64-model-b.dts | 8 +++++ >>>>>> .../boot/dts/allwinner/sun50i-h6-pine-h64.dts | 29 >>>>>+++++++++++++++++++ >>>>>> 2 files changed, 37 insertions(+) >>>>>> >>>>>> diff --git >>>>>a/arch/arm64/boot/dts/allwinner/sun50i-h6-pine-h64-model-b.dts >>>>>b/arch/arm64/boot/dts/allwinner/sun50i-h6-pine-h64-model-b.dts >>>>>> index d0fcc25efb00..d0f775613c9b 100644 >>>>>> --- >a/arch/arm64/boot/dts/allwinner/sun50i-h6-pine-h64-model-b.dts >>>>>> +++ >b/arch/arm64/boot/dts/allwinner/sun50i-h6-pine-h64-model-b.dts >>>>>> @@ -18,3 +18,11 @@ >>>>>> }; >>>>>> }; >>>>>> }; >>>>>> + >>>>>> +&mmc1 { >>>>>> + status = "okay"; >>>>>> +}; >>>>>> + >>>>>> +&wifi_pwrseq { >>>>>> + status = "okay"; >>>>>> +}; >>>>>> diff --git a/arch/arm64/boot/dts/allwinner/sun50i-h6-pine-h64.dts >>>>>b/arch/arm64/boot/dts/allwinner/sun50i-h6-pine-h64.dts >>>>>> index a85867f8b684..75db6d4139bf 100644 >>>>>> --- a/arch/arm64/boot/dts/allwinner/sun50i-h6-pine-h64.dts >>>>>> +++ b/arch/arm64/boot/dts/allwinner/sun50i-h6-pine-h64.dts >>>>>> @@ -40,6 +40,12 @@ >>>>>> gpios = <&r_pio 0 7 GPIO_ACTIVE_HIGH>; /* >>>PL7 >>>>>*/ >>>>>> }; >>>>>> }; >>>>>> + >>>>>> + wifi_pwrseq: wifi_pwrseq { >>>>>> + compatible = "mmc-pwrseq-simple"; >>>>>> + reset-gpios = <&r_pio 1 3 GPIO_ACTIVE_LOW>; /* >PL2 >>>*/ >>>>>> + status = "disabled"; >>>>>> + }; >>>>>> }; >>>>>> >>>>>> &mmc0 { >>>>>> @@ -50,6 +56,17 @@ >>>>>> status = "okay"; >>>>>> }; >>>>>> >>>>>> +&mmc1 { >>>>>> + pinctrl-names = "default"; >>>>>> + pinctrl-0 = <&mmc1_pins>; >>>>>> + vmmc-supply = <®_cldo2>; >>>>>> + vqmmc-supply = <®_bldo2>; >>>>>> + mmc-pwrseq = <&wifi_pwrseq>; >>>>>> + bus-width = <4>; >>>>>> + non-removable; >>>>>> + status = "disabled"; >>>>>> +}; >>>>>> + >>>>>> &mmc2 { >>>>>> pinctrl-names = "default"; >>>>>> pinctrl-0 = <&mmc2_pins>; >>>>>> @@ -128,12 +145,24 @@ >>>>>> }; >>>>>> >>>>>> reg_cldo2: cldo2 { >>>>>> + /* >>>>>> + * This regulator is connected >with >>>>>CLDO3. >>>>>> + * Before the kernel can support >>>>>synchronized >>>>>> + * enable of coupled regulators, >>>keep >>>>>them >>>>>> + * both always on as a ugly hack. >>>>>> + */ >>>>>> + regulator-always-on; >>>>>> regulator-min-microvolt = >>><3300000>; >>>>>> regulator-max-microvolt = >>><3300000>; >>>>>> regulator-name = "vcc-wifi-1"; >>>>>> }; >>>>>> >>>>>> reg_cldo3: cldo3 { >>>>>> + /* >>>>>> + * This regulator is connected >with >>>>>CLDO2. >>>>>> + * See the comments for CLDO2. >>>>>> + */ >>>>>> + regulator-always-on; >>>>>> regulator-min-microvolt = >>><3300000>; >>>>>> regulator-max-microvolt = >>><3300000>; >>>>>> regulator-name = "vcc-wifi-2"; >>>>>> -- >>>>>> 2.18.0 >>>>>> >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>Groups "linux-sunxi" group. >>>> To unsubscribe from this group and stop receiving emails from it, >>>send an email to linux-sunxi+unsubscribe@googlegroups.com. >>>> For more options, visit https://groups.google.com/d/optout. >> >> -- >> You received this message because you are subscribed to the Google >Groups "linux-sunxi" group. >> To unsubscribe from this group and stop receiving emails from it, >send an email to linux-sunxi+unsubscribe@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout.