From: Neil Armstrong <neil.armstrong@linaro.org>
To: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Neil Armstrong <neil.armstrong@linaro.org>
Subject: [PATCH 0/3] arm64: dts: qcom: sm8[456]50: add missing qcom,non-secure-domain property
Date: Tue, 27 Feb 2024 13:53:03 +0100 [thread overview]
Message-ID: <20240227-topic-sm8x50-upstream-fastrpc-non-secure-domain-v1-0-15c4c864310f@linaro.org> (raw)
By default the DSP domains are non secure, add the missing
qcom,non-secure-domain property to SM8450, SM8550 and SM8650
in order to mark them as non-secure.
Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
---
Neil Armstrong (3):
arm64: dts: qcom: sm8450: add missing qcom,non-secure-domain property
arm64: dts: qcom: sm8550: add missing qcom,non-secure-domain property
arm64: dts: qcom: sm8650: add missing qcom,non-secure-domain property
arch/arm64/boot/dts/qcom/sm8450.dtsi | 3 +++
arch/arm64/boot/dts/qcom/sm8550.dtsi | 2 ++
arch/arm64/boot/dts/qcom/sm8650.dtsi | 4 ++++
3 files changed, 9 insertions(+)
---
base-commit: 22ba90670a51a18c6b36d285fddf92b9887c0bc3
change-id: 20240227-topic-sm8x50-upstream-fastrpc-non-secure-domain-a2137ad19135
Best regards,
--
Neil Armstrong <neil.armstrong@linaro.org>
next reply other threads:[~2024-02-27 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 12:53 Neil Armstrong [this message]
2024-02-27 12:53 ` [PATCH 1/3] arm64: dts: qcom: sm8450: add missing qcom,non-secure-domain property Neil Armstrong
2024-02-27 12:53 ` [PATCH 2/3] arm64: dts: qcom: sm8550: " Neil Armstrong
2024-02-27 12:53 ` [PATCH 3/3] arm64: dts: qcom: sm8650: " Neil Armstrong
2024-03-19 2:48 ` [PATCH 0/3] arm64: dts: qcom: sm8[456]50: " Bjorn Andersson
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=20240227-topic-sm8x50-upstream-fastrpc-non-secure-domain-v1-0-15c4c864310f@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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).