From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Subject: [PATCH v3 3/8] arm64: dts: qcom: sdm630: disable GPU by default
Date: Sat, 14 May 2022 02:45:13 +0300 [thread overview]
Message-ID: <20220513234518.3068480-4-dmitry.baryshkov@linaro.org> (raw)
In-Reply-To: <20220513234518.3068480-1-dmitry.baryshkov@linaro.org>
The SoC's device tree file disables gpucc and adreno's SMMU by default.
So let's disable the GPU too. Moreover it looks like SMMU might be not
usable without additional patches (which means that GPU is unusable
too). No board uses GPU at this moment.
Fixes: 5cf69dcbec8b ("arm64: dts: qcom: sdm630: Add Adreno 508 GPU configuration")
Reviewed-by: Konrad Dybcio <konrad.dybcio@somainline.org>
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
---
arch/arm64/boot/dts/qcom/sdm630.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sdm630.dtsi b/arch/arm64/boot/dts/qcom/sdm630.dtsi
index 8697d40e9b74..e8bb170e8b2f 100644
--- a/arch/arm64/boot/dts/qcom/sdm630.dtsi
+++ b/arch/arm64/boot/dts/qcom/sdm630.dtsi
@@ -1050,6 +1050,8 @@ adreno_gpu: gpu@5000000 {
operating-points-v2 = <&gpu_sdm630_opp_table>;
+ status = "disabled";
+
gpu_sdm630_opp_table: opp-table {
compatible = "operating-points-v2";
opp-775000000 {
--
2.35.1
next prev parent reply other threads:[~2022-05-14 1:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 23:45 [PATCH v3 0/8] arm64: dts: qcom: initial Inforce IFC6560 board support Dmitry Baryshkov
2022-05-13 23:45 ` [PATCH v3 1/8] arm64: dts: qcom: sdm660: disable dsi1/dsi1_phy by default Dmitry Baryshkov
2022-05-13 23:45 ` [PATCH v3 2/8] arm64: dts: qcom: sdm630: " Dmitry Baryshkov
2022-05-14 9:37 ` Marijn Suijten
2022-05-14 12:59 ` Dmitry Baryshkov
2022-05-13 23:45 ` Dmitry Baryshkov [this message]
2022-05-14 9:54 ` [PATCH v3 3/8] arm64: dts: qcom: sdm630: disable GPU " Marijn Suijten
2022-05-13 23:45 ` [PATCH v3 4/8] arm64: dts: qcom: sdm630: fix the qusb2phy ref clock Dmitry Baryshkov
2022-05-14 9:56 ` Marijn Suijten
2022-05-14 13:00 ` Dmitry Baryshkov
2022-05-13 23:45 ` [PATCH v3 5/8] arm64: dts: qcom: sdm630: add second (HS) USB host support Dmitry Baryshkov
2022-05-14 10:11 ` Marijn Suijten
2022-05-13 23:45 ` [PATCH v3 6/8] arm64: dts: qcom: sdm630: use defined symbols for interconnects Dmitry Baryshkov
2022-05-14 9:45 ` Marijn Suijten
2022-05-14 12:51 ` Dmitry Baryshkov
2022-05-15 14:44 ` Marijn Suijten
2022-05-15 18:05 ` Dmitry Baryshkov
2022-05-13 23:45 ` [PATCH v3 7/8] arm64: dts: qcom: sdm660: Add initial Inforce IFC6560 board support Dmitry Baryshkov
2022-05-14 10:31 ` Marijn Suijten
2022-05-14 13:09 ` Dmitry Baryshkov
2022-05-13 23:45 ` [PATCH v3 8/8] dt-bindings: arm: qcom: document sda660 SoC and ifc6560 board Dmitry Baryshkov
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=20220513234518.3068480-4-dmitry.baryshkov@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--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).