From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Daniel Mack <zonque@gmail.com>
Cc: Afzal Mohammed <afzal.mohd.ma@gmail.com>,
Fabio Estevam <festevam@gmail.com>,
Russell King <linux@arm.linux.org.uk>,
Mike Turquette <mturquette@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <robherring2@gmail.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: Question about fixed-clock
Date: Tue, 12 Mar 2013 18:40:33 +0000 [thread overview]
Message-ID: <20130312184033.GK19942@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <5139E7F3.5010906@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 974 bytes --]
On Fri, Mar 08, 2013 at 02:30:27PM +0100, Daniel Mack wrote:
> On 08.03.2013 03:15, Mark Brown wrote:
> > Wouldn't this just be set up by the DT in the same way that other
> > off-SoC hardware is?
> Well, I thought so too. To repeat, in my DT, I have:
OK, I got CCed in part way through the thread.
> I would have expected that "fixed-clock" is matched by a driver lurking
> around for DT boards, just like what the "fixed-regulator" driver does
> for instance. But the clock device isn't initialized unless board code
> explicitly calls of_clk_init() with a table mentioning "fixed-clock", as
> in my patch.
> I don't know the clock framework well enough, but it seems that either
> all DT boards are supposed to do the same in their generic bits (which
> sounds like a lot of code duplication), or the fixed-clock driver should
> behave like any other driver wrt its probing from DT. I'm open to
> suggestions :)
Your expectation sounds like what I'd expect too...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-03-12 18:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 23:55 Question about fixed-clock Daniel Mack
2013-02-19 0:07 ` Daniel Mack
2013-02-19 1:33 ` Fabio Estevam
2013-02-19 9:53 ` Daniel Mack
[not found] ` <20130219172246.11471.14635@quantum>
2013-02-19 17:32 ` Daniel Mack
2013-03-02 14:09 ` Daniel Mack
2013-03-07 18:42 ` Afzal Mohammed
2013-03-07 22:31 ` Daniel Mack
2013-03-08 2:15 ` Mark Brown
2013-03-08 13:30 ` Daniel Mack
2013-03-09 8:26 ` Sebastian Hesselbarth
2013-03-12 18:40 ` Mark Brown [this message]
2013-02-19 3:39 ` Afzal Mohammed
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=20130312184033.GK19942@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=afzal.mohd.ma@gmail.com \
--cc=festevam@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mturquette@linaro.org \
--cc=robherring2@gmail.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=zonque@gmail.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