Received: by 10.192.165.148 with SMTP id m20csp2367536imm; Thu, 26 Apr 2018 09:49:03 -0700 (PDT) X-Google-Smtp-Source: AB8JxZopkAOn6ut5hvQhirI/GAULZE+BZWhhQzCf4wm6LuIJrYkKxqrTC95HPmnO3KybzvKdrwSJ X-Received: by 10.101.75.134 with SMTP id t6mr1893604pgq.138.1524761343712; Thu, 26 Apr 2018 09:49:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524761343; cv=none; d=google.com; s=arc-20160816; b=RrlT4LIOz5wzdUSfF4n5axyQkpXye3qiEi+Zp+8DiMPNyla9KTg7fTCcvNZn7BXx3O kELVBITL4RTJjJExUoljhVgJmPitq+n1zcgEvwgJu9o7zpkILlF1ylfoHuSR79u1uB7o mhLSzP56b/RU23uYrbHSYwR7k2wNvdNiU1sj7G2r2PWOmJo1jnT7rn5he0AMbiwgKuAg 5OCh5RUYxROCGWrVDUm7lBEWWGE/cX+QCl2JeVFKfNq1HftXiDPdI3/5GWAW0Flg1e6h TG29nZZgBPeyEeWWlwZi78Es1+psYzT9L2JS8vVDylSIne76aNSan1snzkTUP7UPz0ZN 9mUw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=ArF16BaPMX08qM/1krG/AvOKuZ4jPl4e+vztSAuNnlE=; b=oP9fwPcFTfdCNT4/ovQF2H+Z8HhC1MaBq7TDJFX3VCoaAw/voLk4WUb4fxYa4PMtSQ qnLBu0HnDuDbwjUGL2Vhu6n2fvTbmyZIQorFm90nf9+xCcmc5dp6w+iX+/yM3ofJkjt8 +c5UfjbD6GZeOvt2T6uOLuj+SdAbPBnvHZideQjarlVWb323FleVqNkQQ7+XyePBT/xX NItSiEdkb0spW/C2pzAH+89n4guuyd/lk1TXzW8N09pAuZ7oaqEbUoRiiFQVyFfRGGPn eUMruTaqBs4zVWCmHW6rSXX4JYqwAfXKy6U6v74nz6VTP2BRqYOMDxjzWE3kzs9oOZOw ghIQ== 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 a61-v6si18890112plc.402.2018.04.26.09.48.49; Thu, 26 Apr 2018 09:49:03 -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 S1756831AbeDZQrD (ORCPT + 99 others); Thu, 26 Apr 2018 12:47:03 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:56410 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754544AbeDZQq6 (ORCPT ); Thu, 26 Apr 2018 12:46:58 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id F2CB81435; Thu, 26 Apr 2018 09:46:57 -0700 (PDT) Received: from [192.168.67.35] (usa-sjc-imap-foss1.foss.arm.com [10.72.51.249]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id A0DD13F487; Thu, 26 Apr 2018 09:46:55 -0700 (PDT) Subject: Re: [linux-sunxi] [PATCH 3/3] arm64: allwinner: h6: enable MMC0/2 on Pine H64 To: icenowy@aosc.io, Ulf Hansson , Rob Herring , Maxime Ripard , Chen-Yu Tsai Cc: linux-mmc@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com References: <20180426140728.43155-1-icenowy@aosc.io> <20180426140728.43155-4-icenowy@aosc.io> From: Andre Przywara Message-ID: <03cc2e8c-4a35-3fb4-b408-fd8d4ba3e407@arm.com> Date: Thu, 26 Apr 2018 17:46:26 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180426140728.43155-4-icenowy@aosc.io> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 26/04/18 15:07, Icenowy Zheng wrote: > The Pine H64 board have a MicroSD slot connected to MMC0 controller of > the H6 SoC and a eMMC slot connected to MMC2. > > Enable them in the device tree. > > Signed-off-by: Icenowy Zheng > --- > .../boot/dts/allwinner/sun50i-h6-pine-h64.dts | 32 ++++++++++++++++++++++ > 1 file changed, 32 insertions(+) > > 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 d36de5eb81f3..78b1cd54687c 100644 > --- a/arch/arm64/boot/dts/allwinner/sun50i-h6-pine-h64.dts > +++ b/arch/arm64/boot/dts/allwinner/sun50i-h6-pine-h64.dts > @@ -20,6 +20,38 @@ > chosen { > stdout-path = "serial0:115200n8"; > }; > + > + reg_vcc3v3: vcc3v3 { > + compatible = "regulator-fixed"; > + regulator-name = "vcc3v3"; > + regulator-min-microvolt = <3300000>; > + regulator-max-microvolt = <3300000>; > + }; > + > + reg_vcc1v8: vcc1v8 { > + compatible = "regulator-fixed"; > + regulator-name = "vcc1v8"; > + regulator-min-microvolt = <1800000>; > + regulator-max-microvolt = <1800000>; > + }; > +}; > + > +&mmc0 { > + pinctrl-names = "default"; > + pinctrl-0 = <&mmc0_pins>; > + vmmc-supply = <®_vcc3v3>; So this is actually CLDO1 on the AXP, correct? > + cd-gpios = <&pio 5 6 GPIO_ACTIVE_LOW>; > + status = "okay"; > +}; > + > +&mmc2 { > + pinctrl-names = "default"; > + pinctrl-0 = <&mmc2_pins>; > + vmmc-supply = <®_vcc3v3>; > + vqmmc-supply = <®_vcc1v8>; And this is BLDO2? I am just asking because I want to avoid running into the same problem as with the A64 before: that future DTs become incompatible with older kernels, because we change the power supply to point to the AXP regulators, which this kernel does not support yet. It looks like there are more users of those power rails, so we could keep those supplies connected to these fixed regulators here, even with AXP-805 support in the kernel. Or we keep this back until we get proper AXP support in the kernel? I guess it's quite close to the existing PMICs, so it might be more a copy&paste exercise to support the AXP-805? But apart from this this looks correct to me. Cheers, Andre. > + non-removable; > + cap-mmc-hw-reset; > + status = "okay"; > }; > > &uart0 { >