From nobody Tue Feb 10 09:59:09 2026 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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 544A1CA0FFD for ; Tue, 5 Sep 2023 17:09:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1354114AbjIERHN (ORCPT ); Tue, 5 Sep 2023 13:07:13 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46614 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1354092AbjIEQ3Y (ORCPT ); Tue, 5 Sep 2023 12:29:24 -0400 Received: from mail-ej1-x634.google.com (mail-ej1-x634.google.com [IPv6:2a00:1450:4864:20::634]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BF1F83C16 for ; Tue, 5 Sep 2023 09:21:06 -0700 (PDT) Received: by mail-ej1-x634.google.com with SMTP id a640c23a62f3a-9936b3d0286so420585366b.0 for ; Tue, 05 Sep 2023 09:21:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1693930780; x=1694535580; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=wa8S3640iWUkpmAXcApvED+QJgBuG0siUdi8y84+QOg=; b=zSThOYB2hTL/eUV+RF9pTbmJp1ssw6irK2KPJGGWRO/cqFE+h0AH8yrWH+ewbPB1LL wLLfZrGVX9iKlcXhLM/2Hy/gvAk83Cdy3zpfdWJjnvx/VcsTuEdylG5Nl1GKtVjuygLr q4kHebnzhg2Ti+h4M9dBYQMAF7IFcmGnFctITo7v3ECLtzvIPGt1NkHJvMHK1JaFpTps wzW8DXUmo0iCJyB9wt3pK0Xykfbau2SRaIpbB7ivGq/fA1VhgAR50dN4dKEq14TIchrK C5PZMVJc3NFLwOxga36CSZ32mJGUFJOA0FQpTJs27D+HpEq+lxarMwbgWQW573g4c4CS n18w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693930780; x=1694535580; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=wa8S3640iWUkpmAXcApvED+QJgBuG0siUdi8y84+QOg=; b=H55TLjX+2Kdz1j+ct44FJU1SO4eXQ/qVmAjRQDRIseX7m1Aw5n3LfmdI0Mb7lpy1k1 lqhwqVpM+kHi8F67gB6AmOJRamlho3XceOYI8EpV5ahEpebIhDV4gyPvIh6sxXlxVCMR j2C0hElBhC/EjxgFFoLMUaTaeLPqlXGwXWV+60ARNvcqlSbOfxT8M+/uEUZlV4QRpwzg +RT+tA4NJOraXS3xXbtHTSMiACO8TkMVf18KAX5dJ9hutfdcOn3w8w+tkh8B/5be+kPC 9VB/bZdG6vP9wx+SRfQdtd7UWEQ3ZfI/BNa/UUtMuD8N3Uh7h1aWRjWCMe5QViG5iarK rGPA== X-Gm-Message-State: AOJu0Yxa9yxU4TG3wpRT42z8BgMW6gC10YECyTZCx0cFf8zma5jtLJf1 i9bZqj8Rd5UF+GMXYFSaTGbIpg== X-Google-Smtp-Source: AGHT+IESfv2tKGY9sWI6xhuBrGlNmksCn2wXFYAMdyLFWK3lMFwDIQDIPWPCxfg7uX/4mXrqjrYqBA== X-Received: by 2002:a17:906:18aa:b0:9a1:d087:e0bf with SMTP id c10-20020a17090618aa00b009a1d087e0bfmr237260ejf.43.1693930780565; Tue, 05 Sep 2023 09:19:40 -0700 (PDT) Received: from krzk-bin.. (77-252-46-238.static.ip.netia.com.pl. [77.252.46.238]) by smtp.gmail.com with ESMTPSA id v26-20020a170906489a00b0099cc36c4681sm7743165ejq.157.2023.09.05.09.19.39 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 05 Sep 2023 09:19:40 -0700 (PDT) From: Krzysztof Kozlowski To: Andy Gross , Bjorn Andersson , Konrad Dybcio , Rob Herring , Krzysztof Kozlowski , Conor Dooley , linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Krzysztof Kozlowski Subject: [PATCH 11/12] arm64: dts: qcom: msm8998-sagit: correct UFS pad supply Date: Tue, 5 Sep 2023 18:19:19 +0200 Message-Id: <20230905161920.252013-12-krzysztof.kozlowski@linaro.org> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20230905161920.252013-1-krzysztof.kozlowski@linaro.org> References: <20230905161920.252013-1-krzysztof.kozlowski@linaro.org> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Type: text/plain; charset="utf-8" The Qualcomm UFS phy switched from dedicated driver to QMP phy driver. Eventually the old driver was removed in commit 02dca8c981b5 ("phy: qcom: remove ufs qmp phy driver"). The original driver and its binding used vddp-ref-clk regulator supply, but the new one did not and left the supply unused. The Qualcomm UFS phy bindings were also migrated to newer ones and dropped support for vddp-ref-clk regulator in commit dc5cb63592bd ("dt-bindings: phy: migrate QMP UFS PHY bindings to qcom,sc8280xp-qmp-ufs-phy.yaml"). It turns out that this regulator, although with inaccurate name vddp-ref-clk, is actually needed to provide supply for VDD_PX10 (or similar, depending on the SoC) used by UFS controller. Bring back handling of this supply by using more appropriate regulator - UFS controller host supply. This also fixes dtbs_check warning: msm8998-xiaomi-sagit.dtb: phy@1da7000: 'vddp-ref-clk-supply' does not mat= ch any of the regexes: 'pinctrl-[0-9]+' Signed-off-by: Krzysztof Kozlowski Reviewed-by: Konrad Dybcio --- arch/arm64/boot/dts/qcom/msm8998-xiaomi-sagit.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm64/boot/dts/qcom/msm8998-xiaomi-sagit.dts b/arch/arm64= /boot/dts/qcom/msm8998-xiaomi-sagit.dts index 437b30cc8bdc..0cac06f25a77 100644 --- a/arch/arm64/boot/dts/qcom/msm8998-xiaomi-sagit.dts +++ b/arch/arm64/boot/dts/qcom/msm8998-xiaomi-sagit.dts @@ -667,6 +667,7 @@ &ufshc { vcc-supply =3D <&vreg_l20a_2p95>; vccq-supply =3D <&vreg_l26a_1p2>; vccq2-supply =3D <&vreg_s4a_1p8>; + vdd-hba-supply =3D <&vreg_l26a_1p2>; vcc-max-microamp =3D <750000>; vccq-max-microamp =3D <560000>; vccq2-max-microamp =3D <750000>; @@ -676,7 +677,6 @@ &ufshc { &ufsphy { vdda-phy-supply =3D <&vreg_l1a_0p875>; vdda-pll-supply =3D <&vreg_l2a_1p2>; - vddp-ref-clk-supply =3D <&vreg_l26a_1p2>; status =3D "okay"; }; =20 --=20 2.34.1