From: Kieran Bingham <kieran@ksquared.org.uk>
To: Rob Herring <robh@kernel.org>
Cc: Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
"open list:MEDIA DRIVERS FOR RENESAS - FDP1"
<linux-media@vger.kernel.org>,
"open list:MEDIA DRIVERS FOR RENESAS - FDP1"
<linux-renesas-soc@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] dt-bindings: Add Renesas R-Car FDP1 bindings
Date: Mon, 13 Jun 2016 12:31:53 +0100 [thread overview]
Message-ID: <575E99A9.2050806@bingham.xyz> (raw)
In-Reply-To: <20160610174057.GA21480@rob-hp-laptop>
On 10/06/16 18:40, Rob Herring wrote:
> On Thu, Jun 09, 2016 at 02:41:34PM +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.
>>
>> Signed-off-by: Kieran Bingham <kieran@bingham.xyz>
>> ---
>> .../devicetree/bindings/media/renesas,fdp1.txt | 34 ++++++++++++++++++++++
>> 1 file changed, 34 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/media/renesas,fdp1.txt
>>
>> diff --git a/Documentation/devicetree/bindings/media/renesas,fdp1.txt b/Documentation/devicetree/bindings/media/renesas,fdp1.txt
>> new file mode 100644
>> index 000000000000..e2da2aec5e9f
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/media/renesas,fdp1.txt
>> @@ -0,0 +1,34 @@
>> +Renesas R-Car Fine Display Processor (FDP1)
>> +-----------------------------------------------
>> +
>> +The FDP1 is a de-interlacing module which converts interlaced video to
>> +progressive video. It is capable of performing pixel format conversion between
>> +YCbCr/YUV formats and RGB formats. Only YCbCr/YUV formats are supported as
>> +an input to the module.
>> +
>> + - compatible: Must be one or more of the following
>> +
>> + - "renesas,r8a7795-fdp1" for R8A7795 (R-Car H3)
>> + - "renesas,r8a7796-fdp1" for R8A7796 (R-Car M3-W)
>> + - "renesas,fdp1" for generic compatible
>> +
>> + When compatible with the generic version, nodes must list the
>> + SoC-specific version corresponding to the platform first, followed by the
>> + family-specific and/or generic versions.
>> +
>> + - reg: the register base and size for the device registers
>> + - clocks: Reference to the functional clock
>> + - renesas,fcp: Reference to the FCPF connected to the FDP1
>> +
>> +
>> +Device node example
>> +-------------------
>> +
>> + fdp1ch1: fdp1@fe940000 {
>> + compatible = "renesas,r8a7795-fdp1", "renesas,fdp1";
>> + reg = <0 0xfe940000 0 0x2400>;
>> + interrupts = <GIC_SPI 262 IRQ_TYPE_LEVEL_HIGH>;
>> + clocks = <&cpg CPG_MOD 119>;
>> + power-domains = <&sysc R8A7795_PD_A3VP>;
>
> Not documented.
I'll mirror whatever the consensus is on this topic from the other patch
here.
>
>> + renesas,fcp = <&fcpf0>;
>> + };
>> \ No newline at end of file
>
> Fix this.
Ok
>> --
>> 2.7.4
>>
--
Regards
Kieran Bingham
prev parent reply other threads:[~2016-06-13 11:31 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
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 [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=575E99A9.2050806@bingham.xyz \
--to=kieran@ksquared.org.uk \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.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@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;
as well as URLs for NNTP newsgroup(s).