From: mturquette@ti.com (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: wm831x: Add initial WM831x clock driver
Date: Tue, 12 Jun 2012 10:09:52 -0700 [thread overview]
Message-ID: <20120612170952.GE19410@gmail.com> (raw)
In-Reply-To: <1337004985-22549-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On 20120514-15:16, Mark Brown wrote:
> The WM831x and WM832x series of PMICs contain a flexible clocking
> subsystem intended to provide always on and system core clocks. It
> features:
>
> - A 32.768kHz crystal oscillator which can optionally be used to pass
> through an externally generated clock.
> - A FLL which can be clocked from either the 32.768kHz oscillator or
> the CLKIN pin.
> - A CLKOUT pin which can bring out either the oscillator or the FLL
> output.
> - The 32.768kHz clock can also optionally be brought out on the GPIO
> pins of the device.
>
> This driver fully supports the 32.768kHz oscillator and CLKOUT. The FLL
> is supported only in AUTO mode, the full flexibility of the FLL cannot
> currently be used.
>
> Due to a lack of access to systems where the core SoC has been converted
> to use the generic clock API this driver has been compile tested only.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Hi Mark,
I've taken this into my new clk-next branch which is now based on top of
v3.5-rc2. I'll send a request to Stephen Rothwell in the coming days so
that clk-next starts getting tested.
Just so we're clear, it is likely that in the current state of things
your clk_prepare calls could deadlock on a production system. This is a
shortcoming I'm trying to address in the framework, and I don't see it
as a reason to prevent merging your patch, but I didn't want you to be
surprised if you tested this code on a platform ported to common clk.
Regards,
Mike
next prev parent reply other threads:[~2012-06-12 17:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 14:16 [PATCH] clk: wm831x: Add initial WM831x clock driver Mark Brown
2012-05-16 5:00 ` Turquette, Mike
2012-05-16 7:53 ` Mark Brown
2012-06-12 17:09 ` Mike Turquette [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-06-04 14:44 Mark Brown
2012-05-17 9:04 Mark Brown
2012-03-22 11:33 Mark Brown
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=20120612170952.GE19410@gmail.com \
--to=mturquette@ti.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).