On Tue, Dec 16, 2014 at 5:41 PM, Tomeu Vizoso <[email protected]> wrote: > This block gathers statistics about various counters and can be configured to > fire interrupts when thresholds are crossed. > > Signed-off-by: Tomeu Vizoso <[email protected]> > > --- > > v2: * Add operating-points property > --- > .../devicetree/bindings/arm/tegra/actmon.txt | 38 > ++++++++++++++++++++++ > 1 file changed, 38 insertions(+) > create mode 100644 Documentation/devicetree/bindings/arm/tegra/actmon.txt > > diff --git a/Documentation/devicetree/bindings/arm/tegra/actmon.txt > b/Documentation/devicetree/bindings/arm/tegra/actmon.txt > new file mode 100644 > index 0000000..b4069df > --- /dev/null > +++ b/Documentation/devicetree/bindings/arm/tegra/actmon.txt > @@ -0,0 +1,38 @@ > +Tegra124 Activity Monitor driver
Device Tree describes hardware and is supposed to be driver-independant, so that "driver" qualifier sounds weird to me - maybe remove it? > + > +Required properties: > + > +- compatible: should be "nvidia,tegra124-actmon" > +- reg: offset and length of the register set for the device > +- interrupts: standard interrupt property > +- clocks: Must contain a phandle and clock specifier pair for each entry in > clock-names. See ../clock/clock-bindings.txt for details. Mmm, shouldn't this line be wrapper at character 80? Same throughout this file. Also from this file the correct patch to clock-bindings.txt is ../../clock/clock-bindings.txt (same for reset.txt later). Otherwise, Reviewed-by: Alexandre Courbot <[email protected]> -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
