Received: by 2002:a17:90a:37e8:0:0:0:0 with SMTP id v95csp374009pjb; Fri, 4 Oct 2019 00:40:26 -0700 (PDT) X-Google-Smtp-Source: APXvYqxRgmu5yZZnx4FC6kKsPwCY3COJWRIKLYjUwjYoR44lpBkyIknozLjIn4ODbmEzsWsJBFjT X-Received: by 2002:a50:baa5:: with SMTP id x34mr14238050ede.148.1570174826797; Fri, 04 Oct 2019 00:40:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570174826; cv=none; d=google.com; s=arc-20160816; b=Em2yvig1GmQ9OcSf7+kfY6hDR3eY+6dZ61IGNh1X9Ox3/ZyQzhLA5lzGW0iYJl56/E d/bWDQy4NVS84fSJjT7KIdi0s9BkR/+7SjiEDeqBAIrP+RR6GYIY6Ki4d2vq/E5Wuf8V IOtduAWmd1DS6PJDnsx5G/jN9+TGTfmJcsZQzjOx21axemytM90Sb7INTA1lXQmckLb2 eAqyNkpMt5ufmVpKKZazQ0tncdUj0CV35wnM4P79nzV5UlrguYiOTsTcM7+a+giEOjkO 3BXUSAbGLYtz27UecETSHuOGySJnf/FrbHVPr+lVZ03sPnkz6gSvHofttwLNqy7+rAJw vVsQ== 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; bh=Mfg+nbNaEWTSkrJHEx9L5+HsKZFhUyKWQtF7qOEnaBI=; b=tZhapQloE2oNf7ij6ikEN8PYq/8SaqFLB3M2boqjN79c5yK8AoMg5W913EMjlYCafQ f4VyZg+txJGpX1rWXdnbfLHH1/PoHxpVZartZVInpDZhCu7pKoZmeI/PHnHaPzKjT7ar usmyRvJtqkejsCuxICjUI43kKrkS3kkNlfER8Ht4QagCuB3/4r2uX63++E1XwskCXRcz NCK7j5ASSDwwq4ui3mYthTKXRsLLeVyGtktphlxqTQteq5Nzs4exLmRWNxPzOhR74Qlb bzR8hJ9Ahg92sCiyVnDyo4dWGNUCy6ZZzGpwasxBS9KeCPf/Xw5yNSwVbyPczfOKkgIp vOqg== 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 ox10si2549705ejb.325.2019.10.04.00.40.02; Fri, 04 Oct 2019 00:40:26 -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 S1731972AbfJDABR (ORCPT + 99 others); Thu, 3 Oct 2019 20:01:17 -0400 Received: from foss.arm.com ([217.140.110.172]:59354 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729684AbfJDABQ (ORCPT ); Thu, 3 Oct 2019 20:01:16 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 144A915A1; Thu, 3 Oct 2019 17:01:16 -0700 (PDT) Received: from [192.168.1.124] (unknown [172.31.20.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 49D153F534; Thu, 3 Oct 2019 17:01:15 -0700 (PDT) Subject: Re: [PATCH 3/3] arm64: dts: rockchip: fix RockPro64 sdmmc settings To: Soeren Moch , Heiko Stuebner Cc: linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org References: <20191003215036.15023-1-smoch@web.de> <20191003215036.15023-3-smoch@web.de> From: Robin Murphy Message-ID: <31181f3c-20ec-e717-1f7e-8b35cd54d96d@arm.com> Date: Fri, 4 Oct 2019 01:01:01 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:68.0) Gecko/20100101 Thunderbird/68.1.1 MIME-Version: 1.0 In-Reply-To: <20191003215036.15023-3-smoch@web.de> Content-Type: text/plain; charset=utf-8; format=flowed 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 On 2019-10-03 10:50 pm, Soeren Moch wrote: > According to the RockPro64 schematic [1] the rk3399 sdmmc controller is > connected to a microSD (TF card) slot, which cannot be switched to 1.8V. Really? AFAICS the SDMMC0 wiring looks pretty much identical to the NanoPC-T4 schematic (it's the same reference design, after all), and I know that board can happily drive a UHS-I microSD card with 1.8v I/Os, because mine's doing so right now. Robin. > So also configure the vcc_sdio regulator, which drives the i/o voltage > of the sdmmc controller, accordingly. > > While at it, also remove the cap-mmc-highspeed property of the sdmmc > controller, since no mmc card can be connected here. > > [1] http://files.pine64.org/doc/rockpro64/rockpro64_v21-SCH.pdf > > Fixes: e4f3fb490967 ("arm64: dts: rockchip: add initial dts support for Rockpro64") > Signed-off-by: Soeren Moch > --- > Cc: Heiko Stuebner > Cc: linux-rockchip@lists.infradead.org > Cc: linux-arm-kernel@lists.infradead.org > Cc: linux-kernel@vger.kernel.org > --- > arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dts | 3 +-- > 1 file changed, 1 insertion(+), 2 deletions(-) > > diff --git a/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dts b/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dts > index 2e44dae4865a..084f1d994a50 100644 > --- a/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dts > +++ b/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dts > @@ -353,7 +353,7 @@ > regulator-name = "vcc_sdio"; > regulator-always-on; > regulator-boot-on; > - regulator-min-microvolt = <1800000>; > + regulator-min-microvolt = <3000000>; > regulator-max-microvolt = <3000000>; > regulator-state-mem { > regulator-on-in-suspend; > @@ -624,7 +624,6 @@ > > &sdmmc { > bus-width = <4>; > - cap-mmc-highspeed; > cap-sd-highspeed; > cd-gpios = <&gpio0 7 GPIO_ACTIVE_LOW>; > disable-wp; > -- > 2.17.1 > > > _______________________________________________ > Linux-rockchip mailing list > Linux-rockchip@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-rockchip >