[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <mty6ycfsugaheljicomeucsak7ziakftf22cnikinla7hvthax@f6yu4pmrpuvp>
Date: Sat, 17 Jan 2026 15:51:40 -0600
From: Bjorn Andersson <andersson@...nel.org>
To: Satya Durga Srinivasu Prabhala <satya.prabhala@....qualcomm.com>
Cc: Sudeep Holla <sudeep.holla@....com>,
Mark Rutland <mark.rutland@....com>, Lorenzo Pieralisi <lpieralisi@...nel.org>,
linux-arm-msm@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, trilok.soni@....qualcomm.com
Subject: Re: [PATCH] firmware: smccc: default ARM_SMCCC_SOC_ID to disabled
On Fri, Jan 16, 2026 at 12:53:18PM -0800, Satya Durga Srinivasu Prabhala wrote:
> Hello Sudeep,
>
> Thanks for the discussion & feedback.
>
> Wanted to check on below possibilities to disable the SMCCC SOC ID at the
> vendor end, can you help comment?
> 1. Introduce cmdline option
> We are trying to pursue that in Android Kernel -
> https://android-review.googlesource.com/c/kernel/common/+/3912874
> 2. Mark SMCCC SMC ID driver as tristate & module as suggested by Dmitry
What happens when I boot a system with module autoloading?
What is the expected behavior of userspace when it faces two soc nodes?
Regards,
Bjorn
Powered by blists - more mailing lists