From: Jeya R <jeyr@codeaurora.org>
To: linux-arm-msm@vger.kernel.org, srinivas.kandagatla@linaro.org
Cc: Jeya R <jeyr@codeaurora.org>,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
fastrpc.upstream@qti.qualcomm.com
Subject: [PATCH 1/4] dt-bindings: devicetree documentation for secure domain
Date: Fri, 24 Sep 2021 17:49:08 +0530 [thread overview]
Message-ID: <1632485951-13473-2-git-send-email-jeyr@codeaurora.org> (raw)
In-Reply-To: <1632485951-13473-1-git-send-email-jeyr@codeaurora.org>
Add information about secure domain property.
Signed-off-by: Jeya R <jeyr@codeaurora.org>
---
Documentation/devicetree/bindings/misc/qcom,fastrpc.txt | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindings/misc/qcom,fastrpc.txt b/Documentation/devicetree/bindings/misc/qcom,fastrpc.txt
index 2a1827a..276c1d1 100644
--- a/Documentation/devicetree/bindings/misc/qcom,fastrpc.txt
+++ b/Documentation/devicetree/bindings/misc/qcom,fastrpc.txt
@@ -49,6 +49,12 @@ on the dsp.
context bank. Defaults to 1 when this property
is not specified.
+- secure-domains:
+ Usage: Optional
+ Value type: <empty>
+ Definition: Specify DSP domain is secure, must be
+ "qcom,secure-domain"
+
Example:
adsp-pil {
--
2.7.4
next prev parent reply other threads:[~2021-09-24 12:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 12:19 [PATCH 0/4] Add secure domains support Jeya R
2021-09-24 12:19 ` Jeya R [this message]
2021-09-29 14:06 ` [PATCH 1/4] dt-bindings: devicetree documentation for secure domain Srinivas Kandagatla
2021-09-24 12:19 ` [PATCH 2/4] misc: fastrpc: Add secure device node support Jeya R
2021-09-24 12:19 ` [PATCH 3/4] misc: fastrpc: Set channel as secure Jeya R
2021-09-29 14:07 ` Srinivas Kandagatla
2021-09-24 12:19 ` [PATCH 4/4] misc: fastrpc: reject non-secure node for secure domain Jeya R
2021-09-29 14:06 ` Srinivas Kandagatla
2021-09-29 14:06 ` [PATCH 0/4] Add secure domains support Srinivas Kandagatla
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=1632485951-13473-2-git-send-email-jeyr@codeaurora.org \
--to=jeyr@codeaurora.org \
--cc=fastrpc.upstream@qti.qualcomm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.kandagatla@linaro.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).