From: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-renesas-soc@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH 1/2] clk: renesas: r8a779h0: Add FCPVX clock
Date: Fri, 17 Jan 2025 17:44:43 +0100 [thread overview]
Message-ID: <20250117164443.GF873961@ragnatech.se> (raw)
In-Reply-To: <CAMuHMdUgRJB03rGrVzG2Ft3XJ+0eXbHMHtxbpOkh2A5vRzRhtA@mail.gmail.com>
Hello Geert,
Thanks for your feedback.
On 2025-01-17 17:29:21 +0100, Geert Uytterhoeven wrote:
> Hi Niklas,
>
> On Wed, Jan 15, 2025 at 6:59 PM Niklas Söderlund
> <niklas.soderlund+renesas@ragnatech.se> wrote:
> > Add the FCPVX modules clock for Renesas R-Car V4M.
> >
> > Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
>
> Thanks for your patch!
>
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> i.e. will queue in renesas-clk for v6.15.
>
> > --- a/drivers/clk/renesas/r8a779h0-cpg-mssr.c
> > +++ b/drivers/clk/renesas/r8a779h0-cpg-mssr.c
> > @@ -239,6 +239,7 @@ static const struct mssr_mod_clk r8a779h0_mod_clks[] __initconst = {
> > DEF_MOD("pfc1", 916, R8A779H0_CLK_CP),
> > DEF_MOD("pfc2", 917, R8A779H0_CLK_CP),
> > DEF_MOD("tsc2:tsc1", 919, R8A779H0_CLK_CL16M),
> > + DEF_MOD("fcpvx0", 1100, R8A779H0_CLK_S0D4_VIO),
>
> Any specific reason you are not using S0D1, like on R-Car V4H?
> I can update this while applying.
Nice catch it should be S0D1. I picked it since it listed both FCPVX and
VSPX, and I compared it to S0D2 which only lists FCPVX. Checking the
datasheet again now after your feedback I see indeed S0D1 also lists
both FCPVX and VSPX.
Thanks for fixing this while applying, same comment for 2/2.
>
> > DEF_MOD("ssiu", 2926, R8A779H0_CLK_S0D6_PER),
> > DEF_MOD("ssi", 2927, R8A779H0_CLK_S0D6_PER),
>
> 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
--
Kind Regards,
Niklas Söderlund
next prev parent reply other threads:[~2025-01-17 16:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 17:59 [PATCH 0/2] clk: renesas: r8a779h0: Add FCPVX and VSPX clocks Niklas Söderlund
2025-01-15 17:59 ` [PATCH 1/2] clk: renesas: r8a779h0: Add FCPVX clock Niklas Söderlund
2025-01-17 16:29 ` Geert Uytterhoeven
2025-01-17 16:44 ` Niklas Söderlund [this message]
2025-01-15 17:59 ` [PATCH 2/2] clk: renesas: r8a779h0: Add VSPX clock Niklas Söderlund
2025-01-17 16:30 ` Geert Uytterhoeven
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=20250117164443.GF873961@ragnatech.se \
--to=niklas.soderlund+renesas@ragnatech.se \
--cc=geert@linux-m68k.org \
--cc=linux-clk@vger.kernel.org \
--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