devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: devicetree@vger.kernel.org, robh+dt@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>,
	mchehab@kernel.org, hans.verkuil@cisco.com,
	linux-arm-kernel@lists.infradead.org,
	linux-media@vger.kernel.org
Subject: Re: [PATCH v4 6/6] dt-bindings: media: rcar-vin: Clarify optional props
Date: Tue, 12 Jun 2018 19:15:06 +0300	[thread overview]
Message-ID: <2802458.0ZPzlQSr2q@avalon> (raw)
In-Reply-To: <20180612154553.kgqnqkwv3y6srivg@kekkonen.localdomain>

Hello,

On Tuesday, 12 June 2018 18:45:53 EEST Sakari Ailus wrote:
> On Tue, Jun 12, 2018 at 04:26:06PM +0200, Jacopo Mondi wrote:
> > Add a note to the R-Car VIN interface bindings to clarify that all
> > properties listed as generic properties in video-interfaces.txt can
> > be included in port@0 endpoint, but if not explicitly listed in the
> > interface bindings documentation, they do not modify it behaviour.
> > 
> > Signed-off-by: Jacopo Mondi <jacopo+renesas@jmondi.org>
> > ---
> > 
> >  Documentation/devicetree/bindings/media/rcar_vin.txt | 6 ++++++
> >  1 file changed, 6 insertions(+)
> > 
> > diff --git a/Documentation/devicetree/bindings/media/rcar_vin.txt
> > b/Documentation/devicetree/bindings/media/rcar_vin.txt index
> > 8130849..03544c7 100644
> > --- a/Documentation/devicetree/bindings/media/rcar_vin.txt
> > +++ b/Documentation/devicetree/bindings/media/rcar_vin.txt
> > @@ -55,6 +55,12 @@ from local SoC CSI-2 receivers (port1) depending on
> > SoC.
> > 
> >        instances that are connected to external pins should have port 0.
> > 
> >        - Optional properties for endpoint nodes of port@0:
> > +
> > +        All properties described in [1] and which apply to the selected
> > +        media bus type could be optionally listed here to better describe
> > +        the current hardware configuration, but only the following ones
> > do
> > +        actually modify the VIN interface behaviour:
> > +
> 
> I don't think this should be needed. You should only have properties that
> describe the hardware configuration in a given system.

I agree. Please list explicitly all properties that are applicable for this 
device, and don't tell which one(s) are used by the driver.

> >          - hsync-active: see [1] for description. Default is active high.
> >          - vsync-active: see [1] for description. Default is active high.
> >          - data-enable-active: polarity of CLKENB signal, see [1] for

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2018-06-12 16:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-12 14:26 [PATCH v4 0/6] media: rcar-vin: Brush endpoint properties Jacopo Mondi
2018-06-12 14:26 ` [PATCH v4 1/6] dt-bindings: media: rcar-vin: Describe optional ep properties Jacopo Mondi
2018-06-12 14:26 ` [PATCH v4 2/6] dt-bindings: media: Document data-enable-active property Jacopo Mondi
2018-06-12 14:26 ` [PATCH v4 3/6] media: v4l2-fwnode: parse 'data-enable-active' prop Jacopo Mondi
2018-06-12 14:26 ` [PATCH v4 4/6] dt-bindings: media: rcar-vin: Add 'data-enable-active' Jacopo Mondi
2018-06-12 14:26 ` [PATCH v4 5/6] media: rcar-vin: Handle data-enable polarity Jacopo Mondi
2018-06-12 14:26 ` [PATCH v4 6/6] dt-bindings: media: rcar-vin: Clarify optional props Jacopo Mondi
2018-06-12 15:45   ` Sakari Ailus
2018-06-12 16:15     ` Laurent Pinchart [this message]
2018-06-13  8:54     ` jacopo mondi
2018-06-27  5:24       ` Niklas Söderlund
2018-07-02  7:19         ` Laurent Pinchart
2018-07-03 19:52           ` jacopo mondi
2018-07-06 15:54             ` 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=2802458.0ZPzlQSr2q@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@glider.be \
    --cc=hans.verkuil@cisco.com \
    --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=mchehab@kernel.org \
    --cc=niklas.soderlund@ragnatech.se \
    --cc=robh+dt@kernel.org \
    --cc=sakari.ailus@linux.intel.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).