From: Michael Turquette <mturquette@linaro.org>
To: Tomeu Vizoso <tomeu.vizoso@collabora.com>,
linux-arm-kernel@lists.infradead.org
Cc: "Stéphane Marchesin" <stephane.marchesin@gmail.com>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Alexander Holler" <holler@ahsoftware.de>,
"Grant Likely" <grant.likely@linaro.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Tomeu Vizoso" <tomeu.vizoso@collabora.com>,
"Stephen Boyd" <sboyd@codeaurora.org>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 17/21] clk: Probe clk providers on demand
Date: Wed, 27 May 2015 23:16:43 -0700 [thread overview]
Message-ID: <20150528061643.22384.27268@quantum> (raw)
In-Reply-To: <1432565608-26036-18-git-send-email-tomeu.vizoso@collabora.com>
Quoting Tomeu Vizoso (2015-05-25 07:53:21)
> When looking up a clk through its DT node, ensure that the corresponding
> device has been registered.
> =
> Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>
Ack.
Regards,
Mike
> ---
> drivers/clk/clk.c | 3 +++
> 1 file changed, 3 insertions(+)
> =
> diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
> index 5b0f418..f9e8a8d 100644
> --- a/drivers/clk/clk.c
> +++ b/drivers/clk/clk.c
> @@ -18,6 +18,7 @@
> #include <linux/list.h>
> #include <linux/slab.h>
> #include <linux/of.h>
> +#include <linux/of_platform.h>
> #include <linux/device.h>
> #include <linux/init.h>
> #include <linux/sched.h>
> @@ -2985,6 +2986,8 @@ struct clk *__of_clk_get_from_provider(struct of_ph=
andle_args *clkspec,
> if (!clkspec)
> return ERR_PTR(-EINVAL);
> =
> + of_platform_device_ensure(clkspec->np);
> +
> /* Check if we have such a provider in our array */
> mutex_lock(&of_clk_mutex);
> list_for_each_entry(provider, &of_clk_providers, link) {
> -- =
> 2.4.1
>=20
next prev parent reply other threads:[~2015-05-28 6:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 14:53 [PATCH 00/21] On-demand device registration Tomeu Vizoso
2015-05-25 14:53 ` [PATCH 17/21] clk: Probe clk providers on demand Tomeu Vizoso
2015-05-28 6:16 ` Michael Turquette [this message]
2015-05-28 4:33 ` [PATCH 00/21] On-demand device registration Rob Herring
2015-06-03 19:57 ` Grygorii.Strashko@linaro.org
2015-06-04 8:39 ` Tomeu Vizoso
2015-06-04 16:51 ` Grygorii.Strashko@linaro.org
2015-06-04 20:39 ` Alexander Holler
2015-06-08 12:26 ` Enrico Weigelt, metux IT consult
2015-06-08 18:14 ` Alexander Holler
2015-06-08 18:18 ` Alexander Holler
2015-06-22 15:23 ` Tomeu Vizoso
2015-06-23 0:01 ` Rob Herring
2015-06-02 8:48 ` Linus Walleij
2015-06-02 10:14 ` Tomeu Vizoso
2015-06-10 7:30 ` Linus Walleij
2015-06-10 10:19 ` Tomeu Vizoso
2015-06-10 12:23 ` Andrzej Hajda
2015-06-11 8:15 ` Linus Walleij
2015-06-11 9:56 ` Tomeu Vizoso
2015-06-03 21:12 ` Rob Clark
2015-06-04 21:03 ` Alexander Holler
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=20150528061643.22384.27268@quantum \
--to=mturquette@linaro.org \
--cc=dmitry.torokhov@gmail.com \
--cc=grant.likely@linaro.org \
--cc=holler@ahsoftware.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=stephane.marchesin@gmail.com \
--cc=thierry.reding@gmail.com \
--cc=tomeu.vizoso@collabora.com \
/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