From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
linux-clk <linux-clk@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH 2/2] clk: renesas: r8a779a0: Add THS/TSC clock
Date: Fri, 27 Nov 2020 10:13:03 +0100 [thread overview]
Message-ID: <CAMuHMdW34yrcbJ=pTXRTRoQyXXJ6_8_TPBjS-vHo6pxiuOqKCg@mail.gmail.com> (raw)
In-Reply-To: <20201126221416.3110341-3-niklas.soderlund+renesas@ragnatech.se>
Hi Niklas,
On Thu, Nov 26, 2020 at 11:14 PM Niklas Söderlund
<niklas.soderlund+renesas@ragnatech.se> wrote:
> Implement support for the THS/TSC clock on V3U
>
> Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
Thanks for your patch!
> --- a/drivers/clk/renesas/r8a779a0-cpg-mssr.c
> +++ b/drivers/clk/renesas/r8a779a0-cpg-mssr.c
> @@ -190,6 +190,7 @@ static const struct mssr_mod_clk r8a779a0_mod_clks[] __initconst = {
> DEF_MOD("vin35", 827, R8A779A0_CLK_S1D1),
> DEF_MOD("vin36", 828, R8A779A0_CLK_S1D1),
> DEF_MOD("vin37", 829, R8A779A0_CLK_S1D1),
> + DEF_MOD("thermal", 919, R8A779A0_CLK_CP),
> };
The R-Car V3U Series User's Manual calls this clock "tsc", and states its
parent is "cl16m".
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
prev parent reply other threads:[~2020-11-27 9:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 22:14 [PATCH 0/2] clk: renesas: r8a779a0: Add clocks to support thermal Niklas Söderlund
2020-11-26 22:14 ` [PATCH 1/2] clk: renesas: r8a779a0: Add CP clock Niklas Söderlund
2020-11-27 9:02 ` Geert Uytterhoeven
2020-11-26 22:14 ` [PATCH 2/2] clk: renesas: r8a779a0: Add THS/TSC clock Niklas Söderlund
2020-11-27 9:13 ` Geert Uytterhoeven [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='CAMuHMdW34yrcbJ=pTXRTRoQyXXJ6_8_TPBjS-vHo6pxiuOqKCg@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=geert+renesas@glider.be \
--cc=linux-clk@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund+renesas@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).