From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
Cc: "Simon Horman" <horms@verge.net.au>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Subject: Re: [PATCH 4/5] arm64: dts: renesas: r8a77970: add the LVDS instance
Date: Wed, 31 Jan 2018 19:34:32 +0100 [thread overview]
Message-ID: <CAMuHMdUcqRcGr+n=VqbeNiuGddNww1U+Pe1dy=-kwyGNqxrrMw@mail.gmail.com> (raw)
In-Reply-To: <20180131161811.12699-5-niklas.soderlund@ragnatech.se>
Hi Niklas,
On Wed, Jan 31, 2018 at 5:18 PM, Niklas Söderlund
<niklas.soderlund@ragnatech.se> wrote:
> From: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
>
> Add the LVDS device to r8a77970.dtsi in a disabled state. Also connect
> the it to the LVDS output of the DU.
>
> Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
FWIW, Sergei sent the exact same patch before...
> ---
> arch/arm64/boot/dts/renesas/r8a77970.dtsi | 25 +++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/renesas/r8a77970.dtsi b/arch/arm64/boot/dts/renesas/r8a77970.dtsi
> index e1d8aa0fbc1e4f90..3945a34550d17321 100644
> --- a/arch/arm64/boot/dts/renesas/r8a77970.dtsi
> +++ b/arch/arm64/boot/dts/renesas/r8a77970.dtsi
> @@ -655,6 +655,31 @@
> port@1 {
> reg = <1>;
> du_out_lvds0: endpoint {
> + remote-endpoint = <&lvds0_in>;
> + };
> + };
> + };
> + };
> +
> + lvds0: lvds@feb90000 {
> + compatible = "renesas,r8a77970-lvds";
> + reg = <0 0xfeb90000 0 0x14>;
> + clocks = <&cpg CPG_MOD 727>;
... also with missing power-domains and resets properties.
> + status = "disabled";
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2018-01-31 18:34 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 [this message]
2018-01-31 16:18 ` [PATCH 5/5] arm64: dts: renesas: eagle: add HDMI output using the ADV7511W Niklas Söderlund
[not found] ` <20180131161811.12699-6-niklas.soderlund-1zkq55x86MTxsAP9Fp7wbw@public.gmane.org>
2018-02-15 9:09 ` Kieran Bingham
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='CAMuHMdUcqRcGr+n=VqbeNiuGddNww1U+Pe1dy=-kwyGNqxrrMw@mail.gmail.com' \
--to=geert@linux-m68k.org \
--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;
as well as URLs for NNTP newsgroup(s).