Received: by 2002:a05:6a10:a852:0:0:0:0 with SMTP id d18csp2389736pxy; Sun, 2 May 2021 21:21:56 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyflLAJnIie7fVvUvvFcsuoKxi5qiK1+/7JftE8wAmdStSJLLOUh4/W7M0mtLjWhiJPdNzR X-Received: by 2002:a63:a70b:: with SMTP id d11mr16363164pgf.26.1620015715866; Sun, 02 May 2021 21:21:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620015715; cv=none; d=google.com; s=arc-20160816; b=dq38oBceNIxAcp9/hkVknkUO6ndYK+reJ8bHNyvUNxirbEXe0z99f9X80o3LdPz7iV um3EJh1zEJa/ofWaQbTRn9j+aHhTvntGq8IziCK0UDgq8VPSRtF8lp0ZeMEswjYKvTWS N9LNmTaHGRBXpuS0ldz3Toms+OeIjmI1SOj+RH5Acm4+YD+z2aTpVMoBvd4/ETe/fxf1 retUWkm4F/5CENBllvSTk03+YRVlNRUBSGjt6VBBPkC4Dnz6+8JVAXKp/x87yliAHbFy mmlxjTCymnfp8xYvjMPm0GSXisBLukW1vRzpjitDAa5I7ZKTlklXOxXnpQT7dkfYt+bS NHqQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:subject:cc:to:from:date:references:in-reply-to :message-id:mime-version:user-agent:dkim-signature:dkim-signature; bh=Wp7XYzm4lyNSERoy1FmfOae3cQfvuVX2QEotJK/yJJ8=; b=TEbZ+eISOlAnFxFXR6OrjBwzUPjZDcWnOE2cxg8s+MzPTra20OrStQRoM588BtQb5v qDWOczo9aREiMxq3VzntT1KLZ4KaBKanE2uk3JDxzLnJApKTTGMrsiydbhd9/0GWFg72 4sY/aJeSugauFiQgFCFLSEgJtpNYvPOR5F2kcLBKFtrrWe3qaBi4h2wyz3Dhe8xYSo+B OEz8iIIAXBxhDC99FBXFKZEVwomEbKuM9ABIeLC9pfDRJev577G4NwbZvzGhNz1UBq7w slfwctPKRRD/U9/Roq/REsiGIbekiwP5T/kAta5oauODpeiT10GG29wCU1MhkvAq9Ael ljKg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@aj.id.au header.s=fm2 header.b=bDUARedU; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b=B4jlIQXk; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id j21si11741912pfn.127.2021.05.02.21.21.29; Sun, 02 May 2021 21:21:55 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@aj.id.au header.s=fm2 header.b=bDUARedU; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b=B4jlIQXk; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229817AbhECEUz (ORCPT + 99 others); Mon, 3 May 2021 00:20:55 -0400 Received: from new2-smtp.messagingengine.com ([66.111.4.224]:35775 "EHLO new2-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229457AbhECEUy (ORCPT ); Mon, 3 May 2021 00:20:54 -0400 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailnew.nyi.internal (Postfix) with ESMTP id 8994D580915; Mon, 3 May 2021 00:20:01 -0400 (EDT) Received: from imap2 ([10.202.2.52]) by compute3.internal (MEProxy); Mon, 03 May 2021 00:20:01 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aj.id.au; h= mime-version:message-id:in-reply-to:references:date:from:to:cc :subject:content-type; s=fm2; bh=Wp7XYzm4lyNSERoy1FmfOae3cQfvuVX 2QEotJK/yJJ8=; b=bDUARedUZgjPAzEnZC1bxDiwX+6f3UMtdIfPIEmZ19UArg1 gRjpcu0moAVl/68G1R09VyDMoXzDkBnynu9KIA8ywdVm3i2eOzt/MzAroKWV9HtE EaawbiAPRpMmYsW/0JwECb8riPszF8U+EMMJC+kdujj2fYncAdRj+k6BxRDnJ9dp ToAuRIK7LRPk1sfr5UA2jjwBqyQKI05UpBcw8H4RnRbgy23JGhDdupWTOSsYuXT4 S75haQONi0i28bLR6rLIBXwA8MdhPP8MZE5JVweg1W/FjVd3mkZBA8OPm+ue9DlE xqIpvmxgy+714czPXLCUZoFLt5PIAnwGKqwjLBw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=Wp7XYz m4lyNSERoy1FmfOae3cQfvuVX2QEotJK/yJJ8=; b=B4jlIQXklSprl8L9WIInZ4 K6xyebrbKDzJHotVIMBNqWBMapb2OARcXQ7k8h4iksMYcs94Hd+8CLFN69ZjK5eW YQ9cvbnCFhJqZIPc2ITnnaYYeQmXsP8ZXOhnBJygSNBSGcXTr2WPBkYidrhe0z6e jnBdv46glIKPSf3XQuyPwmG+kkpcqUtj+89V1MSUXv9ykOTadg+a4C42+ZTUQH35 vHNfq9oQgUGz0teetMQp3Ot2eeJ7MQGHee2YX82S5shxOckmEanipyD+y6HZ6593 cgyvExNcwIAiwyLReo17hWhYEkJPgJZx3NRou185hS4ZiBqGUd7yWgTTq8AqcwcQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvdeffedgtdefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesthdtredtreerjeenucfhrhhomhepfdetnhgu rhgvficulfgvfhhfvghrhidfuceorghnughrvgifsegrjhdrihgurdgruheqnecuggftrf grthhtvghrnhepheehfeegfeekjeegtdetuedvgeeljedvteffudeiffduvefhiefhleef lefghfeknecuffhomhgrihhnpeihrghmlhdrohhrghenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrnhgurhgvfiesrghjrdhiugdrrghu X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id CD029A00079; Mon, 3 May 2021 00:19:59 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-403-gbc3c488b23-fm-20210419.005-gbc3c488b Mime-Version: 1.0 Message-Id: <75226402-503c-4e9b-96dc-e4bd74cf20ac@www.fastmail.com> In-Reply-To: <20210503014336.20256-2-steven_lee@aspeedtech.com> References: <20210503014336.20256-1-steven_lee@aspeedtech.com> <20210503014336.20256-2-steven_lee@aspeedtech.com> Date: Mon, 03 May 2021 13:49:38 +0930 From: "Andrew Jeffery" To: "Steven Lee" , "Ulf Hansson" , "Rob Herring" , "Joel Stanley" , "Ryan Chen" , "moderated list:ASPEED SD/MMC DRIVER" , "moderated list:ASPEED SD/MMC DRIVER" , linux-mmc , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , "moderated list:ARM/ASPEED MACHINE SUPPORT" , "open list" Cc: "Hongwei Zhang" , "Ryan Chen" , "Chin-Ting Kuo" Subject: =?UTF-8?Q?Re:_[PATCH_v2_1/3]_dt-bindings:_mmc:_sdhci-of-aspeed:_Add_desc?= =?UTF-8?Q?ription_for_AST2600_EVB.?= Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Steven, On Mon, 3 May 2021, at 11:13, Steven Lee wrote: > Add the description for describing the AST 2600 EVB reference design of > GPIO regulators and provide the example in the document. > > AST2600-A2 EVB has the reference design for enabling SD bus > power and toggling SD bus signal voltage by GPIO pins. > > In the reference design, GPIOV0 of AST2600-A2 EVB is connected to > power load switch that providing 3.3v to SD1 bus vdd. GPIOV1 is > connected to a 1.8v and a 3.3v power load switch that providing > signal voltage to > SD1 bus. > > If GPIOV0 is active high, SD1 bus is enabled. Otherwise, SD1 bus is > disabled. > If GPIOV1 is active high, 3.3v power load switch is enabled, SD1 > signal voltage is 3.3v. Otherwise, 1.8v power load switch will be > enabled, SD1 signal voltage becomes 1.8v. > > AST2600-A2 EVB also support toggling signal voltage for SD2 bus. > The design is the same as SD1 bus. It uses GPIOV2 as power-gpio and > GPIOV3 as power-switch-gpio. > > Signed-off-by: Steven Lee > --- > .../devicetree/bindings/mmc/aspeed,sdhci.yaml | 99 +++++++++++++++++++ > 1 file changed, 99 insertions(+) > > diff --git a/Documentation/devicetree/bindings/mmc/aspeed,sdhci.yaml > b/Documentation/devicetree/bindings/mmc/aspeed,sdhci.yaml > index 987b287f3bff..dd894aba0bb7 100644 > --- a/Documentation/devicetree/bindings/mmc/aspeed,sdhci.yaml > +++ b/Documentation/devicetree/bindings/mmc/aspeed,sdhci.yaml > @@ -20,6 +20,19 @@ description: |+ > the slots are dependent on the common configuration area, they are > described > as child nodes. > > + The signal voltage of SDHCIs on AST2600-A2 EVB is able to be toggled > by GPIO > + pins. In the reference design, GPIOV0 of AST2600-A2 EVB is connected > to the > + power load switch that providing 3.3v to SD1 bus vdd, GPIOV1 is > connected to > + a 1.8v and a 3.3v power load switch that providing signal voltage to > + SD1 bus. > + If GPIOV0 is active high, SD1 bus is enabled. Otherwise, SD1 bus is > + disabled. If GPIOV1 is active high, 3.3v power load switch is > enabled, SD1 > + signal voltage is 3.3v. Otherwise, 1.8v power load switch will be > enabled, SD1 > + signal voltage becomes 1.8v. > + AST2600-A2 EVB also support toggling signal voltage for SD2 bus. > + The design is the same as SD1 bus. It uses GPIOV2 as power-gpio and > GPIOV3 > + as power-switch-gpio. I don't think we should be describing design-specific details in the binding document. However, I think this would be a great comment in the AST2600 EVB devicetree. Can you please move it there? > + > properties: > compatible: > enum: > @@ -78,6 +91,7 @@ required: > - clocks > > examples: > + //Example 1 > - | > #include > sdc@1e740000 { > @@ -104,3 +118,88 @@ examples: > clocks = <&syscon ASPEED_CLK_SDIO>; > }; > }; > + > + //Example 2 (AST2600EVB with GPIO regulator) I feel you didn't test this with `make dt_binding_check` as `//` isn't a valid YAML comment token. You need to use `#` for comments ( https://yaml.org/spec/1.2/spec.html#id2780069 ). > + - | > + #include > + #include > + vcc_sdhci0: regulator-vcc-sdhci0 { > + compatible = "regulator-fixed"; > + > + regulator-name = "SDHCI0 Vcc"; > + regulator-min-microvolt = <3300000>; > + regulator-max-microvolt = <3300000>; > + gpios = <&gpio0 ASPEED_GPIO(V, 0) > + GPIO_ACTIVE_HIGH>; > + enable-active-high; > + }; > + > + vccq_sdhci0: regulator-vccq-sdhci0 { > + compatible = "regulator-gpio"; > + > + regulator-name = "SDHCI0 VccQ"; > + regulator-min-microvolt = <1800000>; > + regulator-max-microvolt = <3300000>; > + gpios = <&gpio0 ASPEED_GPIO(V, 1) > + GPIO_ACTIVE_HIGH>; > + gpios-states = <1>; > + states = <3300000 1 > + 1800000 0>; > + }; > + > + vcc_sdhci1: regulator-vcc-sdhci1 { > + compatible = "regulator-fixed"; > + > + regulator-name = "SDHCI1 Vcc"; > + regulator-min-microvolt = <3300000>; > + regulator-max-microvolt = <3300000>; > + gpios = <&gpio0 ASPEED_GPIO(V, 2) > + GPIO_ACTIVE_HIGH>; > + enable-active-high; > + }; > + > + vccq_sdhci1: regulator-vccq-sdhci1 { > + compatible = "regulator-gpio"; > + > + regulator-name = "SDHCI1 VccQ"; > + regulator-min-microvolt = <1800000>; > + regulator-max-microvolt = <3300000>; > + gpios = <&gpio0 ASPEED_GPIO(V, 3) > + GPIO_ACTIVE_HIGH>; > + gpios-states = <1>; > + states = <3300000 1 > + 1800000 0>; > + }; > + > + sdc@1e740000 { > + compatible = "aspeed,ast2600-sd-controller"; > + reg = <0x1e740000 0x100>; > + #address-cells = <1>; > + #size-cells = <1>; > + ranges = <0 0x1e740000 0x20000>; > + clocks = <&syscon ASPEED_CLK_GATE_SDCLK>; > + > + sdhci0: sdhci@100 { > + compatible = "aspeed,ast2600-sdhci", "sdhci"; > + reg = <0x100 0x100>; > + interrupts = ; > + sdhci,auto-cmd12; > + clocks = <&syscon ASPEED_CLK_SDIO>; > + vmmc-supply = <&vcc_sdhci0>; > + vqmmc-supply = <&vccq_sdhci0>; > + sd-uhs-sdr104; > + clk-phase-uhs-sdr104 = <180>, <180>; > + }; > + > + sdhci1: sdhci@200 { > + compatible = "aspeed,ast2600-sdhci", "sdhci"; > + reg = <0x200 0x100>; > + interrupts = ; > + sdhci,auto-cmd12; > + clocks = <&syscon ASPEED_CLK_SDIO>; > + vmmc-supply = <&vcc_sdhci1>; > + vqmmc-supply = <&vccq_sdhci1>; > + sd-uhs-sdr104; > + clk-phase-uhs-sdr104 = <0>, <0>; > + }; > + }; This is a good example, so can we keep this and just drop the comment from the binding document? Cheers, Andrew