devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
To: Jacopo Mondi <jacopo+renesas@jmondi.org>
Cc: devicetree@vger.kernel.org, robh+dt@kernel.org,
	linux-renesas-soc@vger.kernel.org, horms@verge.net.au,
	hans.verkuil@cisco.com, laurent.pinchart@ideasonboard.com,
	sakari.ailus@linux.intel.com, geert@glider.be,
	mchehab@kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-media@vger.kernel.org
Subject: Re: [PATCH v5 1/6] dt-bindings: media: rcar-vin: Align Gen2 and Gen3
Date: Thu, 12 Jul 2018 10:14:19 +0200	[thread overview]
Message-ID: <20180712081419.GU5237@bigcity.dyn.berto.se> (raw)
In-Reply-To: <1531145962-1540-2-git-send-email-jacopo+renesas@jmondi.org>

Hi Jacopo,

On 2018-07-09 16:19:16 +0200, Jacopo Mondi wrote:
> Align description of the Gen2 and Gen3 bindings for parallel input.
> This commit prepares for description of optional endpoint properties in ports
> subnodes accepting parallel video connections.
> 
> Signed-off-by: Jacopo Mondi <jacopo+renesas@jmondi.org>

Acked-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>

> ---
>  Documentation/devicetree/bindings/media/rcar_vin.txt | 10 ++++++----
>  1 file changed, 6 insertions(+), 4 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/media/rcar_vin.txt b/Documentation/devicetree/bindings/media/rcar_vin.txt
> index e25ab07..39c4e6a 100644
> --- a/Documentation/devicetree/bindings/media/rcar_vin.txt
> +++ b/Documentation/devicetree/bindings/media/rcar_vin.txt
> @@ -39,9 +39,11 @@ Additionally, an alias named vinX will need to be created to specify
>  which video input device this is.
>  
>  The per-board settings Gen2 platforms:
> - - port sub-node describing a single endpoint connected to the vin
> -   as described in video-interfaces.txt[1]. Only the first one will
> -   be considered as each vin interface has one input port.
> +
> +- port - sub-node describing a single endpoint connected to the VIN
> +  from external SoC pins as described in video-interfaces.txt[1].
> +  Only the first one will be considered as each vin interface has one
> +  input port.
>  
>  The per-board settings Gen3 platforms:
>  
> @@ -52,7 +54,7 @@ from local SoC CSI-2 receivers (port@1) depending on SoC.
>  - renesas,id - ID number of the VIN, VINx in the documentation.
>  - ports
>      - port@0 - sub-node describing a single endpoint connected to the VIN
> -      from external SoC pins described in video-interfaces.txt[1].
> +      from external SoC pins as described in video-interfaces.txt[1].
>        Describing more than one endpoint in port@0 is invalid. Only VIN
>        instances that are connected to external pins should have port@0.
>      - port@1 - sub-nodes describing one or more endpoints connected to
> -- 
> 2.7.4
> 

-- 
Regards,
Niklas Söderlund

  parent reply	other threads:[~2018-07-12  8:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-09 14:19 [PATCH v5 0/6] media: rcar-vin: Brush endpoint properties Jacopo Mondi
2018-07-09 14:19 ` [PATCH v5 1/6] dt-bindings: media: rcar-vin: Align Gen2 and Gen3 Jacopo Mondi
2018-07-11 13:51   ` Rob Herring
2018-07-12  8:14   ` Niklas Söderlund [this message]
2018-07-09 14:19 ` [PATCH v5 2/6] dt-bindings: media: rcar-vin: Describe optional ep properties Jacopo Mondi
2018-07-09 14:19 ` [PATCH v5 3/6] dt-bindings: media: Document data-enable-active property Jacopo Mondi
2018-07-12  8:13   ` Niklas Söderlund
2018-07-09 14:19 ` [PATCH v5 4/6] media: v4l2-fwnode: parse 'data-enable-active' prop Jacopo Mondi
2018-07-09 14:19 ` [PATCH v5 5/6] dt-bindings: media: rcar-vin: Add 'data-enable-active' Jacopo Mondi
2018-07-09 14:19 ` [PATCH v5 6/6] media: rcar-vin: Handle data-enable polarity Jacopo Mondi
2018-07-09 14:19 ` [PATCH v5 7/7] ARM: dts: rcar-gen2: Remove un-supported VIN properties Jacopo Mondi
2018-07-09 14:26   ` jacopo mondi

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=20180712081419.GU5237@bigcity.dyn.berto.se \
    --to=niklas.soderlund@ragnatech.se \
    --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=laurent.pinchart@ideasonboard.com \
    --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=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).