On Fri, Jan 17, 2014 at 7:58 AM, James Hogan <[email protected]> wrote: > Add device tree binding for ImgTec Consumer Infrared block, specifically > major revision 1 of the hardware. > > Signed-off-by: James Hogan <[email protected]> > Cc: Mauro Carvalho Chehab <[email protected]> > Cc: [email protected] > Cc: Rob Herring <[email protected]> > Cc: Pawel Moll <[email protected]> > Cc: Mark Rutland <[email protected]> > Cc: Ian Campbell <[email protected]> > Cc: Kumar Gala <[email protected]> > Cc: [email protected] > Cc: Rob Landley <[email protected]> > Cc: [email protected] > Cc: Tomasz Figa <[email protected]> > --- > v2: > - Future proof compatible string from "img,ir" to "img,ir1", where the 1 > corresponds to the major revision number of the hardware (Tomasz > Figa). > - Added clock-names property and three specific clock names described in > the manual, only one of which is used by the current driver (Tomasz > Figa). > --- > .../devicetree/bindings/media/img-ir1.txt | 30 > ++++++++++++++++++++++ > 1 file changed, 30 insertions(+) > create mode 100644 Documentation/devicetree/bindings/media/img-ir1.txt > > diff --git a/Documentation/devicetree/bindings/media/img-ir1.txt > b/Documentation/devicetree/bindings/media/img-ir1.txt > new file mode 100644 > index 0000000..ace5fd9 > --- /dev/null > +++ b/Documentation/devicetree/bindings/media/img-ir1.txt > @@ -0,0 +1,30 @@ > +* ImgTec Infrared (IR) decoder version 1 > + > +This binding is for Imagination Technologies' Infrared decoder block, > +specifically major revision 1. > + > +Required properties: > +- compatible: Should be "img,ir1"
Kind of short for a name. I don't have anything much better, but how about img,ir-rev1. > +- reg: Physical base address of the controller and length of > + memory mapped region. > +- interrupts: The interrupt specifier to the cpu. > + > +Optional properties: > +- clocks: List of clock specifiers as described in standard > + clock bindings. > +- clock-names: List of clock names corresponding to the clocks > + specified in the clocks property. > + Accepted clock names are: > + "core": Core clock (defaults to 32.768KHz if omitted). > + "sys": System side (fast) clock. > + "mod": Power modulation clock. You need to define the order of clocks including how they are interpreted with different number of clocks (not relying on the name). Although, if the h/w block really has different number of clock inputs, then it is a different h/w block and should have a different compatible string. Rob -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
