From: Kieran Bingham <kieran.bingham@ideasonboard.com>
To: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Simon Horman" <horms@verge.net.au>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org
Cc: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Subject: Re: [PATCH 5/5] arm64: dts: renesas: eagle: add HDMI output using the ADV7511W
Date: Thu, 15 Feb 2018 09:09:11 +0000 [thread overview]
Message-ID: <feff4afa-843f-3906-4726-b5ba4dcfd65f@ideasonboard.com> (raw)
In-Reply-To: <20180131161811.12699-6-niklas.soderlund@ragnatech.se>
Hi Niklas,
On 31/01/18 16:18, Niklas Söderlund wrote:
> From: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
>
> Add the HDMI connector and the ADV7511W, also connect it to LVDS. Enable
> the DU and LVDS to be able to use the HDMI output.
>
> Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
> ---
> arch/arm64/boot/dts/renesas/r8a77970-eagle.dts | 66 ++++++++++++++++++++++++++
> 1 file changed, 66 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/renesas/r8a77970-eagle.dts b/arch/arm64/boot/dts/renesas/r8a77970-eagle.dts
> index 359e835cca9876fe..c0fd144970c55fa2 100644
> --- a/arch/arm64/boot/dts/renesas/r8a77970-eagle.dts
> +++ b/arch/arm64/boot/dts/renesas/r8a77970-eagle.dts
> @@ -31,6 +31,17 @@
> /* first 128MB is reserved for secure area. */
> reg = <0x0 0x48000000 0x0 0x38000000>;
> };
> +
> + hdmi-out {
> + compatible = "hdmi-connector";
> + type = "a";
> +
> + port {
> + hdmi_con_out: endpoint {
> + remote-endpoint = <&adv7511_out>;
> + };
> + };
> + };
> };
>
> &avb {
> @@ -67,9 +78,46 @@
> gpio-controller;
> #gpio-cells = <2>;
> };
> +
> + hdmi@39 {
> + compatible = "adi,adv7511w";
> + reg = <0x39>;
It looks like the Eagle-V3M expansion board also has an ADV7511 chip on it.
That brings it into the same category as the Wheat board, and because of a fault
on the ADV7511 reset - *both* chips will have to specify alternate custom I2C
registers. (Alternatively, the expansion board could override the reg and
reg-names of this device node to handle this as an overlay style fix up).
Not an issue with this patch - or a blocker - but something to be aware of.
--
Kieran
> + interrupt-parent = <&gpio1>;
> + interrupts = <20 IRQ_TYPE_LEVEL_LOW>;
> +
> + adi,input-depth = <8>;
> + adi,input-colorspace = "rgb";
> + adi,input-clock = "1x";
> + adi,input-style = <1>;
> + adi,input-justification = "evenly";
> +
> + ports {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + port@0 {
> + reg = <0>;
> + adv7511_in: endpoint {
> + remote-endpoint = <&lvds0_out>;
> + };
> + };
> +
> + port@1 {
> + reg = <1>;
> + adv7511_out: endpoint {
> + remote-endpoint = <&hdmi_con_out>;
> + };
> + };
> + };
> + };
> };
>
> &pfc {
> + du_pins: du {
> + groups = "du_rgb666", "du_sync", "du_oddf", "du_clk_out";
> + function = "du";
> + };
> +
> i2c0_pins: i2c0 {
> groups = "i2c0";
> function = "i2c0";
> @@ -92,3 +140,21 @@
>
> status = "okay";
> };
> +
> +&du {
> + pinctrl-0 = <&du_pins>;
> + pinctrl-names = "default";
> + status = "okay";
> +};
> +
> +&lvds0 {
> + status = "okay";
> +
> + ports {
> + port@1 {
> + endpoint {
> + remote-endpoint = <&adv7511_in>;
> + };
> + };
> + };
> +};
>
next prev parent reply other threads:[~2018-02-15 9:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 16:18 [PATCH 0/5] arm64: dts: renesas: r8a77970: enable HDMI output Niklas Söderlund
2018-01-31 16:18 ` [PATCH 1/5] arm64: dts: renesas: r8a77970: add FCPVD node Niklas Söderlund
2018-01-31 16:18 ` [PATCH 2/5] arm64: dts: renesas: r8a77970: Add VSPD instance Niklas Söderlund
2018-01-31 16:18 ` [PATCH 3/5] arm64: dts: renesas: r8a77970: add DU instance Niklas Söderlund
2018-01-31 16:18 ` [PATCH 4/5] arm64: dts: renesas: r8a77970: add the LVDS instance Niklas Söderlund
2018-01-31 18:34 ` Geert Uytterhoeven
2018-01-31 16:18 ` [PATCH 5/5] arm64: dts: renesas: eagle: add HDMI output using the ADV7511W Niklas Söderlund
2018-02-15 9:09 ` Kieran Bingham [this message]
2018-02-01 8:16 ` [PATCH 0/5] arm64: dts: renesas: r8a77970: enable HDMI output Sergei Shtylyov
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=feff4afa-843f-3906-4726-b5ba4dcfd65f@ideasonboard.com \
--to=kieran.bingham@ideasonboard.com \
--cc=devicetree@vger.kernel.org \
--cc=horms@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=niklas.soderlund@ragnatech.se \
/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