From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Kieran Bingham <kieran@ksquared.org.uk>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: Update Renesas R-Car FCP DT binding
Date: Mon, 13 Jun 2016 15:17:41 +0300 [thread overview]
Message-ID: <2159488.zJIIWenpjG@avalon> (raw)
In-Reply-To: <1465479695-18644-2-git-send-email-kieran@bingham.xyz>
Hi Kieran,
Thank you for the patch.
On Thursday 09 Jun 2016 14:41:32 Kieran Bingham wrote:
> The FCP driver, can also support the FCPF variant for FDP1 compatible
> processing.
With the comma dropped,
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Signed-off-by: Kieran Bingham <kieran@bingham.xyz>
> ---
> Documentation/devicetree/bindings/media/renesas,fcp.txt | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/media/renesas,fcp.txt
> b/Documentation/devicetree/bindings/media/renesas,fcp.txt index
> 6a12960609d8..271dcfdb5a76 100644
> --- a/Documentation/devicetree/bindings/media/renesas,fcp.txt
> +++ b/Documentation/devicetree/bindings/media/renesas,fcp.txt
> @@ -7,12 +7,14 @@ conversion of AXI transactions in order to reduce the
> memory bandwidth.
>
> There are three types of FCP: FCP for Codec (FCPC), FCP for VSP (FCPV) and
> FCP for FDP (FCPF). Their configuration and behaviour depend on the module
> they -are paired with. These DT bindings currently support the FCPV only.
> +are paired with. These DT bindings currently support the FCPV and FCPF.
>
> - compatible: Must be one or more of the following
>
> - "renesas,r8a7795-fcpv" for R8A7795 (R-Car H3) compatible 'FCP for VSP'
> + - "renesas,r8a7795-fcpf" for R8A7795 (R-Car H3) compatible 'FCP for
> FDP' - "renesas,fcpv" for generic compatible 'FCP for VSP'
> + - "renesas,fcpf" for generic compatible 'FCP for FDP'
>
> When compatible with the generic version, nodes must list the
> SoC-specific version corresponding to the platform first, followed by
> the
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2016-06-13 12:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1465479695-18644-1-git-send-email-kieran@bingham.xyz>
2016-06-09 13:41 ` [PATCH 1/3] dt-bindings: Update Renesas R-Car FCP DT binding Kieran Bingham
2016-06-10 17:37 ` Rob Herring
2016-06-13 11:28 ` Kieran Bingham
2016-06-13 12:17 ` Laurent Pinchart [this message]
2016-06-09 13:41 ` [PATCH 2/3] dt-bindings: Document Renesas R-Car FCP power-domains usage Kieran Bingham
2016-06-10 17:39 ` Rob Herring
2016-06-10 19:11 ` Geert Uytterhoeven
2016-06-10 21:33 ` Rob Herring
2016-06-12 8:46 ` Geert Uytterhoeven
2016-06-09 13:41 ` [PATCH 3/3] dt-bindings: Add Renesas R-Car FDP1 bindings Kieran Bingham
2016-06-10 17:40 ` Rob Herring
2016-06-13 11:31 ` Kieran Bingham
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2159488.zJIIWenpjG@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kieran@ksquared.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox