From: Satya Durga Srinivasu Prabhala <satya.prabhala@oss.qualcomm.com>
To: Will Deacon <will@kernel.org>
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: Wed, 14 Jan 2026 08:58:01 -0800 [thread overview]
Message-ID: <6e674553-d0e5-449a-a49f-84f5d32cec94@oss.qualcomm.com> (raw)
In-Reply-To: <aWYk_qGvA9Kn0xGe@willie-the-truck>
Hello Will,
On 1/13/2026 2:57 AM, Will Deacon 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.
> Isn't the fundamental issue here that you have multiple callers of
> soc_device_register() and your userspace is only looking at soc0?
Yes, that is right. The issue is we have several products which already
uses the soc0 interface as vendor interface [1] existed even before the
SMCCC SCM ID [2]. Also, per SMCCC specification, SOC ID is an optional
feature. So, vendor specific implementation can take precedence over
standard implementation or a way to disable SMCCC SOC ID could help.
Best,
Satya
>
> Will
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/soc/qcom/socinfo.c?id=efb448d0a3fca01bb987dd70963da6185b81751e
[2]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/firmware/smccc/soc_id.c?id=821b67fa46390baea0ac5139a60eaa48805261b2
next prev parent reply other threads:[~2026-01-14 16:58 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 6:24 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 [this message]
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
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=6e674553-d0e5-449a-a49f-84f5d32cec94@oss.qualcomm.com \
--to=satya.prabhala@oss.qualcomm.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=sudeep.holla@arm.com \
--cc=trilok.soni@oss.qualcomm.com \
--cc=will@kernel.org \
/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
all inboxes | Powered by JetHome®