On Tue, Sep 12, 2017 at 11:20:08AM -0500, Rob Herring wrote:
> On Fri, Sep 01, 2017 at 07:26:22AM -0700, Guenter Roeck wrote:
> > On Fri, Sep 01, 2017 at 08:58:18AM +0200, Florian Eckert wrote:
> > > Document the devicetree bindings for the ltq-cputemp
> > >
> > > Signed-off-by: Florian Eckert <fe@xxxxxxxxxx>
> >
> > I see nothing special with the bindings, and they are in line with other lantiq
> > bindings, so I am taking the risk of accepting this patch (and the matching
> > driver) without waiting for explicit approval from Rob. Rob, scream at me if
> > that is not ok.
>
> Perhaps the existing one was not well reviewed.
>
Bummer. Should teach me to never accept DT patches without your review.
I owe you a beer or two.
Guenter
> >
> > Thanks,
> > Guenter
> >
> > > ---
> > > Documentation/devicetree/bindings/hwmon/ltq-cputemp.txt | 10 ++++++++++
> > > 1 file changed, 10 insertions(+)
> > > create mode 100644 Documentation/devicetree/bindings/hwmon/ltq-cputemp.txt
> > >
> > > diff --git a/Documentation/devicetree/bindings/hwmon/ltq-cputemp.txt b/Documentation/devicetree/bindings/hwmon/ltq-cputemp.txt
> > > new file mode 100644
> > > index 000000000000..33fd00a987c7
> > > --- /dev/null
> > > +++ b/Documentation/devicetree/bindings/hwmon/ltq-cputemp.txt
> > > @@ -0,0 +1,10 @@
> > > +Lantiq cpu temperatur sensor
>
> s/temperatur/temperature/
>
> > > +
> > > +Requires node properties:
> > > +- compatible value :
> > > + "lantiq,cputemp"
>
> Kind of non-specific. How is this device even accessed without any other
> property?
>
> > > +
> > > +Example:
> > > + cputemp@0 {
>
> unit-address without reg property is not valid.
>
> > > + compatible = "lantiq,cputemp";
> > > + };
> > > --
> > > 2.11.0
> > >
> > > --
> > > To unsubscribe from this list: send the line "unsubscribe linux-hwmon" in
> > > the body of a message to majordomo@xxxxxxxxxxxxxxx
> > > More majordomo info at http://vger.kernel.org/majordomo-info.html
--
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
