From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/4] clk: add of_clk_src_onecell_get() support
Date: Wed, 22 Aug 2012 20:42:37 -0500 [thread overview]
Message-ID: <50358A8D.3090803@gmail.com> (raw)
In-Reply-To: <1345642590-29905-2-git-send-email-shawn.guo@linaro.org>
On 08/22/2012 08:36 AM, Shawn Guo wrote:
> For those SoCs that have hundreds of clock outputs, their clock
> DT bindings could reasonably define #clock-cells as 1 and require
> the client device specify the index of the clock it consumes in the
> cell of its "clocks" phandle.
>
> Add a generic of_clk_src_onecell_get() function for this purpose.
>
> Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
> ---
I have some reservations about how generic this will end up being, but
we have to start somewhere. So, for the series:
Reviewed-by: Rob Herring <rob.herring@calxeda.com>
> drivers/clk/clk.c | 14 ++++++++++++++
> include/linux/clk-provider.h | 5 +++++
> 2 files changed, 19 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
> index efdfd00..308f058 100644
> --- a/drivers/clk/clk.c
> +++ b/drivers/clk/clk.c
> @@ -1582,6 +1582,20 @@ struct clk *of_clk_src_simple_get(struct of_phandle_args *clkspec,
> }
> EXPORT_SYMBOL_GPL(of_clk_src_simple_get);
>
> +struct clk *of_clk_src_onecell_get(struct of_phandle_args *clkspec, void *data)
> +{
> + struct clk_onecell_data *clk_data = data;
> + unsigned int idx = clkspec->args[0];
> +
> + if (idx >= clk_data->clk_num) {
> + pr_err("%s: invalid clock index %d\n", __func__, idx);
> + return ERR_PTR(-EINVAL);
> + }
> +
> + return clk_data->clks[idx];
> +}
> +EXPORT_SYMBOL_GPL(of_clk_src_onecell_get);
> +
> /**
> * of_clk_add_provider() - Register a clock provider for a node
> * @np: Device node pointer associated with clock provider
> diff --git a/include/linux/clk-provider.h b/include/linux/clk-provider.h
> index 77335fa..8fe6ec7 100644
> --- a/include/linux/clk-provider.h
> +++ b/include/linux/clk-provider.h
> @@ -360,6 +360,11 @@ int of_clk_add_provider(struct device_node *np,
> void of_clk_del_provider(struct device_node *np);
> struct clk *of_clk_src_simple_get(struct of_phandle_args *clkspec,
> void *data);
> +struct clk_onecell_data {
> + struct clk **clks;
> + unsigned int clk_num;
> +};
> +struct clk *of_clk_src_onecell_get(struct of_phandle_args *clkspec, void *data);
> const char *of_clk_get_parent_name(struct device_node *np, int index);
> void of_clk_init(const struct of_device_id *matches);
>
>
next prev parent reply other threads:[~2012-08-23 1:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 13:36 [PATCH v2 0/4] Move imx6q/28/23 clock lookup over to device tree Shawn Guo
2012-08-22 13:36 ` [PATCH v2 1/4] clk: add of_clk_src_onecell_get() support Shawn Guo
2012-08-23 1:42 ` Rob Herring [this message]
2012-08-31 6:41 ` Shawn Guo
2012-09-06 22:11 ` Mike Turquette
2012-09-07 0:26 ` Shawn Guo
2012-09-07 19:24 ` Mike Turquette
2012-09-10 6:25 ` Shawn Guo
2012-09-10 17:32 ` Mike Turquette
2012-09-11 1:19 ` Shawn Guo
2012-08-22 13:36 ` [PATCH v2 2/4] ARM: imx6q: replace clk_register_clkdev with clock DT lookup Shawn Guo
2012-08-22 13:36 ` [PATCH v2 3/4] clk: mxs: replace imx28 " Shawn Guo
2012-08-22 13:36 ` [PATCH v2 4/4] clk: mxs: replace imx23 " Shawn Guo
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=50358A8D.3090803@gmail.com \
--to=robherring2@gmail.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).