From: Ilias Apalodimas <ilias.apalodimas@linaro.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Maximilian Luz <luzmaximilian@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
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 15:24:15 +0300 [thread overview]
Message-ID: <CAC_iWjLkSkON99xXoXphY4JWDZXy_OuOye3T_vPru8aj+j=abw@mail.gmail.com> (raw)
In-Reply-To: <20220728113347.ver6argevzmlsc2c@bogus>
On Thu, 28 Jul 2022 at 14:33, Sudeep Holla <sudeep.holla@arm.com> wrote:
>
> On Thu, Jul 28, 2022 at 12:48:19PM +0200, Maximilian Luz wrote:
>
> [...]
>
> >
> > I would very much like to avoid the need for special bootloaders. The
> > devices we're talking about are WoA devices, meaning they _should_
> > ideally boot just fine with EFI and ACPI.
> >
>
> Completely agreed.
This is not a special bootloader though. Quite the opposite. It's a
standard UEFI compliant bootloader, which uses the fact that EFI is
supposed to be extensible. It installs a linux specific config table,
similar to how we install a linux specific protocol to load our initrd
and it's certainly lot more scalable than adding new stuff to the
device tree.
>
> > From an end-user perspective, it's annoying enough that we'll have to
> > stick with DTs for the time being due to the use of PEPs in ACPI.
>
> But have we explored or investigated what it takes to rewrite ACPI f/w
> to just use standard methods ? Does it require more firmware changes or
> new firmware entities or impossible at any cost ?
>
> For me that is more important than just getting this one on DT. Because
> if you take that path, we will have to keep doing that, with loads of
> unnecessary drivers if they are not shared with any other SoC with DT
> support upstream. We might also miss chance to get things added to the ACPI
> spec as we don't care which means that we never be able to use ACPI on
> similar future platforms even though they get shipped with ACPI.
>
> It will be a loop where we constantly keep converting this ACPI shipped
> platform into DT upstream. IMHO we don't want to be there.
>
> --
> Regards,
> Sudeep
Regards
/Ilias
next prev parent reply other threads:[~2022-07-28 12:25 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 [this message]
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
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='CAC_iWjLkSkON99xXoXphY4JWDZXy_OuOye3T_vPru8aj+j=abw@mail.gmail.com' \
--to=ilias.apalodimas@linaro.org \
--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=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luzmaximilian@gmail.com \
--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).