From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-renesas-soc@vger.kernel.org, linux-clk@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Biju Das <biju.das.jz@bp.renesas.com>,
Prabhakar <prabhakar.csengg@gmail.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: [PATCH 0/4] Renesas RZ/G2x enable RPC clocks
Date: Fri, 16 Oct 2020 13:17:05 +0100 [thread overview]
Message-ID: <20201016121709.8447-1-prabhakar.mahadev-lad.rj@bp.renesas.com> (raw)
Hi All,
This patch series enables RPC clocks on RZ/G2x SoC's.
This series applies on top of [1].
[1] https://git.kernel.org/pub/scm/linux/kernel/git/geert/
renesas-drivers.git/log/?h=renesas-clk-for-v5.11
Cheers,
Prabhakar
Biju Das (2):
clk: renesas: r8a774a1: Add RPC clocks
clk: renesas: r8a774b1: Add RPC clocks
Lad Prabhakar (2):
clk: renesas: rcar-gen3: Add support to pass custom RPCSRC div table
clk: renesas: r8a774c0: Add RPC clocks
drivers/clk/renesas/r8a774a1-cpg-mssr.c | 8 ++++++++
drivers/clk/renesas/r8a774b1-cpg-mssr.c | 8 ++++++++
drivers/clk/renesas/r8a774c0-cpg-mssr.c | 14 ++++++++++++++
drivers/clk/renesas/rcar-gen3-cpg.c | 2 ++
drivers/clk/renesas/renesas-cpg-mssr.h | 6 ++++++
5 files changed, 38 insertions(+)
--
2.17.1
next reply other threads:[~2020-10-16 12:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 12:17 Lad Prabhakar [this message]
2020-10-16 12:17 ` [PATCH 1/4] clk: renesas: rcar-gen3: Add support to pass custom RPCSRC div table Lad Prabhakar
2020-10-16 12:17 ` [PATCH 2/4] clk: renesas: r8a774a1: Add RPC clocks Lad Prabhakar
2020-10-22 13:29 ` Geert Uytterhoeven
2020-10-16 12:17 ` [PATCH 3/4] clk: renesas: r8a774b1: " Lad Prabhakar
2020-10-22 13:31 ` Geert Uytterhoeven
2020-10-16 12:17 ` [PATCH 4/4] clk: renesas: r8a774c0: " Lad Prabhakar
2020-10-22 14:09 ` Geert Uytterhoeven
2020-10-23 11:05 ` Lad, Prabhakar
2020-10-23 12:42 ` 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=20201016121709.8447-1-prabhakar.mahadev-lad.rj@bp.renesas.com \
--to=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=prabhakar.csengg@gmail.com \
--cc=sboyd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.