Re: [PATCH] firmware: QCOM interfaces should depend on ARCH_QCOM
Konrad Dybcio <[email protected]>
| Newsgroups | org.kernel.vger.linux-wireless,org.infradead.lists.linux-arm-kernel,org.kernel.vger.linux-arm-msm,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On 8/6/26 12:35 PM, Geert Uytterhoeven wrote: > The various Qualcomm firmware interfaces are only present on Qualcomm > systems. Hence add dependencies on ARCH_QCOM, to prevent asking the > user about them when configuring a kernel without Qualcomm SoC support. > Make QCOM_PAS invisible instead, as it is already selected by its users > when needed. > > Signed-off-by: Geert Uytterhoeven <[email protected]> > --- > I wondered whether QCOM_SCM should be made invisible, too, as it seems > to be selected by its users? But apparently commit 5c1a2975d23c51c0 > ("firmware: qcom_scm: Migrate to generic PAS service") in net-next/main > and soc/for-next made it visible on purpose? For some context, that commit was part of a series that introduced a second back-end to the functions that previously only the QCOM_SCM driver provided ("qcom proprietary TZ interface" vs "what TF-A is going to provide"), and the author's intention was to make the former possible to disable Konrad