From: Maximilian Luz <luzmaximilian@gmail.com>
To: Trilok Soni <quic_tsoni@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>
Cc: Andy Gross <agross@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Ard Biesheuvel <ardb@kernel.org>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Johan Hovold <johan@kernel.org>,
Steev Klimaszewski <steev@kali.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Johan Hovold <johan+linaro@kernel.org>
Subject: Re: [PATCH v6 3/3] firmware: Add support for Qualcomm UEFI Secure Application
Date: Sun, 27 Aug 2023 23:53:08 +0200 [thread overview]
Message-ID: <072b3df6-09fb-98a8-2b58-41dfcabd98c0@gmail.com> (raw)
In-Reply-To: <0d7697fd-11b3-1d4a-78da-7e5eb293d186@quicinc.com>
On 8/27/23 23:26, Trilok Soni wrote:
> On 8/27/2023 2:14 PM, Maximilian Luz wrote:
>>
>> +config QCOM_QSEECOM_UEFISECAPP
>> + bool "Qualcomm SEE UEFI Secure App client driver"
>
> Why not "tristate"? This driver can be a loadable module, right?
As I understand, modular efivars have still not been fully sorted out in
the kernel. For example, userspace could try and mount efivarfs before
the module has been loaded and by that erroneously determine that the
system doesn't support efivars. So requiring it to be built in for now
is more of a workaround (which has been suggested by Johan Hovold).
There is no technical limitation in this part of the code itself, so
enabling it (and QCOM_QSEECOM for that matter) to be built as module
should be fairly straightforward once that's been sorted out.
>> + depends on QCOM_QSEECOM
>> + depends on EFI
>> + help
>
>
next prev parent reply other threads:[~2023-08-27 21:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-27 21:14 [PATCH v6 0/3] " Maximilian Luz
2023-08-27 21:14 ` [PATCH v6 1/3] lib/ucs2_string: Add UCS-2 strscpy function Maximilian Luz
2023-08-27 21:14 ` [PATCH v6 2/3] firmware: qcom_scm: Add support for Qualcomm Secure Execution Environment SCM interface Maximilian Luz
2023-08-27 21:14 ` [PATCH v6 3/3] firmware: Add support for Qualcomm UEFI Secure Application Maximilian Luz
2023-08-27 21:26 ` Trilok Soni
2023-08-27 21:53 ` Maximilian Luz [this message]
2023-08-27 21:59 ` Trilok Soni
2023-09-07 20:52 ` Maximilian Luz
2023-09-07 22:05 ` Trilok Soni
2023-09-07 20:40 ` Bjorn Andersson
2023-09-14 16:04 ` [PATCH v6 0/3] " Bjorn Andersson
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=072b3df6-09fb-98a8-2b58-41dfcabd98c0@gmail.com \
--to=luzmaximilian@gmail.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=ardb@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=johan+linaro@kernel.org \
--cc=johan@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_tsoni@quicinc.com \
--cc=srinivas.kandagatla@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
all inboxes | Powered by JetHome®