[PATCH] firmware: smccc: default ARM_SMCCC_SOC_ID to disabled
Dmitry Baryshkov
dmitry.baryshkov at oss.qualcomm.com
Mon Jan 19 08:44:23 PST 2026
On Mon, Jan 19, 2026 at 02:53:42PM +0000, Sudeep Holla wrote:
> On Sun, Jan 18, 2026 at 03:16:50PM -0600, Bjorn Andersson wrote:
> > On Sun, Jan 18, 2026 at 02:31:23PM +0000, Sudeep Holla wrote:
> >
> > To me, when you decided to add a second caller to soc_device_register()
> > you created a regression in the userspace interface. If nothing else
> > it's a leaky abstraction.
> >
>
> In that case, shouldn't soc_device_register() made to give error when an
> attempt to call it more that one time then ? Also should be change the
> ABI documents to refer it as soc0 and not socX ?
Then the whole SoC bus is an overkill. But I have a strange question
here. Consider the device having the "BT / WiFi SoC" next to the main
SoC. Is that SoC a legit target to export informaiton through sysfs /
soc bus?
--
With best wishes
Dmitry
More information about the linux-arm-kernel
mailing list