From: Rob Herring <robh@kernel.org>
To: Maximilian Luz <luzmaximilian@gmail.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Andy Gross <agross@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Ard Biesheuvel <ardb@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Johan Hovold <johan@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Sumit Garg <sumit.garg@linaro.org>,
Steev Klimaszewski <steev@kali.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 3/4] dt-bindings: firmware: Add Qualcomm QSEECOM interface
Date: Mon, 30 Jan 2023 15:05:30 -0600 [thread overview]
Message-ID: <20230130210530.GA3339716-robh@kernel.org> (raw)
In-Reply-To: <20230127184650.756795-4-luzmaximilian@gmail.com>
On Fri, Jan 27, 2023 at 07:46:49PM +0100, Maximilian Luz wrote:
> Add bindings for the Qualcomm Secure Execution Environment interface
> (QSEECOM).
>
> Signed-off-by: Maximilian Luz <luzmaximilian@gmail.com>
> ---
>
> Changes in v2:
> - Replaces uefisecapp bindings.
> - Fix various dt-checker complaints.
>
> ---
> .../bindings/firmware/qcom,qseecom.yaml | 49 +++++++++++++++++++
> MAINTAINERS | 1 +
> 2 files changed, 50 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/firmware/qcom,qseecom.yaml
>
> diff --git a/Documentation/devicetree/bindings/firmware/qcom,qseecom.yaml b/Documentation/devicetree/bindings/firmware/qcom,qseecom.yaml
> new file mode 100644
> index 000000000000..540a604f81bc
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/firmware/qcom,qseecom.yaml
> @@ -0,0 +1,49 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/firmware/qcom,qseecom.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Qualcomm Secure Execution Environment Communication Interface
> +
> +maintainers:
> + - Maximilian Luz <luzmaximilian@gmail.com>
> +
> +description: |
> + QSEECOM provides an interface to Qualcomm's Secure Execution Environment
> + (SEE) running in the Trust Zone via SCM calls. In particular, it allows
SCM is SMCCC or something else?
> + communication with secure applications running therein.
> +
> + Applications running in this environment can, for example, include
> + 'uefisecapp', which is required for accessing UEFI variables on certain
> + systems as these cannot be accessed directly.
> +
> +properties:
> + compatible:
> + items:
> + - enum:
> + - qcom,qseecom-sc8280xp
> + - const: qcom,qseecom
> +
> + qcom,scm:
> + $ref: '/schemas/types.yaml#/definitions/phandle'
> + description:
> + A phandle pointing to the QCOM SCM device (see ./qcom,scm.yaml).
> +
> +required:
> + - compatible
> + - qcom,scm
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + firmware {
> + scm {
> + compatible = "qcom,scm-sc8280xp", "qcom,scm";
> + };
> + qseecom {
> + compatible = "qcom,qseecom-sc8280xp", "qcom,qseecom";
> + qcom,scm = <&scm>;
Why do you need this in DT? If you already know you have a firmware
interface (via "qcom,scm"), then query the firmware to see if the SEE is
there.
Rob
next prev parent reply other threads:[~2023-01-30 21:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230127184650.756795-1-luzmaximilian@gmail.com>
2023-01-27 18:46 ` [PATCH v2 3/4] dt-bindings: firmware: Add Qualcomm QSEECOM interface Maximilian Luz
2023-01-30 21:05 ` Rob Herring [this message]
2023-01-30 21:46 ` Maximilian Luz
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=20230130210530.GA3339716-robh@kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=ardb@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=johan@kernel.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=luzmaximilian@gmail.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=steev@kali.org \
--cc=sudeep.holla@arm.com \
--cc=sumit.garg@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).