From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Daniel Mack <zonque@gmail.com>
Cc: Sebastian Hesselbarh <sebastian.hesselbarth@googlemail.com>,
linux-kernel@vger.kernel.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
mturquette@ti.com
Subject: Re: [RFC] Common clock framework for external clock generators
Date: Thu, 11 Oct 2012 18:00:34 +0200 [thread overview]
Message-ID: <5076ED22.3060803@gmail.com> (raw)
In-Reply-To: <5076847A.3010705@gmail.com>
On 10/11/2012 10:34 AM, Daniel Mack wrote:
>> I recently read about the newly introduced common clock framework (ccf)
>> and wondered if this could be also used for external, e.g. i2c attached,
>> clock generators.
>>
>> Based on my current understanding of the framework I wrote such a
>> driver and now I want to present it here for clarification of some
>> remarks I have regarding the framework itself.
>
> May I kindly ask what happened to this driver? Are you planning to do
> another spin for submission?
Daniel,
the driver is still on my list but moved more and more downwards as I
got caught by mach-dove DT integration. There is still some work to do,
namely regmap and DT. It is used by some off-mainline tree for SolidRun
CuBox quite successfully since then. Does any of you work rely on
a working si5351 driver?
Sebastian
next prev parent reply other threads:[~2012-10-11 16:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 1:11 [RFC] Common clock framework for external clock generators Sebastian Hesselbarh
2012-05-13 12:29 ` Mark Brown
2012-05-13 16:30 ` Sebastian Hesselbarh
2012-05-13 16:43 ` Mark Brown
2012-05-13 17:11 ` Sebastian Hesselbarh
2012-05-13 17:16 ` Mark Brown
2012-05-14 18:08 ` Turquette, Mike
2012-05-14 18:12 ` Mark Brown
2012-10-11 8:34 ` Daniel Mack
2012-10-11 16:00 ` Sebastian Hesselbarth [this message]
2012-10-12 18:17 ` Daniel Mack
2012-10-14 10:59 ` Sebastian Hesselbarth
2012-10-14 11:13 ` Daniel Mack
2012-10-14 16:16 ` Sebastian Hesselbarth
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=5076ED22.3060803@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@ti.com \
--cc=sebastian.hesselbarth@googlemail.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;
as well as URLs for NNTP newsgroup(s).