From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
horms@verge.net.au, geert@glider.be,
niklas.soderlund@ragnatech.se,
Jacopo Mondi <jacopo+renesas@jmondi.org>,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org
Subject: Re: [PATCH 1/6] dt-bindings: media: rcar-vin: Describe optional ep properties
Date: Wed, 23 May 2018 22:38:27 +0300 [thread overview]
Message-ID: <1709653.qERUERh18a@avalon> (raw)
In-Reply-To: <20180523162947.GA13661@rob-hp-laptop>
Hi Rob,
On Wednesday, 23 May 2018 19:29:47 EEST Rob Herring wrote:
> On Wed, May 16, 2018 at 06:32:27PM +0200, Jacopo Mondi wrote:
> > Describe the optional endpoint properties for endpoint nodes of port@0
> > and port@1 of the R-Car VIN driver device tree bindings documentation.
> >
> > Signed-off-by: Jacopo Mondi <jacopo+renesas@jmondi.org>
> > ---
> >
> > Documentation/devicetree/bindings/media/rcar_vin.txt | 13 ++++++++++++-
> > 1 file changed, 12 insertions(+), 1 deletion(-)
> >
> > diff --git a/Documentation/devicetree/bindings/media/rcar_vin.txt
> > b/Documentation/devicetree/bindings/media/rcar_vin.txt index
> > a19517e1..c53ce4e 100644
> > --- a/Documentation/devicetree/bindings/media/rcar_vin.txt
> > +++ b/Documentation/devicetree/bindings/media/rcar_vin.txt
> > @@ -53,6 +53,16 @@ from local SoC CSI-2 receivers (port1) depending on
> > SoC.
> >
> > from external SoC pins described in video-interfaces.txt[1].
> > Describing more then one endpoint in port 0 is invalid. Only VIN
> > instances that are connected to external pins should have port 0.
> >
> > +
> > + - Optional properties for endpoint nodes of port@0:
> > + - hsync-active: active state of the HSYNC signal, 0/1 for
> > LOW/HIGH
> > + respectively. Default is active high.
> > + - vsync-active: active state of the VSYNC signal, 0/1 for
> > LOW/HIGH
> > + respectively. Default is active high.
> > +
> > + If both HSYNC and VSYNC polarities are not specified, embedded
> > + synchronization is selected.
>
> No need to copy-n-paste from video-interfaces.txt. Just "see
> video-interfaces.txt" for the description is fine.
I would still explicitly list the properties that apply to this binding. I
agree that there's no need to copy & paste the description of those properties
though.
> > +
> >
> > - port 1 - sub-nodes describing one or more endpoints connected to
> >
> > the VIN from local SoC CSI-2 receivers. The endpoint numbers must
> > use the following schema.
> >
> > @@ -62,6 +72,8 @@ from local SoC CSI-2 receivers (port1) depending on SoC.
> >
> > - Endpoint 2 - sub-node describing the endpoint connected to
> > CSI40
> > - Endpoint 3 - sub-node describing the endpoint connected to
> > CSI41
> >
> > + Endpoint nodes of port@1 do not support any optional endpoint
> > property. +
> >
> > Device node example for Gen2 platforms
> > --------------------------------------
> >
> > @@ -112,7 +124,6 @@ Board setup example for Gen2 platforms (vin1 composite
> > video input)>
> > vin1ep0: endpoint {
> >
> > remote-endpoint = <&adv7180>;
> >
> > - bus-width = <8>;
> >
> > };
> >
> > };
> >
> > };
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2018-05-23 19:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1526488352-898-1-git-send-email-jacopo+renesas@jmondi.org>
2018-05-16 16:32 ` [PATCH 1/6] dt-bindings: media: rcar-vin: Describe optional ep properties Jacopo Mondi
2018-05-16 21:18 ` Niklas Söderlund
2018-05-23 16:29 ` Rob Herring
2018-05-23 19:38 ` Laurent Pinchart [this message]
2018-05-23 19:55 ` Rob Herring
2018-05-16 16:32 ` [PATCH 2/6] dt-bindings: media: rcar-vin: Document data-active Jacopo Mondi
2018-05-16 21:55 ` Niklas Söderlund
2018-05-17 8:25 ` jacopo mondi
2018-05-23 16:37 ` Rob Herring
2018-05-16 16:32 ` [PATCH 5/6] ARM: dts: rcar-gen2: Remove unused VIN properties Jacopo Mondi
2018-05-16 22:13 ` Niklas Söderlund
2018-05-17 9:01 ` jacopo mondi
2018-05-22 8:18 ` Simon Horman
2018-05-23 16:33 ` Rob Herring
2018-05-16 16:32 ` [PATCH 6/6] ARM: dts: rcar-gen2: Add 'data-active' property Jacopo Mondi
2018-05-16 22:15 ` Niklas Söderlund
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=1709653.qERUERh18a@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@glider.be \
--cc=horms@verge.net.au \
--cc=jacopo+renesas@jmondi.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--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).