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 1/2] firmware: qcom: scm: add modparam to control QSEECOM enablement
Date: Mon, 4 Nov 2024 10:38:51 +0100 [thread overview]
Message-ID: <f6205012-5f5b-4613-bcb5-dea3f904b5a0@oss.qualcomm.com> (raw)
In-Reply-To: <20241103-rework-qseecom-v1-1-1d75d4eedc1e@linaro.org>
On 3.11.2024 4:37 PM, Dmitry Baryshkov wrote:
> In preparation to enabling QSEECOM for the platforms rather than
> individual machines provide a mechanism for the user to override default
> selection. Allow users to use qcom_scm.qseecom modparam. Setting it to
> 'force' will enable QSEECOM even if it disabled or not handled by the
> allowlist. Setting it to 'off' will forcebly disable the QSEECOM
> interface, allowing incompatible machines to function. All other values
> mean 'auto', trusting the allowlist in the module.
>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
[...]
>
> -static bool qcom_scm_qseecom_machine_is_allowed(void)
> +static bool qcom_scm_qseecom_machine_is_allowed(struct device *scm_dev)
> {
> struct device_node *np;
> bool match;
>
> + if (!strcmp(qseecom, "off")) {
> + dev_info(scm_dev, "qseecom: disabled by modparam\n");
> + return false;
> + } else if (!strcmp(qseecom, "force")) {
> + dev_info(scm_dev, "qseecom: forcebly enabled\n");
forcibly
may also be useful to say "by modparam" here as well
Konrad
next prev parent reply other threads:[~2024-11-04 9:38 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 [this message]
2024-11-03 15:37 ` [PATCH 2/2] firmware: qcom: scm: rework QSEECOM allowlist Dmitry Baryshkov
2024-11-04 11:23 ` Konrad Dybcio
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=f6205012-5f5b-4613-bcb5-dea3f904b5a0@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®