From: Rob Herring <robh@kernel.org>
To: Kieran Bingham <kieran@ksquared.org.uk>
Cc: laurent.pinchart@ideasonboard.com, mark.rutland@arm.com,
linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] dt-bindings: Add Renesas R-Car FDP1 bindings
Date: Thu, 30 Jun 2016 21:51:01 -0500 [thread overview]
Message-ID: <20160701025101.GA3652@rob-hp-laptop> (raw)
In-Reply-To: <1467305430-25660-4-git-send-email-kieran@bingham.xyz>
On Thu, Jun 30, 2016 at 05:50:30PM +0100, Kieran Bingham wrote:
> The FDP1 is a de-interlacing module which converts interlaced video to
> progressive video. It is also capable of performing pixel format conversion
> between YCbCr/YUV formats and RGB formats.
>
> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Signed-off-by: Kieran Bingham <kieran@bingham.xyz>
> ---
> Changes since v1:
> - title fixed
> - Interrupts property documented
> - version specific compatibles removed as we have a hw version register
> - label removed from device node example
> * (fdp1 is not referenced by other nodes)
>
> .../devicetree/bindings/media/renesas,fdp1.txt | 33 ++++++++++++++++++++++
> 1 file changed, 33 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/media/renesas,fdp1.txt
Acked-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2016-07-01 2:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 16:50 [PATCH v2 0/3] dt-bindings: RCar FCP and FDP1 bindings Kieran Bingham
2016-06-30 16:50 ` [PATCH v2 1/3] dt-bindings: Update Renesas R-Car FCP DT binding Kieran Bingham
2016-06-30 16:50 ` [PATCH v2 2/3] dt-bindings: Document Renesas R-Car FCP power-domains usage Kieran Bingham
2016-07-01 2:49 ` Rob Herring
2016-07-17 16:31 ` Laurent Pinchart
2016-06-30 16:50 ` [PATCH v2 3/3] dt-bindings: Add Renesas R-Car FDP1 bindings Kieran Bingham
2016-07-01 2:51 ` Rob Herring [this message]
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=20160701025101.GA3652@rob-hp-laptop \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kieran@ksquared.org.uk \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
/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;
as well as URLs for NNTP newsgroup(s).