Message-ID: <aWgEDAlglnGrzdR4@bogus>
Date: Wed, 14 Jan 2026 21:01:00 +0000
From: Sudeep Holla <sudeep.holla@....com>
To: Satya Durga Srinivasu Prabhala <satya.prabhala@....qualcomm.com>
Cc: Mark Rutland <mark.rutland@....com>,
	Lorenzo Pieralisi <lpieralisi@...nel.org>,
	Sudeep Holla <sudeep.holla@....com>, 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 Wed, Jan 14, 2026 at 08:50:23AM -0800, Satya Durga Srinivasu Prabhala wrote:
> Hello Sudeep,
> 
> On 1/13/2026 4:29 AM, Sudeep Holla wrote:
> > On Mon, Jan 12, 2026 at 10:24:06PM -0800, Satya Durga Srinivasu Prabhala wrote:
> > > The ARM SMCCC SoC ID driver is currently enabled by default and publishes
> > > SMCCC-provided SoC identification into /sys/bus/soc/devices/socX/*.
> > > 
> > > On platforms where a vendor SoC driver already exposes widely-consumed
> > > attributes (e.g. Qualcomm socinfo [1]), enabling the SMCCC driver changes
> > > the format of /sys/devices/soc0/soc_id (e.g. "jep106:XXYY:ZZZZ" instead
> > > of a vendor logical ID like "519") and breaks existing userspace consumers.
> > > 
> > Instead of relying on a vendor-specific SoC driver, we should consider
> > disabling it and using the OS-agnostic SoC information interface provided by
> > the firmware.
> Would like to add some history here. Vendor interface existed [1] even
> before
> SMCCC SMC ID was introduced [2]. And there are several user space entities
> which
> uses the soc0 interface already.

True, but that's not the main point.

> > The presence of this interface strongly suggests that the
> > firmware is designed to support multiple operating systems or software stacks
> > that already depend on it.
> That is correct. We started seeing the issue with user space when our
> firmware
> started implementing support for SMCCC SOC ID recently for non-Linux based
> product.
> As the firmware remain same across OSes, user space is broken on Linux.

What exactly do you mean by "firmware started implementing support for SMCCC
SOC ID recently for non-Linux based product" ? Does that really mean that
you can change the firmware for Linux based products ? I don't think so and
hence we are in this discussion.

1. Either it exists in which case deal with it by disabling vendor driver
   and/or fixing the userspace.

or

2. It doesn't exist which is not a problem.


> > Aligning the Linux kernel with this
> > firmware-defined, OS-agnostic mechanism would reduce vendor-specific
> > dependencies and improve portability. Any gaps can be addressed by enhancing
> > userspace to correctly parse and consume this information.
> Agree. Updating entire use space would need time and we are looking to see
> if vendor specific interface can be given priority over the standard
> interface.

That statement simply doesn't make sense at all. Your product took all the
effort to implement standards and then you don't want to use it at all.
As per your claims it is not even broken(in terms of data from the sysfs
files), so I don't know what to say here, sorry ?

> >   Given these
> > advantages, why would this approach not be the better long-term solution?
> As mentioned above, existing user space will be broken and fixing existing
> user space is going to take time. As the feature itself is "optional" from SMCCC
> specification, if we can't disable by default, we should at-least have a way
> to disable the feature by other means.
>

The data given to the userspace from the kernel is not broken. The userspace
tool seem to have made a wrong assumption and can't expect the kernel to
magically fix the issue here.

E.g. We didn't disable HMP(a.k.a big little platforms) as the assumptions
made by several userspace tools(e.g. lscpu IIRC) was wrong at the time.

-- 
Regards,
Sudeep

Powered by blists - more mailing lists