Hi Rob, On Wednesday 27 Apr 2016 21:54:29 Rob Herring wrote: > On Tue, Apr 26, 2016 at 12:36:26AM +0300, Laurent Pinchart wrote: > > 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. > > > > Signed-off-by: Laurent Pinchart > > <laurent.pinchart+renesas@xxxxxxxxxxxxxxxx> > > --- > > > > .../devicetree/bindings/media/renesas,fcp.txt | 31 > > ++++++++++++++++++++++ 1 file changed, 31 insertions(+) > > create mode 100644 > > Documentation/devicetree/bindings/media/renesas,fcp.txt > > > > Cc: devicetree@xxxxxxxxxxxxxxx > > > > 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" ? -- Regards, Laurent Pinchart
