On Thu, Apr 28, 2016 at 8:36 AM, Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx> wrote: >> > diff --git a/Documentation/devicetree/bindings/media/renesas,fcp.txt >> > b/Documentation/devicetree/bindings/media/renesas,fcp.txt new file mode >> > 100644 >> > index 000000000000..0c72ca24379f >> > --- /dev/null >> > +++ b/Documentation/devicetree/bindings/media/renesas,fcp.txt >> > @@ -0,0 +1,31 @@ >> > +Renesas R-Car Frame Compression Processor (FCP) >> > +----------------------------------------------- >> > + >> > +The FCP is a companion module of video processing modules in the Renesas >> > R-Car +Gen3 SoCs. It provides data compression and decompression, data >> > caching, and +conversion of AXI transactions in order to reduce the >> > memory bandwidth. + >> > +There are three types of FCP whose configuration and behaviour highly >> > depend +on the module they are paired with. >> >> 3 types?, but I only see one compatible and no relationship with said >> module described. > > The bindings currently support a single type, as that's all the driver > currently supports and I'm not comfortable merging bindings without at least > one test implementation. Should I clarify that with something as "These DT > bindings currently support the "FCP for Video" type only" ? Yes please. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds