From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH v4 4/7] arm64: dts: r8a7795: salvator-x: Add DU1 and DU2 external dot clocks
Date: Wed, 10 May 2017 15:29:18 +0300 [thread overview]
Message-ID: <8258966.uNlgZS14Hm@avalon> (raw)
In-Reply-To: <CAMuHMdUv6L4-=WSSrOQGoV0wh8tSXurx1hfwP7-38csvwMz6yQ@mail.gmail.com>
Hi Geert,
On Wednesday 10 May 2017 10:57:04 Geert Uytterhoeven wrote:
> On Wed, May 10, 2017 at 9:04 AM, Laurent Pinchart wrote:
> > The DU1 and DU2 external dot clocks are fixed frequency clock generators
> > running at 33MHz.
> >
> > Signed-off-by: Laurent Pinchart
> > <laurent.pinchart+renesas@ideasonboard.com>
> > ---
> >
> > arch/arm64/boot/dts/renesas/salvator-x.dtsi | 23 +++++++++++++++++++++++
> > 1 file changed, 23 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/renesas/salvator-x.dtsi
> > b/arch/arm64/boot/dts/renesas/salvator-x.dtsi index
> > 2cd0cce818e7..884c63ebba69 100644
> > --- a/arch/arm64/boot/dts/renesas/salvator-x.dtsi
> > +++ b/arch/arm64/boot/dts/renesas/salvator-x.dtsi
> > @@ -212,6 +212,19 @@
> >
> > #clock-cells = <0>;
> > clock-frequency = <24576000>;
> >
> > };
> >
> > +
> > + /* External DU dot clocks */
> > + x21_clk: x21-clock {
> > + compatible = "fixed-clock";
> > + #clock-cells = <0>;
> > + clock-frequency = <33000000>;
> > + };
> > +
> > + x22_clk: x22-clock {
> > + compatible = "fixed-clock";
> > + #clock-cells = <0>;
> > + clock-frequency = <33000000>;
> > + };
> >
> > };
> >
> > &audio_clk_a {
> >
> > @@ -238,6 +251,16 @@
> >
> > pinctrl-names = "default";
> > status = "okay";
> >
> > + clocks = <&cpg CPG_MOD 724>,
> > + <&cpg CPG_MOD 723>,
> > + <&cpg CPG_MOD 722>,
> > + <&cpg CPG_MOD 721>,
> > + <&cpg CPG_MOD 727>,
> > + <&x21_clk>,
> > + <&x22_clk>;
> > + clock-names = "du.0", "du.1", "du.2", "du.3", "lvds.0",
> > + "dclkin.1", "dclkin.2";
>
> Another H3 vs. M3-W oddity: DU_DOTCLKIN2 is wired to pin AR7 on H3 SiP,
> and AR8 on M3-W SiP.
> But crystal X22 is wired to AR7, and AR8 is not connected.
> Hence on M3-W, "dclkin.2" is not available, cfr. "NC <M3SiP>" in the
> schematics.
Indeed :-/ X22 is populated though. No wonder the board is expensive :-)
> So either the du clocks and -names should be overridden in
> r8a7795-salvator.dtsi to add "dclkin.2", or in r8a7796-salvator.dtsi to
> remove it.
Or specified differently in both. I'll do that, it would be confusing
otherwise.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2017-05-10 12:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 7:04 [PATCH v4 0/7] R-Car H3 HDMI output DT integration Laurent Pinchart
2017-05-10 7:04 ` [PATCH v4 1/7] arm64: dts: r8a7795: Add HDMI encoder support Laurent Pinchart
2017-05-10 8:24 ` Geert Uytterhoeven
2017-05-10 7:04 ` [PATCH v4 2/7] arm64: dts: r8a7796: Add display placeholders Laurent Pinchart
2017-05-10 8:44 ` Geert Uytterhoeven
2017-05-10 7:04 ` [PATCH v4 3/7] arm64: dts: renesas: salvator-x: Enable HDMI outputs Laurent Pinchart
2017-05-10 8:28 ` Geert Uytterhoeven
2017-05-10 11:52 ` Laurent Pinchart
2017-05-10 12:13 ` Geert Uytterhoeven
2017-05-11 14:58 ` Simon Horman
2017-05-10 7:04 ` [PATCH v4 4/7] arm64: dts: r8a7795: salvator-x: Add DU1 and DU2 external dot clocks Laurent Pinchart
2017-05-10 8:57 ` Geert Uytterhoeven
2017-05-10 12:29 ` Laurent Pinchart [this message]
2017-05-10 12:34 ` Geert Uytterhoeven
2017-05-10 7:04 ` [PATCH v4 5/7] arm64: dts: r8a7795: salvator-x: Add DU0 and DU3 " Laurent Pinchart
2017-05-10 8:32 ` Geert Uytterhoeven
2017-05-10 7:04 ` [PATCH v4 6/7] arm64: dts: r8a7795: salvator-x: Add panel backlight support Laurent Pinchart
2017-05-10 7:04 ` [PATCH v4 7/7] ARM: shmobile: dts: Switch to panel-lvds bindings for Mitsubishi panels Laurent Pinchart
2017-05-10 9:14 ` [PATCH v4 0/7] R-Car H3 HDMI output DT integration Simon Horman
2017-05-11 14:59 ` Simon Horman
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=8258966.uNlgZS14Hm@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=geert@linux-m68k.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-renesas-soc@vger.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).