From: ping.bai@nxp.com (Bai Ping)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/4] driver: clk: imx: Add CLK_IS_CRITICAL flag for busy divider and busy mux
Date: Thu, 8 Mar 2018 17:47:22 +0800 [thread overview]
Message-ID: <1520502445-22576-1-git-send-email-ping.bai@nxp.com> (raw)
The busy divider and busy mux is actually used by the system critical clocks,
so add 'CLK_IS_CRITICAL' to clocks registered with these two type.
Signed-off-by: Bai Ping <ping.bai@nxp.com>
---
change from V3->v4:
- fix a typo in commit log
---
drivers/clk/imx/clk-busy.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/clk/imx/clk-busy.c b/drivers/clk/imx/clk-busy.c
index 6df3389..9903652 100644
--- a/drivers/clk/imx/clk-busy.c
+++ b/drivers/clk/imx/clk-busy.c
@@ -101,7 +101,7 @@ struct clk *imx_clk_busy_divider(const char *name, const char *parent_name,
init.name = name;
init.ops = &clk_busy_divider_ops;
- init.flags = CLK_SET_RATE_PARENT;
+ init.flags = CLK_SET_RATE_PARENT | CLK_IS_CRITICAL;
init.parent_names = &parent_name;
init.num_parents = 1;
@@ -175,7 +175,7 @@ struct clk *imx_clk_busy_mux(const char *name, void __iomem *reg, u8 shift,
init.name = name;
init.ops = &clk_busy_mux_ops;
- init.flags = 0;
+ init.flags = CLK_IS_CRITICAL;
init.parent_names = parent_names;
init.num_parents = num_parents;
--
1.9.1
next reply other threads:[~2018-03-08 9:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 9:47 Bai Ping [this message]
2018-03-08 9:47 ` [PATCH v4 2/4] driver: clk: imx: add new gate/gate2 wrapper funtion Bai Ping
2018-03-08 9:47 ` [PATCH v4 3/4] Document: dt: binding: imx: update clock doc for imx6sll Bai Ping
2018-03-08 9:47 ` [PATCH v4 4/4] driver: clk: imx: add clock driver " Bai Ping
2018-03-09 2:45 ` Shawn Guo
2018-03-09 5:01 ` Jacky Bai
2018-03-09 2:31 ` [PATCH v4 1/4] driver: clk: imx: Add CLK_IS_CRITICAL flag for busy divider and busy mux Shawn Guo
2018-03-09 5:00 ` Jacky Bai
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=1520502445-22576-1-git-send-email-ping.bai@nxp.com \
--to=ping.bai@nxp.com \
--cc=linux-arm-kernel@lists.infradead.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).