From: haojian.zhuang@linaro.org (Haojian Zhuang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/6] clk: mux: add CLK_MUX_HIWORD_MASK
Date: Tue, 4 Jun 2013 23:05:13 +0800 [thread overview]
Message-ID: <1370358317-12768-3-git-send-email-haojian.zhuang@linaro.org> (raw)
In-Reply-To: <1370358317-12768-1-git-send-email-haojian.zhuang@linaro.org>
There's a HIWORD mask field in Hisilicon Hi3620 clock mux register. This
field must be set while update the clk mux register. In order to reuse
the clk-mux driver, append the CLK_MUX_HIWORD_MASK field into mux->flags.
Signed-off-by: Haojian Zhuang <haojian.zhuang@linaro.org>
---
drivers/clk/clk-mux.c | 8 ++++++++
include/linux/clk-provider.h | 2 ++
2 files changed, 10 insertions(+)
diff --git a/drivers/clk/clk-mux.c b/drivers/clk/clk-mux.c
index 25b1734..887f462 100644
--- a/drivers/clk/clk-mux.c
+++ b/drivers/clk/clk-mux.c
@@ -70,6 +70,7 @@ static int clk_mux_set_parent(struct clk_hw *hw, u8 index)
{
struct clk_mux *mux = to_clk_mux(hw);
u32 val;
+ u8 width = 0;
unsigned long flags = 0;
if (mux->table)
@@ -89,6 +90,13 @@ static int clk_mux_set_parent(struct clk_hw *hw, u8 index)
val = readl(mux->reg);
val &= ~(mux->mask << mux->shift);
val |= index << mux->shift;
+ if (mux->flags & CLK_MUX_HIWORD_MASK) {
+ width = fls(mux->mask) - ffs(mux->mask) + 1;
+ if (width + mux->shift > 16)
+ pr_warn("mux value exceeds LOWORD field\n");
+ else
+ val |= mux->mask << (mux->shift + 16);
+ }
writel(val, mux->reg);
if (mux->lock)
diff --git a/include/linux/clk-provider.h b/include/linux/clk-provider.h
index 1186098..6ba32bc 100644
--- a/include/linux/clk-provider.h
+++ b/include/linux/clk-provider.h
@@ -299,6 +299,7 @@ struct clk *clk_register_divider_table(struct device *dev, const char *name,
* Flags:
* CLK_MUX_INDEX_ONE - register index starts at 1, not 0
* CLK_MUX_INDEX_BIT - register index is a single bit (power of two)
+ * CLK_MUX_HIWORD_MASK - register contains high 16-bit as mask field
*/
struct clk_mux {
struct clk_hw hw;
@@ -312,6 +313,7 @@ struct clk_mux {
#define CLK_MUX_INDEX_ONE BIT(0)
#define CLK_MUX_INDEX_BIT BIT(1)
+#define CLK_MUX_HIWORD_MASK BIT(2)
extern const struct clk_ops clk_mux_ops;
--
1.8.1.2
next prev parent reply other threads:[~2013-06-04 15:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 15:05 [PATCH v2 0/6] support hi3xxx soc Haojian Zhuang
2013-06-04 15:05 ` [PATCH v2 1/6] ARM: debug: support debug ll on hisilicon soc Haojian Zhuang
2013-06-04 15:13 ` Arnd Bergmann
2013-06-04 15:05 ` Haojian Zhuang [this message]
2013-06-04 15:05 ` [PATCH v2 3/6] clk: divider: add CLK_DIVIDER_HIWORD_MASK flag Haojian Zhuang
2013-06-07 9:15 ` Linus Walleij
2013-06-07 9:30 ` Haojian Zhuang
2013-06-07 12:31 ` Heiko Stübner
2013-06-08 3:17 ` Haojian Zhuang
2013-06-08 9:20 ` Heiko Stübner
2013-06-04 15:05 ` [PATCH v2 4/6] clk: hi3xxx: add clock support Haojian Zhuang
2013-06-04 15:05 ` [PATCH v2 5/6] ARM: hi3xxx: add board support with device tree Haojian Zhuang
2013-06-04 15:16 ` Arnd Bergmann
2013-06-05 3:04 ` Haojian Zhuang
2013-06-07 10:54 ` Arnd Bergmann
2013-06-04 15:05 ` [PATCH v2 6/6] ARM: hi3xxx: enable hi4511 " Haojian Zhuang
2013-06-04 15:20 ` Arnd Bergmann
2013-06-04 15:31 ` Haojian Zhuang
2013-06-05 3:56 ` [PATCH v3 5/6] ARM: hi3xxx: add board support " Haojian Zhuang
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=1370358317-12768-3-git-send-email-haojian.zhuang@linaro.org \
--to=haojian.zhuang@linaro.org \
--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).