From: Sudeep Holla <sudeep.holla@arm.com>
To: Satya Durga Srinivasu Prabhala <satya.prabhala@oss.qualcomm.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
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: Tue, 13 Jan 2026 12:29:07 +0000 [thread overview]
Message-ID: <aWY6kx8Bwa_2azIl@bogus> (raw)
In-Reply-To: <20260112-disable_smccc_soc_id-v1-1-a5bee24befb4@oss.qualcomm.com>
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. 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. 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. Given these
advantages, why would this approach not be the better long-term solution?
--
Regards,
Sudeep
next prev parent reply other threads:[~2026-01-13 12:29 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 [this message]
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
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=aWY6kx8Bwa_2azIl@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=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