From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] firmware: qcom: scm: rework QSEECOM allowlist
Date: Mon, 4 Nov 2024 12:23:57 +0100 [thread overview]
Message-ID: <02171841-acd3-4f26-987d-1376caf11481@oss.qualcomm.com> (raw)
In-Reply-To: <20241103-rework-qseecom-v1-2-1d75d4eedc1e@linaro.org>
On 3.11.2024 4:37 PM, Dmitry Baryshkov wrote:
> Listing individual machines in qcom_scm_qseecom_allowlist doesn't scale.
> Allow it to function as allow and disallow list at the same time by the
> means of the match->data and list the SoC families instead of devices.
>
> In case a particular device has buggy or incompatible firmware user
> still can disable QSEECOM by specifying qcom_scm.qseecom=off kernel
> param and (in the longer term) adding machine-specific entry to the
> qcom_scm_qseecom_allowlist table.
>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
> drivers/firmware/qcom/qcom_scm.c | 37 ++++++++++++++++++++-----------------
> 1 file changed, 20 insertions(+), 17 deletions(-)
>
> diff --git a/drivers/firmware/qcom/qcom_scm.c b/drivers/firmware/qcom/qcom_scm.c
> index 9fed03d0a4b7e5709edf2db9a58b5326301008b4..6f70fbb0ddfbf88542ff2b3ed2bc372c2f3ce9eb 100644
> --- a/drivers/firmware/qcom/qcom_scm.c
> +++ b/drivers/firmware/qcom/qcom_scm.c
> @@ -1743,28 +1743,23 @@ module_param(qseecom, charp, 0);
>
> /*
> * We do not yet support re-entrant calls via the qseecom interface. To prevent
> - * any potential issues with this, only allow validated machines for now. Users
> + * any potential issues with this, only allow validated platforms for now. Users
> * still can manually enable or disable it via the qcom_scm.qseecom modparam.
> + *
> + * To disable QSEECOM for a particular machine, add compatible entry and set
^ a
> + * data to (void *)false.
> */
> static const struct of_device_id qcom_scm_qseecom_allowlist[] __maybe_unused = {
> - { .compatible = "dell,xps13-9345" },
> - { .compatible = "lenovo,flex-5g" },
> - { .compatible = "lenovo,thinkpad-t14s" },
> - { .compatible = "lenovo,thinkpad-x13s", },
> - { .compatible = "lenovo,yoga-slim7x" },
> - { .compatible = "microsoft,arcata", },
> - { .compatible = "microsoft,romulus13", },
> - { .compatible = "microsoft,romulus15", },
> - { .compatible = "qcom,sc8180x-primus" },
> - { .compatible = "qcom,x1e80100-crd" },
> - { .compatible = "qcom,x1e80100-qcp" },
> + { .compatible = "qcom,sc8180x", .data = (void *)true },
> + { .compatible = "qcom,sc8280xp", .data = (void *)true },
> + { .compatible = "qcom,x1e80100", .data = (void *)true },
> { }
> };
+ Steev I think you had some unhappy machine
And maybe 8180 Primus?
>
> static bool qcom_scm_qseecom_machine_is_allowed(struct device *scm_dev)
> {
> struct device_node *np;
> - bool match;
> + const struct of_device_id *match;
Reverse-Christmas-tree?
Konrad
next prev parent reply other threads:[~2024-11-04 11:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-03 15:37 [PATCH 0/2] firmware: scm: rework allowlist to be more scalable Dmitry Baryshkov
2024-11-03 15:37 ` [PATCH 1/2] firmware: qcom: scm: add modparam to control QSEECOM enablement Dmitry Baryshkov
2024-11-04 9:38 ` Konrad Dybcio
2024-11-03 15:37 ` [PATCH 2/2] firmware: qcom: scm: rework QSEECOM allowlist Dmitry Baryshkov
2024-11-04 11:23 ` Konrad Dybcio [this message]
2024-11-04 11:34 ` Dmitry Baryshkov
2024-11-04 13:31 ` Konrad Dybcio
2024-11-04 12:15 ` Johan Hovold
2024-11-04 19:43 ` Dmitry Baryshkov
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=02171841-acd3-4f26-987d-1376caf11481@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®