#thermal-sensor-cells under protocol@15

Laszlo Ersek <[email protected]> Tue, 28 Jul 2026 11:53:41 +0200
Newsgroups org.kernel.vger.arm-scmi,org.kernel.vger.linux-devicetree
Message-ID <[email protected]>
Hello,

as of commit 62cc90241548 (=C2=ABMerge tag
'mm-hotfixes-stable-2026-07-27-14-18' of
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm=C2=BB, 2026-07-27):

"Documentation/devicetree/bindings/firmware/arm,scmi.yaml" specifies
that for protocol@15 -- the SCMI Sensor management protocol --, property
#thermal-sensor-cells is required (with value 1).

I don't understand this requirement. According to now-historical commit
fe7be8b297b2 (=C2=ABdt-bindings: arm: add support for ARM System Control an=
d
Management Interface(SCMI) protocol=C2=BB, 2018-02-28), #thermal-sensor-cel=
ls
specifies the width of SCMI "Sensor ID"s used in sensor references made
by "thermal-sensors".

But a platform's complete set of sensors may not contain a single
thermal sensor (only other sensor types). In that case, the driver file

   drivers/thermal/thermal_of.c

has no business connecting to SCMI (=3D no business referring to Sensor
IDs; consequently, the width of a Sensor ID is irrelevant), while the
driver file

   drivers/hwmon/scmi-hwmon.c

may still justifiedly want to consume protocol@15 (SCMI_PROTOCOL_SENSOR)
from the device tree (i.e., to expose SCMI-provided sensors -- *not*
thermal sensors -- via the hwmon interface, to usespace).

And so describing protocol@15 in the Device Tree, without a
#thermal-sensor-cells property, looks like a valid use case.

Am I wrong?

Thanks!
Laszlo
IMPORTANT NOTICE: The contents of this email and any attachments are confid=
ential and may also be privileged. If you are not the intended recipient, p=
lease notify the sender immediately and do not disclose the contents to any=
 other person, use it for any purpose, or store or copy the information in =
any medium. Thank you.