From: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
To: Geert Uytterhoeven <geert+renesas@glider.be>, linux-clk@vger.kernel.org
Cc: linux-renesas-soc@vger.kernel.org,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Subject: [PATCH 0/5] clk: renesas: Add TMU clocks
Date: Wed, 9 Dec 2020 20:53:38 +0100 [thread overview]
Message-ID: <20201209195343.803120-1-niklas.soderlund+renesas@ragnatech.se> (raw)
Hi,
This series adds the missing TMU clocks for most Renesas R-Car Gen3
SoCs. I have tested this series on all boards but D3 and E3 as I do not
have access to those. But I see no reason they should not not work
equally well as they the boards I can test on.
Niklas Söderlund (5):
clk: renesas: r8a7795: Add TMU clocks
clk: renesas: r8a7796: Add TMU clocks
clk: renesas: r8a77965: Add TMU clocks
clk: renesas: r8a77990: Add TMU clocks
clk: renesas: r8a77995: Add TMU clocks
drivers/clk/renesas/r8a7795-cpg-mssr.c | 5 +++++
drivers/clk/renesas/r8a7796-cpg-mssr.c | 5 +++++
drivers/clk/renesas/r8a77965-cpg-mssr.c | 5 +++++
drivers/clk/renesas/r8a77990-cpg-mssr.c | 5 +++++
drivers/clk/renesas/r8a77995-cpg-mssr.c | 5 +++++
5 files changed, 25 insertions(+)
--
2.29.2
next reply other threads:[~2020-12-09 19:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 19:53 Niklas Söderlund [this message]
2020-12-09 19:53 ` [PATCH 1/5] clk: renesas: r8a7795: Add TMU clocks Niklas Söderlund
2020-12-10 12:32 ` Geert Uytterhoeven
2020-12-09 19:53 ` [PATCH 2/5] clk: renesas: r8a7796: " Niklas Söderlund
2020-12-10 12:34 ` Geert Uytterhoeven
2020-12-09 19:53 ` [PATCH 3/5] clk: renesas: r8a77965: " Niklas Söderlund
2020-12-10 12:35 ` Geert Uytterhoeven
2020-12-09 19:53 ` [PATCH 4/5] clk: renesas: r8a77990: " Niklas Söderlund
2020-12-10 12:36 ` Geert Uytterhoeven
2020-12-09 19:53 ` [PATCH 5/5] clk: renesas: r8a77995: " Niklas Söderlund
2020-12-10 12:41 ` 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=20201209195343.803120-1-niklas.soderlund+renesas@ragnatech.se \
--to=niklas.soderlund+renesas@ragnatech.se \
--cc=geert+renesas@glider.be \
--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;
as well as URLs for NNTP newsgroup(s).