Message ID | 20241116-add_asus_qcom_scm-v1-1-5aa2b0fb52bd@hotmail.com |
---|---|
State | New |
Headers | show |
Series | firmware: qcom: scm: Allow QSEECOM on the asus vivobook s15 | expand |
I fear this may have slipped through the cracks as it has not yet gotten a response. or does it have to do with [1]? [1]: https://lore.kernel.org/all/20241103-rework-qseecom-v1-0-1d75d4eedc1e@linaro.org/ kind regards, Maud
On 10.12.2024 8:13 PM, Maud Spierings wrote: > I fear this may have slipped through the cracks as it has not yet gotten a response. > > or does it have to do with [1]? > > [1]: https://lore.kernel.org/all/20241103-rework-qseecom-v1-0-1d75d4eedc1e@linaro.org/ I'm not sure, but I'd much prefer for that one to land instead of having this list grow Konrad
On Fri, Dec 13, 2024 at 02:02:12PM +0100, Konrad Dybcio wrote: > On 10.12.2024 8:13 PM, Maud Spierings wrote: > > I fear this may have slipped through the cracks as it has not yet gotten a response. > > > > or does it have to do with [1]? > > > > [1]: https://lore.kernel.org/all/20241103-rework-qseecom-v1-0-1d75d4eedc1e@linaro.org/ > > I'm not sure, but I'd much prefer for that one to land instead of > having this list grow It's on my todo list, but fist I need to sort out RO efivars support via QSEECOM. I hope to have time for that during or after the weekend.
diff --git a/drivers/firmware/qcom/qcom_scm.c b/drivers/firmware/qcom/qcom_scm.c index 72bf87ddcd969834609cda2aa915b67505e93943..0bdfe64a0ff009c38720692fe60d9f13342181a9 100644 --- a/drivers/firmware/qcom/qcom_scm.c +++ b/drivers/firmware/qcom/qcom_scm.c @@ -1768,6 +1768,7 @@ EXPORT_SYMBOL_GPL(qcom_scm_qseecom_app_send); + any potential issues with this, only allow validated machines for now. */ static const struct of_device_id qcom_scm_qseecom_allowlist[] __maybe_unused = { + { .compatible = "asus,vivobook-s15" }, { .compatible = "dell,xps13-9345" }, { .compatible = "lenovo,flex-5g" }, { .compatible = "lenovo,thinkpad-t14s" },