From: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
Biju Das <biju.das@bp.renesas.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Hans Verkuil <hans.verkuil@cisco.com>,
linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH] media: dt-bindings: rcar_vin: Document RZ/G1 per-board settings
Date: Thu, 24 Oct 2019 20:02:03 +0200 [thread overview]
Message-ID: <20191024180203.GA24998@bigcity.dyn.berto.se> (raw)
In-Reply-To: <20191024131423.16799-1-geert+renesas@glider.be>
Hi Geert,
Thanks for your work.
On 2019-10-24 15:14:23 +0200, Geert Uytterhoeven wrote:
> The R-Car Gen2 per-board settings apply to RZ/G1, too.
>
> Fixes: 1d14a5eaa156b0b3 ("media: dt-bindings: media: rcar_vin: add device tree support for r8a774[35]")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Reviewed-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
> ---
> Documentation/devicetree/bindings/media/renesas,vin.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/media/renesas,vin.txt b/Documentation/devicetree/bindings/media/renesas,vin.txt
> index aa217b0962797712..221fcc416d1ac598 100644
> --- a/Documentation/devicetree/bindings/media/renesas,vin.txt
> +++ b/Documentation/devicetree/bindings/media/renesas,vin.txt
> @@ -43,7 +43,7 @@ on Gen3 and RZ/G2 platforms to a CSI-2 receiver.
> Additionally, an alias named vinX will need to be created to specify
> which video input device this is.
>
> -The per-board settings Gen2 platforms:
> +The per-board settings for Gen2 and RZ/G1 platforms:
>
> - port - sub-node describing a single endpoint connected to the VIN
> from external SoC pins as described in video-interfaces.txt[1].
> @@ -63,7 +63,7 @@ The per-board settings Gen2 platforms:
> - data-enable-active: polarity of CLKENB signal, see [1] for
> description. Default is active high.
>
> -The per-board settings Gen3 and RZ/G2 platforms:
> +The per-board settings for Gen3 and RZ/G2 platforms:
>
> Gen3 and RZ/G2 platforms can support both a single connected parallel input
> source from external SoC pins (port@0) and/or multiple parallel input sources
> --
> 2.17.1
>
--
Regards,
Niklas Söderlund
next prev parent reply other threads:[~2019-10-24 18:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 13:14 [PATCH] media: dt-bindings: rcar_vin: Document RZ/G1 per-board settings Geert Uytterhoeven
2019-10-24 18:02 ` Niklas Söderlund [this message]
2019-10-29 19:37 ` Rob Herring
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=20191024180203.GA24998@bigcity.dyn.berto.se \
--to=niklas.soderlund+renesas@ragnatech.se \
--cc=biju.das@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrizio.castro@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=hans.verkuil@cisco.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--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).