From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2 v4] clk: Add Gemini SoC clock controller
Date: Wed, 14 Jun 2017 08:55:23 -0700 [thread overview]
Message-ID: <20170614155523.GX20170@codeaurora.org> (raw)
In-Reply-To: <CACRpkdbF4syppZsFv2hbB1JxHvnndbS53yY8Pkbz2zoq5Jjzjw@mail.gmail.com>
On 06/14, Linus Walleij wrote:
> On Mon, Jun 12, 2017 at 11:02 PM, Stephen Boyd <sboyd@codeaurora.org> wrote:
> > On 06/12, Linus Walleij wrote:
>
> >> So the deferred clock makes the whole platform hang because the timer
> >> needs it. Without a clocksource, the delay loop cannot be calibrated, so
> >> it hangs there.
> >
> > Ok. So can the certain clks that are required to get the timer
> > going be put into CLK_OF_DECLARE_DRIVER() and then have a regular
> > platform driver for the rest of the clks that aren't required for
> > early boot? We've been doing this sort of hybrid design lately,
> > so hopefully that works here too.
>
> Sure I will give it a spin!
>
> Is there a best-in-class driver doing this I can use as inspiration?
>
Great. I suppose drivers/clk/nxp/clk-lpc18xx-creg.c or
drivers/clk/axis/clk-artpec6.c would be good examples.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-06-14 15:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 8:20 [PATCH 2/2 v4] clk: Add Gemini SoC clock controller Linus Walleij
2017-06-01 7:02 ` Stephen Boyd
2017-06-05 13:34 ` Linus Walleij
2017-06-05 19:58 ` Stephen Boyd
2017-06-08 12:18 ` Linus Walleij
2017-06-12 6:21 ` Linus Walleij
2017-06-12 21:02 ` Stephen Boyd
2017-06-14 11:31 ` Linus Walleij
2017-06-14 15:55 ` Stephen Boyd [this message]
2017-06-15 7:16 ` Linus Walleij
2017-06-15 8:55 ` Geert Uytterhoeven
2017-06-15 12:57 ` Linus Walleij
2017-06-15 21:00 ` Stephen Boyd
2017-06-16 8:35 ` Linus Walleij
2017-06-15 21:55 ` Philipp Zabel
2017-06-16 8:38 ` Linus Walleij
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=20170614155523.GX20170@codeaurora.org \
--to=sboyd@codeaurora.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).