[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220723224949.1089973-5-luzmaximilian@gmail.com>
Date: Sun, 24 Jul 2022 00:49:49 +0200
From: Maximilian Luz <luzmaximilian@...il.com>
To: Andy Gross <agross@...nel.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Ard Biesheuvel <ardb@...nel.org>
Cc: Konrad Dybcio <konrad.dybcio@...ainline.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Steev Klimaszewski <steev@...i.org>,
Shawn Guo <shawn.guo@...aro.org>,
Sudeep Holla <sudeep.holla@....com>,
Cristian Marussi <cristian.marussi@....com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-arm-msm@...r.kernel.org, linux-efi@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Maximilian Luz <luzmaximilian@...il.com>
Subject: [PATCH 4/4] dt-bindings: firmware: Add Qualcomm UEFI Secure Application client
Add bindings for the Qualcomm Trusted Execution Environment (TrEE) UEFI
Secure application (uefisecapp) client.
Signed-off-by: Maximilian Luz <luzmaximilian@...il.com>
---
.../firmware/qcom,tee-uefisecapp.yaml | 38 +++++++++++++++++++
MAINTAINERS | 1 +
2 files changed, 39 insertions(+)
create mode 100644 Documentation/devicetree/bindings/firmware/qcom,tee-uefisecapp.yaml
diff --git a/Documentation/devicetree/bindings/firmware/qcom,tee-uefisecapp.yaml b/Documentation/devicetree/bindings/firmware/qcom,tee-uefisecapp.yaml
new file mode 100644
index 000000000000..9e5de1005d5c
--- /dev/null
+++ b/Documentation/devicetree/bindings/firmware/qcom,tee-uefisecapp.yaml
@@ -0,0 +1,38 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/soc/qcom/qcom,rpmh-rsc.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Qualcomm Trusted Execution Environment UEFI Secure Application
+
+maintainers:
+ - Maximilian Luz <luzmaximilian@...il.com>
+
+description: |
+ Various Qualcomm SoCs do not allow direct access to UEFI variables. Instead,
+ these need to be accessed via the UEFI Secure Application (uefisecapp),
+ residing in the Trusted Execution Environment (TrEE). These bindings mark the
+ presence of uefisecapp and allow the respective client driver to load and
+ install efivar operations, providing the kernel with access to UEFI
+ variables.
+
+properties:
+ compatible:
+ const: qcom,tee-uefisecapp
+
+required:
+ - compatible
+
+additionalProperties: false
+
+examples:
+ - |
+ firmware {
+ scm {
+ compatible = "qcom,scm-sc8180x", "qcom,scm";
+ };
+ tee-uefisecapp {
+ compatible = "qcom,tee-uefisecapp";
+ };
+ };
diff --git a/MAINTAINERS b/MAINTAINERS
index 6e014e16fc82..00436245189d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -16607,6 +16607,7 @@ QUALCOMM UEFISECAPP DRIVER
M: Maximilian Luz <luzmaximilian@...il.com>
L: linux-arm-msm@...r.kernel.org
S: Maintained
+F: Documentation/devicetree/bindings/firmware/qcom,tee-uefisecapp.yaml
F: drivers/firmware/qcom_tee_uefisecapp.c
QUALCOMM VENUS VIDEO ACCELERATOR DRIVER
--
2.37.1
Powered by blists - more mailing lists