On Wed, 2017-01-04 at 16:57 +0800, Jia Hongtao wrote: > For different types of SoC the sensor id and endianness may vary. > "#thermal-sensor-cells" is used to provide sensor id information. > "little-endian" property is to tell the endianness of TMU. > > Signed-off-by: Jia Hongtao <hongtao.jia@xxxxxxx> > Acked-by: Rob Herring <robh@xxxxxxxxxx> > --- > Documentation/devicetree/bindings/thermal/qoriq-thermal.txt | 7 +++++++ > 1 file changed, 7 insertions(+) > > diff --git a/Documentation/devicetree/bindings/thermal/qoriq-thermal.txt > b/Documentation/devicetree/bindings/thermal/qoriq-thermal.txt > index 66223d5..20ca4ef 100644 > --- a/Documentation/devicetree/bindings/thermal/qoriq-thermal.txt > +++ b/Documentation/devicetree/bindings/thermal/qoriq-thermal.txt > @@ -17,6 +17,12 @@ Required properties: > calibration data, as specified by the SoC reference manual. > The first cell of each pair is the value to be written to TTCFGR, > and the second is the value to be written to TSCFGR. > +- #thermal-sensor-cells : Must be 1. The sensor specifier is the monitoring > + site ID, and represents the "n" in TRITSRn and TRATSRn. I assume the driver will continue to work with existing device trees where this information is absent? If so, ACK for the whole series. -Scott -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
