From: Jeffrey Hugo <jeffrey.l.hugo@gmail.com>
To: agross@kernel.org, bjorn.andersson@linaro.org
Cc: lgirdwood@gmail.com, broonie@kernel.org, robh+dt@kernel.org,
mark.rutland@arm.com, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Jeffrey Hugo <jeffrey.l.hugo@gmail.com>
Subject: [PATCH v5 3/5] arm64: dts: msm8998-mtp: Add pm8005_s1 regulator
Date: Mon, 17 Jun 2019 11:37:58 -0700 [thread overview]
Message-ID: <20190617183759.13605-1-jeffrey.l.hugo@gmail.com> (raw)
In-Reply-To: <20190617183643.13449-1-jeffrey.l.hugo@gmail.com>
The pm8005_s1 is VDD_GFX, and needs to be on to enable the GPU.
This should be hooked up to the GPU CPR, but we don't have support for that
yet, so until then, just turn on the regulator and keep it on so that we
can focus on basic GPU bringup.
Signed-off-by: Jeffrey Hugo <jeffrey.l.hugo@gmail.com>
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
---
arch/arm64/boot/dts/qcom/msm8998-mtp.dtsi | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8998-mtp.dtsi b/arch/arm64/boot/dts/qcom/msm8998-mtp.dtsi
index f09f3e03f708..108667ce4f31 100644
--- a/arch/arm64/boot/dts/qcom/msm8998-mtp.dtsi
+++ b/arch/arm64/boot/dts/qcom/msm8998-mtp.dtsi
@@ -27,6 +27,23 @@
status = "okay";
};
+&pm8005_lsid1 {
+ pm8005-regulators {
+ compatible = "qcom,pm8005-regulators";
+
+ vdd_s1-supply = <&vph_pwr>;
+
+ pm8005_s1: s1 { /* VDD_GFX supply */
+ regulator-min-microvolt = <524000>;
+ regulator-max-microvolt = <1100000>;
+ regulator-enable-ramp-delay = <500>;
+
+ /* hack until we rig up the gpu consumer */
+ regulator-always-on;
+ };
+ };
+};
+
&qusb2phy {
status = "okay";
--
2.17.1
next prev parent reply other threads:[~2019-06-17 18:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 18:36 [PATCH v5 0/5] PM8005 and PMS405 regulator support Jeffrey Hugo
2019-06-17 18:37 ` [PATCH v5 1/5] dt-bindings: qcom_spmi: Document PM8005 regulators Jeffrey Hugo
2019-06-18 18:33 ` Applied "dt-bindings: qcom_spmi: Document PM8005 regulators" to the regulator tree Mark Brown
2019-06-17 18:37 ` [PATCH v5 2/5] regulator: qcom_spmi: Add support for PM8005 Jeffrey Hugo
2019-06-18 18:33 ` Applied "regulator: qcom_spmi: Add support for PM8005" to the regulator tree Mark Brown
2019-06-17 18:37 ` Jeffrey Hugo [this message]
2019-06-18 18:33 ` Applied "arm64: dts: msm8998-mtp: Add pm8005_s1 regulator" " Mark Brown
2019-06-17 18:38 ` [PATCH v5 4/5] dt-bindings: qcom_spmi: Document pms405 support Jeffrey Hugo
2019-06-18 18:33 ` Applied "dt-bindings: qcom_spmi: Document pms405 support" to the regulator tree Mark Brown
2019-06-17 18:38 ` [PATCH v5 5/5] regulator: qcom_spmi: add PMS405 SPMI regulator Jeffrey Hugo
2019-06-18 18:33 ` Applied "regulator: qcom_spmi: add PMS405 SPMI regulator" to the regulator tree Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190617183759.13605-1-jeffrey.l.hugo@gmail.com \
--to=jeffrey.l.hugo@gmail.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).