From: Melody Olvera <quic_molvera@quicinc.com>
To: Souradeep Chowdhury <quic_schowdhu@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Trilok Soni <quic_tsoni@quicinc.com>,
Satya Durga Srinivasu Prabhala <quic_satyap@quicinc.com>,
Elson Serrao <quic_eserrao@quicinc.com>
Cc: <cros-qcom-dts-watchers@chromium.org>,
<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-usb@vger.kernel.org>,
Melody Olvera <quic_molvera@quicinc.com>
Subject: [PATCH v1 1/3] dt-bindings: soc: qcom: eud: Update compatible strings for eud
Date: Wed, 7 Aug 2024 11:32:02 -0700 [thread overview]
Message-ID: <20240807183205.803847-2-quic_molvera@quicinc.com> (raw)
In-Reply-To: <20240807183205.803847-1-quic_molvera@quicinc.com>
The EUD can more accurately be divided into two types; a secure type
which requires that certain registers be updated via scm call and a
nonsecure type which must access registers nonsecurely. Thus, change
the compatible strings to reflect secure and nonsecure eud usage.
Signed-off-by: Melody Olvera <quic_molvera@quicinc.com>
---
Documentation/devicetree/bindings/soc/qcom/qcom,eud.yaml | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/soc/qcom/qcom,eud.yaml b/Documentation/devicetree/bindings/soc/qcom/qcom,eud.yaml
index f2c5ec7e6437..476f92768610 100644
--- a/Documentation/devicetree/bindings/soc/qcom/qcom,eud.yaml
+++ b/Documentation/devicetree/bindings/soc/qcom/qcom,eud.yaml
@@ -17,8 +17,8 @@ properties:
compatible:
items:
- enum:
- - qcom,sc7280-eud
- - const: qcom,eud
+ - qcom,secure-eud
+ - qcom,eud
reg:
items:
@@ -55,7 +55,7 @@ additionalProperties: false
examples:
- |
eud@88e0000 {
- compatible = "qcom,sc7280-eud", "qcom,eud";
+ compatible = "qcom,eud";
reg = <0x88e0000 0x2000>,
<0x88e2000 0x1000>;
--
2.45.2
next prev parent reply other threads:[~2024-08-07 18:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 18:32 [PATCH v1 0/3] Add compatibles for different eud access modes Melody Olvera
2024-08-07 18:32 ` Melody Olvera [this message]
2024-08-08 11:00 ` [PATCH v1 1/3] dt-bindings: soc: qcom: eud: Update compatible strings for eud Krzysztof Kozlowski
2024-08-13 20:03 ` Melody Olvera
2024-08-14 6:15 ` Krzysztof Kozlowski
2024-08-14 10:30 ` Konrad Dybcio
2024-08-14 17:33 ` Melody Olvera
2024-08-14 20:25 ` Konrad Dybcio
2024-08-14 22:09 ` Trilok Soni
2024-08-20 18:21 ` Melody Olvera
2024-08-20 19:19 ` Konrad Dybcio
2024-08-21 6:48 ` Krzysztof Kozlowski
2024-08-21 17:27 ` Konrad Dybcio
2024-08-14 17:20 ` Melody Olvera
2024-08-07 18:32 ` [PATCH v1 2/3] usb: misc: qcom_eud: Access mode manager through secure calls Melody Olvera
2024-08-07 18:32 ` [PATCH v1 3/3] arm64: dts: qcom: sc7280: Update eud compatible string Melody Olvera
2024-08-08 11:03 ` Krzysztof Kozlowski
2024-08-13 20:05 ` Melody Olvera
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=20240807183205.803847-2-quic_molvera@quicinc.com \
--to=quic_molvera@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=quic_eserrao@quicinc.com \
--cc=quic_satyap@quicinc.com \
--cc=quic_schowdhu@quicinc.com \
--cc=quic_tsoni@quicinc.com \
--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