* thermal-zones DT node bound by name rather than compatible property
@ 2014-03-06 17:57 Stephen Warren
0 siblings, 0 replies; only message in thread
From: Stephen Warren @ 2014-03-06 17:57 UTC (permalink / raw)
To: Eduardo Valentin
Cc: Wei Ni, Zhang Rui, devicetree@vger.kernel.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Rob Herring, Pawel Moll, Mark Rutland, Ian Campbell, Kumar Gala
Commit 4e5e4705bf69 "thermal: introduce device tree parser" introduced
the text below into Documentation/devicetree/bindings/thermal/thermal.txt:
> * The thermal-zones node
>
> The "thermal-zones" node is a container for all thermal zone nodes. It shall
> contain only sub-nodes describing thermal zones as in the section
> "Thermal zone nodes". The "thermal-zones" node appears under "/".
This implies that software must find the thermal-zones node by node
name. Node names aren't supposed to be significant in DT. Rather,
software is supposed to bind to a node by searching for all nodes with a
particular value in the compatible property. While there are some legacy
counter-examples such as /aliases, /chosen, and /cpus, I don't think we
should propagate any more of these in new bindings.
Can this mistake in the binding definition be rectified, or is it too late?
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2014-03-06 17:57 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-03-06 17:57 thermal-zones DT node bound by name rather than compatible property Stephen Warren
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.