From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 3/5] clk: dt: binding for basic multiplexer clock
Date: Tue, 09 Jul 2013 06:58:08 -0700 [thread overview]
Message-ID: <20130709135808.10823.84545@quantum> (raw)
In-Reply-To: <20130626084058.GA10833@e106331-lin.cambridge.arm.com>
Quoting Mark Rutland (2013-06-26 01:40:58)
> Hi,
>
> I have a couple of minor comments.
>
> On Fri, Jun 21, 2013 at 07:14:14AM +0100, Mike Turquette wrote:
> > Device Tree binding for the basic clock multiplexer, plus the setup
> > function to register the clock. Based on the existing fixed-clock
> > binding.
> >
> > Includes minor beautification of clk-provider.h where some whitespace is
> > added and of_fixed_factor_clock_setup is relocated to maintain a
> > consistent style.
> >
> > Tero Kristo contributed helpful bug fixes to this patch.
> >
> > Signed-off-by: Mike Turquette <mturquette@linaro.org>
> > ---
> > Changes since v2:
> > * added hiword-mask property to the binding
> > * changed bit-shift property from u8 to u32 in the dt binding
> >
> > Changes since v1:
> > * pass shift value into clk_register_mux_table
> > * s/multiplexor/multiplexer/
> > * removed debug prints
> > * mask is u32, shift is u8
> > * DT property names use dashes instead of underscores
> > * DT property names are more verbose
> > * shift property is optional in binding and can be auto-generated from a
> > full 32-bit mask
> >
> > .../devicetree/bindings/clock/mux-clock.txt | 79 ++++++++++++++++++++++
> > drivers/clk/clk-mux.c | 65 +++++++++++++++++-
> > include/linux/clk-provider.h | 5 +-
> > 3 files changed, 147 insertions(+), 2 deletions(-)
> > create mode 100644 Documentation/devicetree/bindings/clock/mux-clock.txt
> >
> > diff --git a/Documentation/devicetree/bindings/clock/mux-clock.txt b/Documentation/devicetree/bindings/clock/mux-clock.txt
> > new file mode 100644
> > index 0000000..54cb8d1
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/clock/mux-clock.txt
> > @@ -0,0 +1,79 @@
> > +Binding for simple mux clock.
> > +
> > +This binding uses the common clock binding[1]. It assumes a
> > +register-mapped multiplexer with multiple input clock signals or
> > +parents, one of which can be selected as output. This clock does not
> > +gate or adjust the parent rate via a divider or multiplier.
> > +
> > +By default the "clocks" property lists the parents in the same order
> > +as they are programmed into the regster. E.g:
> > +
> > + clocks = <&foo_clock>, <&bar_clock>, <&baz_clock>;
> > +
> > +results in programming the register as follows:
> > +
> > +register value selected parent clock
> > +0 foo_clock
> > +1 bar_clock
> > +2 baz_clock
> > +
> > +Some clock controller IPs do not allow a value of zero to be programmed
> > +into the register, instead indexing begins at 1. The optional property
> > +"index_one" modified the scheme as follows:
>
> I assume this is meant to be "index-starts-at-one", given the code and
> changelog?
>
> > +
> > +register value selected clock parent
> > +1 foo_clock
> > +2 bar_clock
> > +3 baz_clock
> > +
> > +Additionally an optional table of bit and parent pairs may be supplied
> > +like so:
> > +
> > + table = <&foo_clock 0x0>, <&bar_clock, 0x2>, <&baz_clock, 0x4>;
> > +
> > +where the first value in the pair is the parent clock and the second
> > +value is the bitfield to be programmed into the register.
> > +
> > +The binding must provide the register to control the mux and the mask
> > +for the corresponding control bits. Optionally the number of bits to
> > +shift that mask if necessary. If the shift value is missing it is the
> > +same as supplying a zero shift.
> > +
> > +[1] Documentation/devicetree/bindings/clock/clock-bindings.txt
> > +
> > +Required properties:
> > +- compatible : shall be "mux-clock".
> > +- #clock-cells : from common clock binding; shall be set to 0.
> > +- clocks : link phandles of parent clocks
> > +- reg : base address for register controlling adjustable mux
> > +- bit-mask : arbitrary bitmask for programming the adjustable mux
> > +
> > +Optional properties:
> > +- clock-output-names : From common clock binding.
> > +- table : array of integer pairs defining parents & bitfield values
> > +- bit-shift : number of bits to shift the bit-mask, defaults to
> > + (ffs(mask) - 1) if not present
> > +- index-starts-at-one : valid input select programming starts at 1, not
> > + zero
> > +- hiword-mask : lower half of the register programs the mux, upper half
> > + of the register indicates bits that were updated in the lower half
> > +
> > +Examples:
> > + clock: clock at 4a008100 {
> > + compatible = "mux-clock";
> > + #clock-cells = <0>;
> > + clocks = <&clock_foo>, <&clock_bar>, <&clock_baz>;
> > + reg = <0x4a008100 0x4>
> > + mask = <0x3>;
> > + index_one;
>
> And here too?
>
> [...]
>
> > +/**
> > + * of_mux_clk_setup() - Setup function for simple mux rate clock
> > + */
> > +void of_mux_clk_setup(struct device_node *node)
> > +{
> > + struct clk *clk;
> > + const char *clk_name = node->name;
> > + void __iomem *reg;
> > + int num_parents;
> > + const char **parent_names;
> > + int i;
> > + u8 clk_mux_flags = 0;
> > + u32 mask = 0;
> > + u32 shift = 0;
> > +
> > + of_property_read_string(node, "clock-output-names", &clk_name);
> > +
> > + num_parents = of_clk_get_parent_count(node);
> > + if (num_parents < 1) {
> > + pr_err("%s: mux-clock %s must have parent(s)\n",
> > + __func__, node->name);
> > + return;
> > + }
> > +
> > + parent_names = kzalloc((sizeof(char*) * num_parents),
> > + GFP_KERNEL);
> > +
> > + for (i = 0; i < num_parents; i++)
> > + parent_names[i] = of_clk_get_parent_name(node, i);
> > +
> > + reg = of_iomap(node, 0);
>
> Would it not be a good idea to check this isn't NULL before we pass it
> to clk_register_mux_table later?
>
> > +
> > + if (of_property_read_u32(node, "bit-mask", &mask)) {
> > + pr_err("%s: missing bit-mask property for %s\n", __func__, node->name);
> > + return;
> > + }
> > +
> > + if (of_property_read_u32(node, "bit-shift", &shift)) {
> > + shift = __ffs(mask);
> > + pr_debug("%s: bit-shift property defaults to 0x%x for %s\n",
> > + __func__, shift, node->name);
> > + }
> > +
> > + if (of_property_read_bool(node, "index-starts-at-one"))
> > + clk_mux_flags |= CLK_MUX_INDEX_ONE;
> > +
> > + if (of_property_read_bool(node, "hiword-mask"))
> > + clk_mux_flags |= CLK_MUX_HIWORD_MASK;
> > +
> > + clk = clk_register_mux_table(NULL, clk_name, parent_names, num_parents,
> > + 0, reg, (u8) shift, mask, clk_mux_flags,
> > + NULL, NULL);
>
> Why do you need the (u8) cast on shift? Isn't that implicit?
All of your suggestions are good. I'll roll them into the next version.
Regards,
Mike
>
> Thanks,
> Mark.
WARNING: multiple messages have this Message-ID (diff)
From: Mike Turquette <mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
Cc: "devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
Stephen Boyd <sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Tero Kristo <t-kristo-l0cyMroinI0@public.gmane.org>,
Haojian Zhuang
<haojian.zhuang-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Matt Sealey <neko-HhXTZounMxbZATc7fWT8Dg@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH v3 3/5] clk: dt: binding for basic multiplexer clock
Date: Tue, 09 Jul 2013 06:58:08 -0700 [thread overview]
Message-ID: <20130709135808.10823.84545@quantum> (raw)
In-Reply-To: <20130626084058.GA10833-NuALmloUBlrZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
Quoting Mark Rutland (2013-06-26 01:40:58)
> Hi,
>
> I have a couple of minor comments.
>
> On Fri, Jun 21, 2013 at 07:14:14AM +0100, Mike Turquette wrote:
> > Device Tree binding for the basic clock multiplexer, plus the setup
> > function to register the clock. Based on the existing fixed-clock
> > binding.
> >
> > Includes minor beautification of clk-provider.h where some whitespace is
> > added and of_fixed_factor_clock_setup is relocated to maintain a
> > consistent style.
> >
> > Tero Kristo contributed helpful bug fixes to this patch.
> >
> > Signed-off-by: Mike Turquette <mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
> > ---
> > Changes since v2:
> > * added hiword-mask property to the binding
> > * changed bit-shift property from u8 to u32 in the dt binding
> >
> > Changes since v1:
> > * pass shift value into clk_register_mux_table
> > * s/multiplexor/multiplexer/
> > * removed debug prints
> > * mask is u32, shift is u8
> > * DT property names use dashes instead of underscores
> > * DT property names are more verbose
> > * shift property is optional in binding and can be auto-generated from a
> > full 32-bit mask
> >
> > .../devicetree/bindings/clock/mux-clock.txt | 79 ++++++++++++++++++++++
> > drivers/clk/clk-mux.c | 65 +++++++++++++++++-
> > include/linux/clk-provider.h | 5 +-
> > 3 files changed, 147 insertions(+), 2 deletions(-)
> > create mode 100644 Documentation/devicetree/bindings/clock/mux-clock.txt
> >
> > diff --git a/Documentation/devicetree/bindings/clock/mux-clock.txt b/Documentation/devicetree/bindings/clock/mux-clock.txt
> > new file mode 100644
> > index 0000000..54cb8d1
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/clock/mux-clock.txt
> > @@ -0,0 +1,79 @@
> > +Binding for simple mux clock.
> > +
> > +This binding uses the common clock binding[1]. It assumes a
> > +register-mapped multiplexer with multiple input clock signals or
> > +parents, one of which can be selected as output. This clock does not
> > +gate or adjust the parent rate via a divider or multiplier.
> > +
> > +By default the "clocks" property lists the parents in the same order
> > +as they are programmed into the regster. E.g:
> > +
> > + clocks = <&foo_clock>, <&bar_clock>, <&baz_clock>;
> > +
> > +results in programming the register as follows:
> > +
> > +register value selected parent clock
> > +0 foo_clock
> > +1 bar_clock
> > +2 baz_clock
> > +
> > +Some clock controller IPs do not allow a value of zero to be programmed
> > +into the register, instead indexing begins at 1. The optional property
> > +"index_one" modified the scheme as follows:
>
> I assume this is meant to be "index-starts-at-one", given the code and
> changelog?
>
> > +
> > +register value selected clock parent
> > +1 foo_clock
> > +2 bar_clock
> > +3 baz_clock
> > +
> > +Additionally an optional table of bit and parent pairs may be supplied
> > +like so:
> > +
> > + table = <&foo_clock 0x0>, <&bar_clock, 0x2>, <&baz_clock, 0x4>;
> > +
> > +where the first value in the pair is the parent clock and the second
> > +value is the bitfield to be programmed into the register.
> > +
> > +The binding must provide the register to control the mux and the mask
> > +for the corresponding control bits. Optionally the number of bits to
> > +shift that mask if necessary. If the shift value is missing it is the
> > +same as supplying a zero shift.
> > +
> > +[1] Documentation/devicetree/bindings/clock/clock-bindings.txt
> > +
> > +Required properties:
> > +- compatible : shall be "mux-clock".
> > +- #clock-cells : from common clock binding; shall be set to 0.
> > +- clocks : link phandles of parent clocks
> > +- reg : base address for register controlling adjustable mux
> > +- bit-mask : arbitrary bitmask for programming the adjustable mux
> > +
> > +Optional properties:
> > +- clock-output-names : From common clock binding.
> > +- table : array of integer pairs defining parents & bitfield values
> > +- bit-shift : number of bits to shift the bit-mask, defaults to
> > + (ffs(mask) - 1) if not present
> > +- index-starts-at-one : valid input select programming starts at 1, not
> > + zero
> > +- hiword-mask : lower half of the register programs the mux, upper half
> > + of the register indicates bits that were updated in the lower half
> > +
> > +Examples:
> > + clock: clock@4a008100 {
> > + compatible = "mux-clock";
> > + #clock-cells = <0>;
> > + clocks = <&clock_foo>, <&clock_bar>, <&clock_baz>;
> > + reg = <0x4a008100 0x4>
> > + mask = <0x3>;
> > + index_one;
>
> And here too?
>
> [...]
>
> > +/**
> > + * of_mux_clk_setup() - Setup function for simple mux rate clock
> > + */
> > +void of_mux_clk_setup(struct device_node *node)
> > +{
> > + struct clk *clk;
> > + const char *clk_name = node->name;
> > + void __iomem *reg;
> > + int num_parents;
> > + const char **parent_names;
> > + int i;
> > + u8 clk_mux_flags = 0;
> > + u32 mask = 0;
> > + u32 shift = 0;
> > +
> > + of_property_read_string(node, "clock-output-names", &clk_name);
> > +
> > + num_parents = of_clk_get_parent_count(node);
> > + if (num_parents < 1) {
> > + pr_err("%s: mux-clock %s must have parent(s)\n",
> > + __func__, node->name);
> > + return;
> > + }
> > +
> > + parent_names = kzalloc((sizeof(char*) * num_parents),
> > + GFP_KERNEL);
> > +
> > + for (i = 0; i < num_parents; i++)
> > + parent_names[i] = of_clk_get_parent_name(node, i);
> > +
> > + reg = of_iomap(node, 0);
>
> Would it not be a good idea to check this isn't NULL before we pass it
> to clk_register_mux_table later?
>
> > +
> > + if (of_property_read_u32(node, "bit-mask", &mask)) {
> > + pr_err("%s: missing bit-mask property for %s\n", __func__, node->name);
> > + return;
> > + }
> > +
> > + if (of_property_read_u32(node, "bit-shift", &shift)) {
> > + shift = __ffs(mask);
> > + pr_debug("%s: bit-shift property defaults to 0x%x for %s\n",
> > + __func__, shift, node->name);
> > + }
> > +
> > + if (of_property_read_bool(node, "index-starts-at-one"))
> > + clk_mux_flags |= CLK_MUX_INDEX_ONE;
> > +
> > + if (of_property_read_bool(node, "hiword-mask"))
> > + clk_mux_flags |= CLK_MUX_HIWORD_MASK;
> > +
> > + clk = clk_register_mux_table(NULL, clk_name, parent_names, num_parents,
> > + 0, reg, (u8) shift, mask, clk_mux_flags,
> > + NULL, NULL);
>
> Why do you need the (u8) cast on shift? Isn't that implicit?
All of your suggestions are good. I'll roll them into the next version.
Regards,
Mike
>
> Thanks,
> Mark.
next prev parent reply other threads:[~2013-07-09 13:58 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 6:14 [PATCH v3 0/5] clk: dt: bindings for mux, divider & gate clocks Mike Turquette
2013-06-21 6:14 ` Mike Turquette
2013-06-21 6:14 ` [PATCH v3 1/5] clk: divider: replace bitfield width with mask Mike Turquette
2013-06-21 6:14 ` Mike Turquette
2013-06-21 6:14 ` [PATCH v3 2/5] clk: of: helper for determining number of parent clocks Mike Turquette
2013-06-21 6:14 ` Mike Turquette
2013-06-21 6:14 ` Mike Turquette
2013-06-21 6:14 ` [PATCH v3 3/5] clk: dt: binding for basic multiplexer clock Mike Turquette
2013-06-21 6:14 ` Mike Turquette
2013-06-25 8:27 ` Haojian Zhuang
2013-06-25 8:27 ` Haojian Zhuang
2013-06-25 17:40 ` Mike Turquette
2013-06-25 17:40 ` Mike Turquette
2013-06-26 8:40 ` Mark Rutland
2013-06-26 8:40 ` Mark Rutland
2013-07-09 13:58 ` Mike Turquette [this message]
2013-07-09 13:58 ` Mike Turquette
2013-06-21 6:14 ` [PATCH v3 4/5] clk: dt: binding for basic divider clock Mike Turquette
2013-06-21 6:14 ` Mike Turquette
2013-06-21 6:14 ` [PATCH v3 5/5] clk: dt: binding for basic gate clock Mike Turquette
2013-06-21 6:14 ` Mike Turquette
2013-06-22 17:04 ` [PATCH v3 0/5] clk: dt: bindings for mux, divider & gate clocks Heiko Stübner
2013-06-22 17:04 ` Heiko Stübner
2013-06-22 17:04 ` Heiko Stübner
2013-07-18 21:04 ` Stephen Boyd
2013-07-18 21:04 ` Stephen Boyd
2013-07-18 21:04 ` Stephen Boyd
2013-08-22 4:14 ` Mike Turquette
2013-08-22 4:14 ` Mike Turquette
2013-08-23 4:32 ` Stephen Boyd
2013-08-23 4:32 ` Stephen Boyd
2013-08-23 6:54 ` Mike Turquette
2013-08-23 6:54 ` Mike Turquette
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=20130709135808.10823.84545@quantum \
--to=mturquette@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 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.