mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: robh@kernel.org, krzk+dt@kernel.org,
	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>,
	"open list:THERMAL" <linux-pm@vger.kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: thermal: Drop thermal zone node name length limit
Date: Wed, 28 Oct 2026 17:07:46 +0100	[thread overview]
Message-ID: <f054a608-730f-4415-87ef-510523a50ac5@oss.qualcomm.com> (raw)
In-Reply-To: <20261028-worthy-prudent-cuckoo-d5ed97@quoll>

On 10/28/26 14:00, Krzysztof Kozlowski wrote:
> On Mon, Oct 26, 2026 at 10:49:56AM +0100, Daniel Lezcano wrote:
>> Device Tree bindings describe hardware and must remain OS-agnostic.
> 
> DTS describes hardware. Bindings describe the ABI between hardware and
> software, so if SW requires something regarding the DTS, should be
> placed in the binding as well, IMO.
That's odd, if the Linux kernel changes the thermal zone name length to 
something else, then that impacts the bindings, no ?

I don't see a good reason why the node name must be limited by Linux.

  reply	other threads:[~2026-10-28 16:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26  9:49 Daniel Lezcano
2026-10-28 13:00 ` Krzysztof Kozlowski
2026-10-28 16:07   ` Daniel Lezcano [this message]
2026-10-28 18:04     ` Krzysztof Kozlowski

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=f054a608-730f-4415-87ef-510523a50ac5@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=krzk@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®