From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND v3] clk: return probe defer when DT clock not yet ready
Date: Mon, 24 Feb 2014 17:02:00 -0800 [thread overview]
Message-ID: <20140225010200.22529.17490@quantum> (raw)
In-Reply-To: <20140219185315.GV21483@n2100.arm.linux.org.uk>
Quoting Russell King - ARM Linux (2014-02-19 10:53:15)
> On Wed, Feb 19, 2014 at 07:03:05PM +0100, Jean-Francois Moine wrote:
> > On Mon, 25 Nov 2013 19:47:04 +0100
> > Jean-Francois Moine <moinejf@free.fr> wrote:
> >
> > > At probe time, a clock device may not be ready when some other device
> > > wants to use it.
> > >
> > > This patch lets the functions clk_get/devm_clk_get return a probe defer
> > > when the clock is defined in the DT but not yet available.
> >
> > Hi Mike,
> >
> > Any news about this patch?
>
> Mike,
>
> Can you please have a look at this patch so that either you or I can take
> this. It /is/ required so that subsystems can correctly identify whether
> a clock is missing because it's not specified in DT, or whether the clock
> is missing because it's specified in DT but doesn't yet exist.
>
> This patch has been hanging around for ages and deserves some attention.
I only saw this patch now thanks to another thread. I have some
aggressive mail filtering going on and I guess maybe the original ASoC
subject had something to do with that?
Oh well. I've pull this patch into clk-next for testing. I'll see if
anything goes boom.
Thanks for the patch and longsuffering patience!
Regards,
Mike
>
> Thanks.
>
prev parent reply other threads:[~2014-02-25 1:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 13:25 [PATCH RESEND v3] clk: return probe defer when DT clock not yet ready Jean-Francois Moine
2014-02-18 13:23 ` Sylwester Nawrocki
2014-02-19 18:03 ` Jean-Francois Moine
2014-02-19 18:53 ` Russell King - ARM Linux
2014-02-25 1:02 ` Mike Turquette [this message]
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=20140225010200.22529.17490@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 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).