From nobody Tue Feb 10 13:17:12 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 448B2CA0FFC for ; Tue, 5 Sep 2023 17:09:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1354093AbjIERHI (ORCPT ); Tue, 5 Sep 2023 13:07:08 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57842 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1354119AbjIEQ3Z (ORCPT ); Tue, 5 Sep 2023 12:29:25 -0400 Received: from mail-ej1-x62f.google.com (mail-ej1-x62f.google.com [IPv6:2a00:1450:4864:20::62f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 969583C32 for ; Tue, 5 Sep 2023 09:21:09 -0700 (PDT) Received: by mail-ej1-x62f.google.com with SMTP id a640c23a62f3a-99c4923195dso410343366b.2 for ; Tue, 05 Sep 2023 09:21:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1693930781; x=1694535581; 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=eDCWmN0mPD6hCatLBKjMrDlxIVWIUgJK7MJJd+ho5Vc=; b=C24tzWljiND8ZSX2Q9XcXWrw5KzBNfxeI36ALjVBB6tXRY319eVKA+8UWQYymxmLtJ Piq8sL5C5JSFPXCICJCnHwrvom4E1D4C+kqU8Q/MxZ3xwAW8wH8NYqc0yqi4xTIc7B8K QfktPdbT4zDGv6Rs3n6+xc6JpwKP7G7ebIlhgUwyZZpNKdq442EXgioUZVyxGJpmwIdU W9MP9pmUaaHLczIBRMZkzMPhjNh5CTaqQkHCwOgB2E+xxumNl1e+orz8GzDq+Y9VfqQZ jnaATnQCBzEL9wTu7oW7+LL/0ZurhpebogwTLgJ8+AJli0Lu6j/Mp6xRa2IUfrhrxF7g pzPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693930781; x=1694535581; 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=eDCWmN0mPD6hCatLBKjMrDlxIVWIUgJK7MJJd+ho5Vc=; b=hPcbtT4SpFI85BLXJUzxXO0wWJe1E1F+WPJQtTzGFPJ75Ofa25wHSERa/23xsQxP6Z t2Qybyi2dhVthc3KVpTVAbTt+YFMMxNpkhJ6N0GllrC0PCVzCkhhoCXX0Cvgib9V/HUS 6BkHIemRA9K9gFt+1RuVI4xtyG5r/Z3RoLC215yERKU3M0XOYQUvISFRn7r1wVN8p2M8 BVVLiNsXnS9ewhKJ8X7b2ZiidnG/WgJaJWMgyp9URJgIhYs2DsmHrXXc/051LPQqjOtQ 3EnmD3WF9l94dJ2C/rwXsD6hHh2flK8TEAwzTRU4SAgm2WAP63EdHX0LmjL6VFsCMhod afpA== X-Gm-Message-State: AOJu0YxSnVuqzHkn/HOrut0BQHL73bkt9NthxJYdaWLxqfq48lu51mXn oBpBG7fdLjyq7D11QHnbhukN8Q== X-Google-Smtp-Source: AGHT+IHP6OBBOhp2XqNXHnK7pnzjbPCbx0swl8k5IRAOAeEg9BeQC0c2Z0DhbmOKSgrSC4rz+j6yMQ== X-Received: by 2002:a17:907:2cd8:b0:9a2:2635:dab6 with SMTP id hg24-20020a1709072cd800b009a22635dab6mr235384ejc.47.1693930781780; Tue, 05 Sep 2023 09:19:41 -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.40 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 05 Sep 2023 09:19:41 -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 12/12] arm64: dts: qcom: sm4250-billie2: correct UFS pad supply Date: Tue, 5 Sep 2023 18:19:20 +0200 Message-Id: <20230905161920.252013-13-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: sm4250-oneplus-billie2.dtb: phy@4807000: 'vddp-ref-clk-supply' does not m= atch any of the regexes: 'pinctrl-[0-9]+' Signed-off-by: Krzysztof Kozlowski Reviewed-by: Konrad Dybcio --- arch/arm64/boot/dts/qcom/sm4250-oneplus-billie2.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm64/boot/dts/qcom/sm4250-oneplus-billie2.dts b/arch/arm= 64/boot/dts/qcom/sm4250-oneplus-billie2.dts index 75951fd439df..2c7a12983dae 100644 --- a/arch/arm64/boot/dts/qcom/sm4250-oneplus-billie2.dts +++ b/arch/arm64/boot/dts/qcom/sm4250-oneplus-billie2.dts @@ -225,13 +225,13 @@ &ufs_mem_hc { vcc-max-microamp =3D <600000>; vccq2-supply =3D <&vreg_l11a>; vccq2-max-microamp =3D <600000>; + vdd-hba-supply =3D <&vreg_l18a>; status =3D "okay"; }; =20 &ufs_mem_phy { vdda-phy-supply =3D <&vreg_l4a>; vdda-pll-supply =3D <&vreg_l12a>; - vddp-ref-clk-supply =3D <&vreg_l18a>; status =3D "okay"; }; =20 --=20 2.34.1