From: Prabhakar <prabhakar.csengg@gmail.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-renesas-soc@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org,
Prabhakar <prabhakar.csengg@gmail.com>,
Biju Das <biju.das.jz@bp.renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: [RFC PATCH 0/2] clk: renesas: RZ/G2L: Add support for no PM clocks
Date: Tue, 27 Sep 2022 21:30:42 +0100 [thread overview]
Message-ID: <20220927203044.751611-1-prabhakar.mahadev-lad.rj@bp.renesas.com> (raw)
From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Hi All,
This patch series adds support for indicating MOD clocks as no PM (if any).
Patch#1 adds DEF_NO_PM() macro to flagup no PM clock and patch #2 switches
sysclk and vclk clocks to no PM.
Sending it as an RFC as there wasn't any way we could obtain the priv data
due to which I had to create a static global var for rzg2l_cpg_priv.
Cheers,
Prabhakar
Lad Prabhakar (2):
clk: renesas: rzg2l: Don't assume all CPG_MOD clocks support PM
clk: renesas: r9a07g044: Mark CRU_SYSCLK and CRU_VCLK as no PM
drivers/clk/renesas/r9a07g044-cpg.c | 4 ++--
drivers/clk/renesas/rzg2l-cpg.c | 35 +++++++++++++++++++++++++----
drivers/clk/renesas/rzg2l-cpg.h | 12 +++++++---
3 files changed, 42 insertions(+), 9 deletions(-)
--
2.25.1
next reply other threads:[~2022-09-27 20:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 20:30 Prabhakar [this message]
2022-09-27 20:30 ` [RFC PATCH 1/2] clk: renesas: rzg2l: Don't assume all CPG_MOD clocks support PM Prabhakar
2022-09-28 7:02 ` Biju Das
2022-09-28 8:28 ` Lad, Prabhakar
2022-09-28 8:42 ` Biju Das
2022-09-28 9:37 ` Lad, Prabhakar
2022-09-27 20:30 ` [RFC PATCH 2/2] clk: renesas: r9a07g044: Mark CRU_SYSCLK and CRU_VCLK as no PM Prabhakar
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=20220927203044.751611-1-prabhakar.mahadev-lad.rj@bp.renesas.com \
--to=prabhakar.csengg@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=laurent.pinchart@ideasonboard.com \
--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.mahadev-lad.rj@bp.renesas.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.