devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dzmitry Sankouski <dsankouski@gmail.com>
Cc: Dzmitry Sankouski <dsankouski@gmail.com>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: [PATCH v2 5/6] arm64: dts: qcom: starqltechn: disable crypto
Date: Tue, 24 Oct 2023 18:43:37 +0300	[thread overview]
Message-ID: <20231024154338.407191-6-dsankouski@gmail.com> (raw)
In-Reply-To: <20231024154338.407191-1-dsankouski@gmail.com>

Disable the crypto block due to it causing an SError in qce_start() on
the starqltechn, which happens upon every boot when cryptomanager tests are
enabled.

Same problem is on Lenovo C630, see
commit 382e3e0eb6a8 ("arm64: dts: qcom: c630: disable crypto due to serror")

Signed-off-by: Dzmitry Sankouski <dsankouski@gmail.com>
Link: https://lore.kernel.org/r/20211105035235.2392-1-steev@kali.org
Cc: Andy Gross <agross@kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>
Cc: Conor Dooley <conor+dt@kernel.org>
Cc: Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org
Cc: linux-arm-msm@vger.kernel.org

---

Changes in v2:
- none

 arch/arm64/boot/dts/qcom/sdm845-samsung-starqltechn.dts | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/arch/arm64/boot/dts/qcom/sdm845-samsung-starqltechn.dts b/arch/arm64/boot/dts/qcom/sdm845-samsung-starqltechn.dts
index f2bc3c412a2f..0e2c7df2baa7 100644
--- a/arch/arm64/boot/dts/qcom/sdm845-samsung-starqltechn.dts
+++ b/arch/arm64/boot/dts/qcom/sdm845-samsung-starqltechn.dts
@@ -504,6 +504,11 @@ touchscreen@48 {
 	};
 };
 
+&crypto {
+	/* FIXME: qce_start triggers an SError */
+	status = "disable";
+};
+
 /* Modem/wifi*/
 &mss_pil {
 	status = "okay";
-- 
2.30.2


  parent reply	other threads:[~2023-10-24 15:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231024154338.407191-1-dsankouski@gmail.com>
2023-10-24 15:43 ` [PATCH v2 1/6] dt-bindings: regulator: add Samsung s2dos05 pmic Dzmitry Sankouski
2023-10-24 15:59   ` Krzysztof Kozlowski
2023-10-28 16:01     ` Dzmitry Sankouski
2023-10-28 20:17       ` Krzysztof Kozlowski
2023-10-29 12:06         ` Dzmitry Sankouski
2023-10-24 16:29   ` Rob Herring
2023-10-24 15:43 ` [PATCH v2 3/6] arm64: dts: qcom: starqltechn: remove wifi Dzmitry Sankouski
2023-10-24 22:04   ` Bryan O'Donoghue
2023-10-26 19:21   ` Konrad Dybcio
2023-10-24 15:43 ` [PATCH v2 4/6] arm64: dts: qcom: starqltechn: enable more features Dzmitry Sankouski
2023-10-26 19:26   ` Konrad Dybcio
2023-10-28 17:13     ` Dzmitry Sankouski
2023-10-28 20:18       ` Krzysztof Kozlowski
2023-10-24 15:43 ` Dzmitry Sankouski [this message]
2023-10-24 22:09   ` [PATCH v2 5/6] arm64: dts: qcom: starqltechn: disable crypto Bryan O'Donoghue
2023-10-26 19:33   ` Konrad Dybcio
2023-10-24 15:43 ` [PATCH v2 6/6] arm64: dts: qcom: starqltechn: add supply to framebuffer Dzmitry Sankouski

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=20231024154338.407191-6-dsankouski@gmail.com \
    --to=dsankouski@gmail.com \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.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).