On Wed, Sep 13, 2017 at 12:36 AM, Florian Eckert <fe@xxxxxxxxxx> wrote: > Hello Rob > >>> > --- /dev/null >>> > +++ b/Documentation/devicetree/bindings/hwmon/ltq-cputemp.txt >>> > @@ -0,0 +1,10 @@ >>> > +Lantiq cpu temperatur sensor >> >> >> s/temperatur/temperature/ > > > Will update this in a follow up page based on the old one. So no v4? > >> >>> > + >>> > +Requires node properties: >>> > +- compatible value : >>> > + "lantiq,cputemp" >> >> >> Kind of non-specific. How is this device even accessed without any other >> property? > > > It does not need any further properties. If this is set in the device tree > then the driver is loaded. DT is not the only way to instantiate drivers. What I meant is how do you access the hardware? That should be evident from the binding and it is not. Looking at the driver, you have some memory mapped system control registers which get ioremapped in arch/mips/lantiq/xway/sysctrl.c and accesses thru some platform specific macros. That is not the ideal way to do things as we use syscon and regmap for such things. But that's all mostly kernel details not so relevant to the DT binding. For DT, I'd expect this is a child node of the sysctrl block with a reg property value of <0x40 4> (along with any other child devices). You could also not even put this in DT and the system controller can have it's own driver that instantiates the child device for this driver. Rob -- 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
