From: Ulrich Hecht <uli+renesas@fpond.eu>
To: linux-renesas-soc@vger.kernel.org
Cc: wsa@the-dreams.de, geert@linux-m68k.org, magnus.damm@gmail.com,
Ulrich Hecht <uli+renesas@fpond.eu>
Subject: [PATCH v3 1/3] clk: renesas: cpg-mssr: add support for never-disable clocks
Date: Mon, 11 May 2020 18:33:56 +0200 [thread overview]
Message-ID: <1589214838-18075-2-git-send-email-uli+renesas@fpond.eu> (raw)
In-Reply-To: <1589214838-18075-1-git-send-email-uli+renesas@fpond.eu>
This adds facilities to mark clocks as never to be turned off. The primary
application is the RWDT clock, which needs to remain on throughout the boot
process if enabled by the bootloader.
Signed-off-by: Ulrich Hecht <uli+renesas@fpond.eu>
---
drivers/clk/renesas/renesas-cpg-mssr.c | 10 ++++++++++
drivers/clk/renesas/renesas-cpg-mssr.h | 9 +++++++++
2 files changed, 19 insertions(+)
diff --git a/drivers/clk/renesas/renesas-cpg-mssr.c b/drivers/clk/renesas/renesas-cpg-mssr.c
index 8f6dff3..e234156 100644
--- a/drivers/clk/renesas/renesas-cpg-mssr.c
+++ b/drivers/clk/renesas/renesas-cpg-mssr.c
@@ -152,11 +152,13 @@ static struct cpg_mssr_priv *cpg_mssr_priv;
* @hw: handle between common and hardware-specific interfaces
* @index: MSTP clock number
* @priv: CPG/MSSR private data
+ * @never_disable: clock shall never be disabled
*/
struct mstp_clock {
struct clk_hw hw;
u32 index;
struct cpg_mssr_priv *priv;
+ bool never_disable;
};
#define to_mstp_clock(_hw) container_of(_hw, struct mstp_clock, hw)
@@ -175,6 +177,9 @@ static int cpg_mstp_clock_endisable(struct clk_hw *hw, bool enable)
dev_dbg(dev, "MSTP %u%02u/%pC %s\n", reg, bit, hw->clk,
enable ? "ON" : "OFF");
+ if (!enable && clock->never_disable)
+ return 0;
+
spin_lock_irqsave(&priv->rmw_lock, flags);
if (priv->stbyctrl) {
@@ -423,6 +428,11 @@ static void __init cpg_mssr_register_mod_clk(const struct mssr_mod_clk *mod,
init.flags |= CLK_IS_CRITICAL;
break;
}
+ for (i = 0; i < info->num_never_disable_mod_clks; i++)
+ if (id == info->never_disable_mod_clks[i]) {
+ clock->never_disable = true;
+ break;
+ }
parent_name = __clk_get_name(parent);
init.parent_names = &parent_name;
diff --git a/drivers/clk/renesas/renesas-cpg-mssr.h b/drivers/clk/renesas/renesas-cpg-mssr.h
index 55a18ef..654d3a789 100644
--- a/drivers/clk/renesas/renesas-cpg-mssr.h
+++ b/drivers/clk/renesas/renesas-cpg-mssr.h
@@ -105,6 +105,11 @@ struct device_node;
* @crit_mod_clks: Array with Module Clock IDs of critical clocks that
* should not be disabled without a knowledgeable driver
* @num_crit_mod_clks: Number of entries in crit_mod_clks[]
+ * @never_disable_mod_clks: Array with Module Clock IDs of clocks that
+ * should not be disabled even if they seem to
+ * be unused
+ * @num_never_disable_mod_clks: Number of entries in
+ * never_disable_mod_clks[]
*
* @core_pm_clks: Array with IDs of Core Clocks that are suitable for Power
* Management, in addition to Module Clocks
@@ -141,6 +146,10 @@ struct cpg_mssr_info {
const unsigned int *crit_mod_clks;
unsigned int num_crit_mod_clks;
+ /* Module Clocks that should not be disabled even if unused */
+ const unsigned int *never_disable_mod_clks;
+ unsigned int num_never_disable_mod_clks;
+
/* Core Clocks suitable for PM, in addition to the Module Clocks */
const unsigned int *core_pm_clks;
unsigned int num_core_pm_clks;
--
2.7.4
next prev parent reply other threads:[~2020-05-11 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 16:33 [PATCH v3 0/3] clk: renesas: cpg-mssr: add never-disable option Ulrich Hecht
2020-05-11 16:33 ` Ulrich Hecht [this message]
2020-05-11 16:33 ` [PATCH v3 2/3] clk: renesas: rcar-gen3: mark RWDT clocks as never-disable Ulrich Hecht
2020-05-11 16:33 ` [PATCH v3 3/3] clk: renesas: rzg2: mark RWDT clock " Ulrich Hecht
2020-05-11 17:50 ` [PATCH v3 0/3] clk: renesas: cpg-mssr: add never-disable option 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=1589214838-18075-2-git-send-email-uli+renesas@fpond.eu \
--to=uli+renesas@fpond.eu \
--cc=geert@linux-m68k.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=wsa@the-dreams.de \
/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).