From: Maximilian Luz <luzmaximilian@gmail.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Ard Biesheuvel <ardb@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Steev Klimaszewski <steev@kali.org>,
Shawn Guo <shawn.guo@linaro.org>,
Cristian Marussi <cristian.marussi@arm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-arm-msm@vger.kernel.org, linux-efi@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] dt-bindings: firmware: Add Qualcomm UEFI Secure Application client
Date: Thu, 28 Jul 2022 16:09:44 +0200 [thread overview]
Message-ID: <d16d14fd-3edc-32f8-d00b-23b4b8a799fa@gmail.com> (raw)
In-Reply-To: <20220728134222.hs2v75zkxgtcctrx@bogus>
On 7/28/22 15:42, Sudeep Holla wrote:
> On Thu, Jul 28, 2022 at 01:45:57PM +0200, Maximilian Luz wrote:
>>
>> Would something like this work for you: Add a compatible for the TrEE
>> interface (e.g. qcom,sc8180x-tee) but not for the specific apps running
>
> IIUC, you would introduce a compatible for each unique production if there
> is a need. This constitutes as a strong need for that, but you need just
> that, no need to have any notion or info to indicate TrEE/TEE as you know
> this product runs those in TEE.
>
> In short, just use the platform specific(not SoC or SoC family) specific
> compatible to initialise your driver and don't introduce any specific
> compatible for this particular firmware interface need.
As Krzysztof mentioned, it would be good to ensure proper device
ordering wrt. SCM. Having a device node for the overall TrEE interface
would allow specifying that via DT. We could then still use the platform
compatible to load the specific things inside that driver.
Alternatively, we would need to do this extra stuff in qcom_scm.
I think separating this from qcom_scm into a new driver would be better
from a code separation and maintenance point of view. Also, this
reflects what's present in ACPI: There is a QCOM040B device for SCM and
a QCOM0476 device for TrEE.
Regards,
Max
next prev parent reply other threads:[~2022-07-28 14:10 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 22:49 [PATCH 0/4] firmware: Add support for Qualcomm UEFI Secure Application Maximilian Luz
2022-07-23 22:49 ` [PATCH 1/4] firmware: qcom_scm: Export SCM call functions Maximilian Luz
2022-07-23 22:49 ` [PATCH 2/4] firmware: Add support for Qualcomm Trusted Execution Environment SCM calls Maximilian Luz
2022-07-23 22:49 ` [PATCH 3/4] firmware: Add support for Qualcomm UEFI Secure Application Maximilian Luz
2023-01-17 8:24 ` Johan Hovold
2023-01-17 8:42 ` Maximilian Luz
2023-01-18 20:45 ` Maximilian Luz
2023-01-19 16:47 ` Johan Hovold
2023-01-19 17:19 ` Maximilian Luz
2023-01-17 11:05 ` Johan Hovold
2023-01-17 12:07 ` Maximilian Luz
2022-07-23 22:49 ` [PATCH 4/4] dt-bindings: firmware: Add Qualcomm UEFI Secure Application client Maximilian Luz
2022-07-25 1:06 ` Rob Herring
2022-07-26 10:17 ` Krzysztof Kozlowski
2022-07-26 11:15 ` Maximilian Luz
2022-07-26 13:25 ` Krzysztof Kozlowski
2022-07-26 15:00 ` Maximilian Luz
2022-07-27 11:24 ` Krzysztof Kozlowski
2022-07-27 13:00 ` Maximilian Luz
2022-07-28 7:48 ` Krzysztof Kozlowski
2022-07-28 10:25 ` Maximilian Luz
2022-07-28 10:38 ` Krzysztof Kozlowski
2022-07-28 10:49 ` Maximilian Luz
2022-07-26 14:30 ` Sudeep Holla
2022-07-26 15:15 ` Maximilian Luz
2022-07-26 15:41 ` Sudeep Holla
2022-07-26 17:01 ` Maximilian Luz
2022-07-27 11:38 ` Krzysztof Kozlowski
2022-07-27 13:03 ` Maximilian Luz
2022-07-27 13:24 ` Sudeep Holla
2022-07-27 14:49 ` Maximilian Luz
2022-07-28 6:03 ` Ilias Apalodimas
2022-07-28 10:48 ` Maximilian Luz
2022-07-28 11:33 ` Sudeep Holla
2022-07-28 12:13 ` Maximilian Luz
2022-07-28 12:24 ` Ilias Apalodimas
2022-07-28 15:05 ` Ard Biesheuvel
2022-07-28 15:16 ` Ilias Apalodimas
2022-07-28 16:16 ` Sudeep Holla
2022-07-28 16:24 ` Konrad Dybcio
2022-07-28 12:35 ` Ilias Apalodimas
2022-07-28 12:49 ` Maximilian Luz
2022-07-28 16:56 ` Ilias Apalodimas
2022-07-28 17:27 ` Maximilian Luz
2022-07-29 8:52 ` Sudeep Holla
2022-07-29 15:11 ` Maximilian Luz
2022-07-31 9:54 ` Ilias Apalodimas
2022-07-31 22:48 ` Maximilian Luz
2022-07-28 8:23 ` Sudeep Holla
2022-07-28 10:05 ` Maximilian Luz
2022-07-28 11:21 ` Sudeep Holla
2022-07-28 11:45 ` Maximilian Luz
2022-07-28 13:42 ` Sudeep Holla
2022-07-28 14:09 ` Maximilian Luz [this message]
2022-07-25 19:27 ` [PATCH 0/4] firmware: Add support for Qualcomm UEFI Secure Application Rob Herring
2022-07-25 20:16 ` Maximilian Luz
2022-08-02 11:51 ` Srinivas Kandagatla
2022-08-02 13:22 ` Maximilian Luz
2022-08-02 14:02 ` Ard Biesheuvel
2022-08-02 19:11 ` Maximilian Luz
2022-09-02 7:26 ` Sumit Garg
2022-09-02 13:18 ` Maximilian Luz
2022-09-05 6:50 ` Sumit Garg
2022-11-23 11:22 ` Srinivas Kandagatla
2022-11-23 12:05 ` 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=d16d14fd-3edc-32f8-d00b-23b4b8a799fa@gmail.com \
--to=luzmaximilian@gmail.com \
--cc=agross@kernel.org \
--cc=ardb@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=cristian.marussi@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=shawn.guo@linaro.org \
--cc=steev@kali.org \
--cc=sudeep.holla@arm.com \
/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).