From: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
To: daniel.lezcano@oss.qualcomm.com, robh@kernel.org, krzk+dt@kernel.org
Cc: Manaf Meethalavalappu Pallikunhi
<manaf.pallikunhi@oss.qualcomm.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@kernel.org>,
Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>,
Conor Dooley <conor+dt@kernel.org>,
linux-pm@vger.kernel.org (open list:THERMAL),
devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND
FLATTENED DEVICE TREE BINDINGS),
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH] dt-bindings: thermal: Drop thermal zone node name length limit
Date: Mon, 26 Oct 2026 10:49:56 +0100 [thread overview]
Message-ID: <20261026094956.2323036-1-daniel.lezcano@oss.qualcomm.com> (raw)
Device Tree bindings describe hardware and must remain OS-agnostic.
The thermal zone node name length limit is derived from Linux's
THERMAL_NAME_LENGTH macro, which is an implementation detail rather
than a hardware requirement.
Remove the length restriction and its accompanying comment while
preserving the thermal zone naming convention. Any OS-specific limits
should be handled by the implementation rather than encoded in the
Device Tree ABI.
Signed-off-by: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
Cc: Manaf Meethalavalappu Pallikunhi <manaf.pallikunhi@oss.qualcomm.com>
---
Documentation/devicetree/bindings/thermal/thermal-zones.yaml | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/Documentation/devicetree/bindings/thermal/thermal-zones.yaml b/Documentation/devicetree/bindings/thermal/thermal-zones.yaml
index 999ad40a20d5..6091e886829d 100644
--- a/Documentation/devicetree/bindings/thermal/thermal-zones.yaml
+++ b/Documentation/devicetree/bindings/thermal/thermal-zones.yaml
@@ -49,10 +49,7 @@ properties:
to take when the temperature crosses those thresholds.
patternProperties:
- # Node name is limited in size due to Linux kernel requirements - 19
- # characters in total (see THERMAL_NAME_LENGTH, including terminating NUL
- # byte):
- "^[a-zA-Z][a-zA-Z0-9\\-]{1,10}-thermal$":
+ "^[a-zA-Z][a-zA-Z0-9\\-]*-thermal$":
type: object
description:
Each thermal zone node contains information about how frequently it
--
2.43.0
reply other threads:[~2026-10-26 9:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261026094956.2323036-1-daniel.lezcano@oss.qualcomm.com \
--to=daniel.lezcano@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=manaf.pallikunhi@oss.qualcomm.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=rui.zhang@intel.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
all inboxes | Powered by JetHome®