public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Neil Armstrong <neil.armstrong@linaro.org>
Cc: Satya Durga Srinivasu Prabhala <satya.prabhala@oss.qualcomm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Lorenzo Pieralisi <lpieralisi@kernel.org>,
	linux-arm-msm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, trilok.soni@oss.qualcomm.com
Subject: Re: [PATCH] firmware: smccc: default ARM_SMCCC_SOC_ID to disabled
Date: Wed, 14 Jan 2026 21:06:06 +0000	[thread overview]
Message-ID: <aWgFPuyVRNLPH3J0@bogus> (raw)
In-Reply-To: <d153103d-4b9a-4380-b5cf-1f07dcbcedb8@linaro.org>

On Wed, Jan 14, 2026 at 06:12:29PM +0100, Neil Armstrong wrote:
> On 1/13/26 07:24, 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.
> > 
> > Flip the default of CONFIG_ARM_SMCCC_SOC_ID from y to n. Platforms that
> > prefer SMCCC over a vendor driver can explicitly enable it.
> > 
> > This avoids unexpected format changes and keeps the generic SoC sysfs
> > stable on systems that rely on vendor-specific identification.
> > 
> > [1]
> > Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/soc/qcom/socinfo.c
> > 
> > Signed-off-by: Satya Durga Srinivasu Prabhala <satya.prabhala@oss.qualcomm.com>
> > ---
> >   drivers/firmware/smccc/Kconfig | 5 ++++-
> >   1 file changed, 4 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/firmware/smccc/Kconfig b/drivers/firmware/smccc/Kconfig
> > index 15e7466179a6..f830d11ebdca 100644
> > --- a/drivers/firmware/smccc/Kconfig
> > +++ b/drivers/firmware/smccc/Kconfig
> > @@ -18,8 +18,11 @@ config HAVE_ARM_SMCCC_DISCOVERY
> >   config ARM_SMCCC_SOC_ID
> >   	bool "SoC bus device for the ARM SMCCC SOC_ID"
> >   	depends on HAVE_ARM_SMCCC_DISCOVERY
> > -	default y
> > +	default n
> >   	select SOC_BUS
> >   	help
> >   	  Include support for the SoC bus on the ARM SMCCC firmware based
> >   	  platforms providing some sysfs information about the SoC variant.
> > +	  Note: Several vendor platforms provide their own SoC information
> > +	  drivers under drivers/soc/*. To avoid conflicting sysfs attribute
> > +	  formats in /sys/devices/socX/*, this driver defaults to disabled.
> > 
> > ---
> > base-commit: b71e635feefc852405b14620a7fc58c4c80c0f73
> > change-id: 20260112-disable_smccc_soc_id-ed09ef4d777f
> > 
> > Best regards,
> 
> Disabling it by default impacts other platforms, the arm64 kernel is designed
> to be generic and run on any platform with defconfig and from the same build,
> please don't forget that.
> 
> If you want to ship an arm64 kernel tailored for Qualcomm platforms, you're
> allowed, and you're also allowed to disable ARM_SMCCC_SOC_ID.
> 

Exactly!

> The soc sysfs interface is designed to support multiple source of information,
> from vendor (like qcom socinfo) and smccc ID. And this is well documented,
> and pretty obvious...
> 

Indeed, otherwise soc_device_register() would have failed for more than one
calls to it if that was the design/intention.

-- 
Regards,
Sudeep


  reply	other threads:[~2026-01-14 21:06 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-13  6:24 [PATCH] firmware: smccc: default ARM_SMCCC_SOC_ID to disabled Satya Durga Srinivasu Prabhala
2026-01-13  8:04 ` Mukesh Ojha
2026-01-14 21:07   ` Sudeep Holla
2026-01-13 10:57 ` Will Deacon
2026-01-14 16:58   ` Satya Durga Srinivasu Prabhala
2026-01-14 21:13     ` Sudeep Holla
2026-01-13 11:25 ` Dmitry Baryshkov
2026-01-14 18:04   ` Satya Durga Srinivasu Prabhala
2026-01-14 19:37     ` Dmitry Baryshkov
2026-01-14 21:03       ` Sudeep Holla
2026-01-15 20:14       ` Satya Durga Srinivasu Prabhala
2026-01-15 20:40         ` Dmitry Baryshkov
2026-01-13 12:29 ` Sudeep Holla
2026-01-14 16:50   ` Satya Durga Srinivasu Prabhala
2026-01-14 21:01     ` Sudeep Holla
2026-01-15 18:42       ` Satya Durga Srinivasu Prabhala
2026-01-15 20:18         ` Dmitry Baryshkov
2026-01-15 23:51           ` Satya Durga Srinivasu Prabhala
2026-01-16  0:01           ` Bjorn Andersson
2026-01-16 10:39         ` Sudeep Holla
2026-01-16 20:53           ` Satya Durga Srinivasu Prabhala
2026-01-16 23:53             ` Trilok Soni
2026-01-17 21:43               ` Bjorn Andersson
2026-01-18 14:31               ` Sudeep Holla
2026-01-18 21:16                 ` Bjorn Andersson
2026-01-19 14:53                   ` Sudeep Holla
2026-01-19 16:44                     ` Dmitry Baryshkov
2026-01-19 16:56                       ` Sudeep Holla
2026-01-19 17:20                         ` Dmitry Baryshkov
2026-01-19 17:25                           ` Bjorn Andersson
2026-01-19 19:46                             ` Dmitry Baryshkov
2026-01-19 20:25                               ` Bjorn Andersson
2026-01-19 17:21                     ` Bjorn Andersson
2026-01-20 17:47                       ` Sudeep Holla
2026-01-17 21:51             ` Bjorn Andersson
2026-01-14 17:12 ` Neil Armstrong
2026-01-14 21:06   ` Sudeep Holla [this message]
2026-01-15 20:24   ` Satya Durga Srinivasu Prabhala

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aWgFPuyVRNLPH3J0@bogus \
    --to=sudeep.holla@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=neil.armstrong@linaro.org \
    --cc=satya.prabhala@oss.qualcomm.com \
    --cc=trilok.soni@oss.qualcomm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox