From: Biju Das <biju.das.jz@bp.renesas.com>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: Biju Das <biju.das.jz@bp.renesas.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Sergei Shtylyov <sergei.shtylyov@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
linux-renesas-soc@vger.kernel.org, linux-clk@vger.kernel.org,
Chris Paterson <Chris.Paterson2@renesas.com>,
Biju Das <biju.das@bp.renesas.com>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: [PATCH v4 0/4] Add GbEthernet Clock support
Date: Wed, 22 Sep 2021 16:51:41 +0100 [thread overview]
Message-ID: <20210922155145.28156-1-biju.das.jz@bp.renesas.com> (raw)
This patch series aims to add GbEthernet clock support.
GbEthernet clock support involves handing mux clock support
for HP clock and coupled clock for axi/chi module clocks which
shares same bit for controlling the clock output.
This patch series depend upon [1]
[1] https://patchwork.kernel.org/project/linux-renesas-soc/patch/20210922112405.26413-2-biju.das.jz@bp.renesas.com/
v3->v4:
* Renamed PLL5_2_DIV12 and PLL6_2_DIV2 to PLL5_250 and PLL6_250.
* Added locking, in case both clocks are changed concurrently
* initialized mstp_clock.enabled to match the current hardware state.
v2->v3:
* Rebased to latest renesas-clk
* Updated commit header for all patches
* Replaced CLK_PLL5_2 with PLL5_FOUT3
* Removed CLK_PLL6_2 and pll6_2 as the clk is sourced from PLL6
* Added enabled flag to track the status of clock, if it is coupled
with another clock
* Introduced siblings pointer which points to the other coupled
clock
* coupled clock linking is done during module clk register.
* rzg2l_mod_clock_is_enabled function returns soft state of the
module clocks, if it is coupled with another clock
v1->v2:
* No change. Separated clock patches from driver patch series as per [1]
[1]
https://www.spinics.net/lists/linux-renesas-soc/msg59067.html
v1:-
* New patch
Biju Das (4):
clk: renesas: rzg2l: Add support to handle MUX clocks
clk: renesas: r9a07g044: Add ethernet clock sources
clk: renesas: rzg2l: Add support to handle coupled clocks
clk: renesas: r9a07g044: Add GbEthernet clock/reset
drivers/clk/renesas/r9a07g044-cpg.c | 29 ++++++++-
drivers/clk/renesas/rzg2l-cpg.c | 96 +++++++++++++++++++++++++++++
drivers/clk/renesas/rzg2l-cpg.h | 26 +++++++-
3 files changed, 149 insertions(+), 2 deletions(-)
--
2.17.1
next reply other threads:[~2021-09-22 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 15:51 Biju Das [this message]
2021-09-22 15:51 ` [PATCH v4 1/4] clk: renesas: rzg2l: Add support to handle MUX clocks Biju Das
2021-09-22 15:51 ` [PATCH v4 2/4] clk: renesas: r9a07g044: Add ethernet clock sources Biju Das
2021-09-22 15:51 ` [PATCH v4 3/4] clk: renesas: rzg2l: Add support to handle coupled clocks Biju Das
2021-09-23 9:49 ` Geert Uytterhoeven
2021-09-22 15:51 ` [PATCH v4 4/4] clk: renesas: r9a07g044: Add GbEthernet clock/reset Biju Das
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=20210922155145.28156-1-biju.das.jz@bp.renesas.com \
--to=biju.das.jz@bp.renesas.com \
--cc=Chris.Paterson2@renesas.com \
--cc=andrew@lunn.ch \
--cc=biju.das@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=linux-clk@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=sboyd@kernel.org \
--cc=sergei.shtylyov@gmail.com \
/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).