From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 357F1C0218A for ; Tue, 28 Jan 2025 21:39:58 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 3005982153; Tue, 28 Jan 2025 22:39:53 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=fail (p=reject dis=none) header.from=tidylabs.net Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=tidylabs.net header.i=@tidylabs.net header.b="wlEEQw/V"; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=purelymail.com header.i=@purelymail.com header.b="mpWQ1Xvk"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id 9550481DFA; Tue, 28 Jan 2025 22:39:50 +0100 (CET) Received: from sendmail.purelymail.com (sendmail.purelymail.com [34.202.193.197]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id 5AAD982008 for ; Tue, 28 Jan 2025 22:39:35 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=pass (p=reject dis=none) header.from=tidylabs.net Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=justin@tidylabs.net DKIM-Signature: a=rsa-sha256; b=wlEEQw/VZmL86h5EFroZTJeLnhYi1DQYX8VJC1hcEguACrUlD9ubuX0iiHiie228MsorT7evc5+7cbTB9IhXBQz8JjnEjB7WWC/ilVgnO+qxLi/MuAZvkxrZ5fxi7azsxDYnKjGSf6EE4vDT0Y93Y5/rdwhmEJ6Z3i+kG50RiLi/0pc7cFJSeSZt6F7btg0oOsFPsZYiDcScJeT09CAR35/CIf7HbF5k8WiHRq9ATUbVSfr9htskuvrtRE+oP2fR410FfMV3wWTipQuxpcG3OicL63n6WUdXLZHTXIaJ9PLKkKkIKAuuLKOm8C4lPRx5v9shsyiJP1ScI0neNYt9MQ==; s=purelymail1; d=tidylabs.net; v=1; bh=HjMYWVXq9anMOHoOIMlrIO76slqc4xHGVLLkNsbJ0oA=; h=Received:From:To:Subject:Date; DKIM-Signature: a=rsa-sha256; b=mpWQ1XvkilaNmL7HfXlVfvQ04HcVmeF+Klk924yhL0iWqNkwcDOXMhMgsJle5cQetzKyLlJfJAcssmVwBkbMqSM/Rg8esJBwF8w7Ws0uWB2sV5aCTFsHPfaqz7Cph9kKbY+mKDwxrEKJ+6Fw21W6iCaWh+0gdaEt60TZtOu8UZZyv4ikgfarMgRQGVUzvU8wqV2KtcnEo8qEp2rJtgbDYzDOBFUXjcKeIazjFlp5+gNHcdmp1vABXLLI5PibgVJSCr5JEE6JkBsTY7y9eTmUbtg9+a9R/fjedOfBdAFxDBI7sgRIc/Nc0EmEZdkZiRd+0PQXH+QguyVTZ4EURSTWPg==; s=purelymail1; d=purelymail.com; v=1; bh=HjMYWVXq9anMOHoOIMlrIO76slqc4xHGVLLkNsbJ0oA=; h=Feedback-ID:Received:From:To:Subject:Date; Feedback-ID: 81901:11097:null:purelymail X-Pm-Original-To: u-boot@lists.denx.de Received: by smtp.purelymail.com (Purelymail SMTP) with ESMTPSA id -499528210; (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384); Tue, 28 Jan 2025 21:39:31 +0000 (UTC) From: Justin Klaassen To: u-boot@lists.denx.de Cc: Justin Klaassen , Dragan Simic , Jonas Karlman , Kever Yang , Philipp Tomsich , Philipp Tomsich , Simon Glass , Tom Rini Subject: [PATCH v2 4/5] rockchip: rk3399-nanopi-4: Allow MMC driver to control SD regulators Date: Tue, 28 Jan 2025 21:37:36 +0000 Message-ID: <20250128213852.465664-5-justin@tidylabs.net> X-Mailer: git-send-email 2.45.3 In-Reply-To: <20250128213852.465664-1-justin@tidylabs.net> References: <20250128213852.465664-1-justin@tidylabs.net> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by Purelymail Content-Type: text/plain; charset=UTF-8 X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.39 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.8 at phobos.denx.de X-Virus-Status: Clean This change removes the "regulator-always-on" property from the "vcc3v0_sd" (vmmc-supply) and "vcc_sdio" (vqmmc-supply) regulators, which otherwise prevents the MMC driver from being able to power cycle the SD card as part of the initialization procedure. It also removes the "regulator-boot-on" from the "vcc_sdio" regulator, which could theoretically damage a SD card that is already initialized in a low voltage mode. Signed-off-by: Justin Klaassen --- Changes in v2: - Added patch to remove device-tree properties that conflicted with MMC dri= ver initialization arch/arm/dts/rk3399-nanopi4-u-boot.dtsi | 3 +++ 1 file changed, 3 insertions(+) diff --git a/arch/arm/dts/rk3399-nanopi4-u-boot.dtsi b/arch/arm/dts/rk3399-= nanopi4-u-boot.dtsi index 75736124996..ba2b73223d4 100644 --- a/arch/arm/dts/rk3399-nanopi4-u-boot.dtsi +++ b/arch/arm/dts/rk3399-nanopi4-u-boot.dtsi @@ -19,8 +19,11 @@ =20 &vcc3v0_sd { =09bootph-pre-ram; +=09/delete-property/ regulator-always-on; }; =20 &vcc_sdio { +=09/delete-property/ regulator-always-on; +=09/delete-property/ regulator-boot-on; =09regulator-init-microvolt =3D <3000000>; }; --=20 2.45.3