All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kieran Bingham <kieran@ksquared.org.uk>
To: laurent.pinchart@ideasonboard.com,
	linux-renesas-soc@vger.kernel.org, kieran@ksquared.org.uk
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: [PATCH 2/4] dt-bindings: Update Renesas R-Car FCP DT binding
Date: Fri, 27 May 2016 18:19:23 +0100	[thread overview]
Message-ID: <1464369565-12259-4-git-send-email-kieran@bingham.xyz> (raw)
In-Reply-To: <1464369565-12259-1-git-send-email-kieran@bingham.xyz>

The FCP driver, can also support the FCPF variant for FDP1 compatible
processing.

Signed-off-by: Kieran Bingham <kieran@bingham.xyz>
---
 Documentation/devicetree/bindings/media/renesas,fcp.txt | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

Cc: devicetree@vger.kernel.org

diff --git a/Documentation/devicetree/bindings/media/renesas,fcp.txt b/Documentation/devicetree/bindings/media/renesas,fcp.txt
index 6a12960609d8..1c0718b501ef 100644
--- a/Documentation/devicetree/bindings/media/renesas,fcp.txt
+++ b/Documentation/devicetree/bindings/media/renesas,fcp.txt
@@ -7,11 +7,12 @@ 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'
 
    When compatible with the generic version, nodes must list the
-- 
2.5.0

WARNING: multiple messages have this Message-ID (diff)
From: Kieran Bingham <kieran@bingham.xyz>
To: laurent.pinchart@ideasonboard.com,
	linux-renesas-soc@vger.kernel.org, kieran@bingham.xyz
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: [PATCH 2/4] dt-bindings: Update Renesas R-Car FCP DT binding
Date: Fri, 27 May 2016 18:19:23 +0100	[thread overview]
Message-ID: <1464369565-12259-4-git-send-email-kieran@bingham.xyz> (raw)
In-Reply-To: <1464369565-12259-1-git-send-email-kieran@bingham.xyz>

The FCP driver, can also support the FCPF variant for FDP1 compatible
processing.

Signed-off-by: Kieran Bingham <kieran@bingham.xyz>
---
 Documentation/devicetree/bindings/media/renesas,fcp.txt | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

Cc: devicetree@vger.kernel.org

diff --git a/Documentation/devicetree/bindings/media/renesas,fcp.txt b/Documentation/devicetree/bindings/media/renesas,fcp.txt
index 6a12960609d8..1c0718b501ef 100644
--- a/Documentation/devicetree/bindings/media/renesas,fcp.txt
+++ b/Documentation/devicetree/bindings/media/renesas,fcp.txt
@@ -7,11 +7,12 @@ 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'
 
    When compatible with the generic version, nodes must list the
-- 
2.5.0

  parent reply	other threads:[~2016-05-27 17:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-27 17:19 [PATCH 0/4] RCar r8a7795 FCPF support Kieran Bingham
2016-05-27 17:19 ` Kieran Bingham
2016-05-27 17:19 ` [PATCH 1/4] fcp: Extend FCP compatible list to support the FDP Kieran Bingham
2016-05-27 17:19   ` Kieran Bingham
2016-05-27 17:21   ` Kieran Bingham
2016-05-27 17:21     ` Kieran Bingham
2016-05-27 17:19 ` [PATCH 1/4] v4l: " Kieran Bingham
2016-05-27 17:19   ` Kieran Bingham
2016-05-27 17:19   ` Kieran Bingham
2016-05-27 17:19 ` Kieran Bingham [this message]
2016-05-27 17:19   ` [PATCH 2/4] dt-bindings: Update Renesas R-Car FCP DT binding Kieran Bingham
2016-05-28 19:06   ` Geert Uytterhoeven
2016-05-28 19:06     ` Geert Uytterhoeven
2016-05-30 10:04     ` Kieran Bingham
2016-05-30 10:04       ` Kieran Bingham
2016-05-27 17:19 ` [PATCH 3/4] dt-bindings: Document Renesas R-Car FCP power-domains usage Kieran Bingham
2016-05-27 17:19   ` Kieran Bingham
2016-05-28 19:03   ` Geert Uytterhoeven
2016-05-28 19:03     ` Geert Uytterhoeven
2016-05-30 10:09     ` Kieran Bingham
2016-05-30 10:09       ` Kieran Bingham
2016-05-27 17:19 ` [PATCH 4/4] arm64: dts: r8a7795: add FCPF device nodes Kieran Bingham
2016-05-27 17:19   ` Kieran Bingham
2016-05-31  9:10 ` [PATCH 0/4] RCar r8a7795 FCPF support Geert Uytterhoeven
2016-05-31  9:10   ` Geert Uytterhoeven

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=1464369565-12259-4-git-send-email-kieran@bingham.xyz \
    --to=kieran@ksquared.org.uk \
    --cc=devicetree@vger.kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-renesas-soc@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.