From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Kieran Bingham <kieran@ksquared.org.uk>,
linux-renesas-soc@vger.kernel.org,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Subject: Re: [PATCH] clk: renesas: Provide r8a7795 FDP1 clocks
Date: Tue, 17 May 2016 18:42:40 +0300 [thread overview]
Message-ID: <60985808.sO50ZmgucX@avalon> (raw)
In-Reply-To: <CAMuHMdWX7H184XBTHxoh76e3=2a+qphZVvvHJiR87MUnJcA4Fg@mail.gmail.com>
Hello Kieran,
On Tuesday 17 May 2016 12:25:37 Geert Uytterhoeven wrote:
> On Tue, May 17, 2016 at 12:03 PM, Kieran Bingham wrote:
> > Add the clocks with a parent of S2D1 for now, until the correct
> > parentage is identified
>
> Thanks for your patch!
>
> > --- a/drivers/clk/renesas/r8a7795-cpg-mssr.c
> > +++ b/drivers/clk/renesas/r8a7795-cpg-mssr.c
> > @@ -128,6 +128,9 @@ static const struct cpg_core_clk r8a7795_core_clks[]
> > __initconst = {>
> > };
> >
> > static const struct mssr_mod_clk r8a7795_mod_clks[] __initconst = {
> >
> > + DEF_MOD("fdp1-ch2", 117, R8A7795_CLK_S2D1),
> > + DEF_MOD("fdp1-ch1", 118, R8A7795_CLK_S2D1),
> > + DEF_MOD("fdp1-ch0", 119, R8A7795_CLK_S2D1),
>
> I would call them "fdp1-2" etc., to match the documentation for the various
> Module Stop registers.
>
> Apart from that:
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
After fixing that (and double-checking the clock parent),
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2016-05-17 15:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 10:03 [PATCH] Provide r8a7795 FDP1 clocks Kieran Bingham
2016-05-17 10:03 ` [PATCH] clk: renesas: " Kieran Bingham
2016-05-17 10:25 ` Geert Uytterhoeven
2016-05-17 13:03 ` Kieran Bingham
2016-05-17 15:42 ` Geert Uytterhoeven
2016-05-17 15:43 ` Laurent Pinchart
2016-05-17 15:42 ` Laurent Pinchart [this message]
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=60985808.sO50ZmgucX@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=geert@linux-m68k.org \
--cc=kieran@ksquared.org.uk \
--cc=kuninori.morimoto.gx@renesas.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