From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Herring Subject: Re: [PATCH v2 01/13] dt-bindings: Add Renesas R-Car FCP DT bindings Date: Wed, 27 Apr 2016 21:54:29 -0500 Message-ID: <20160428025429.GA11679@rob-hp-laptop> References: <1461620198-13428-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com> <1461620198-13428-2-git-send-email-laurent.pinchart+renesas@ideasonboard.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1461620198-13428-2-git-send-email-laurent.pinchart+renesas@ideasonboard.com> Sender: linux-renesas-soc-owner@vger.kernel.org To: Laurent Pinchart Cc: linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org List-Id: devicetree@vger.kernel.org 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 > --- > .../devicetree/bindings/media/renesas,fcp.txt | 31 ++++++++++++++++++++++ > 1 file changed, 31 insertions(+) > create mode 100644 Documentation/devicetree/bindings/media/renesas,fcp.txt > > Cc: devicetree@vger.kernel.org > > 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. Rob