From: Tony Lindgren <tony@atomide.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Felipe Balbi <balbi@ti.com>, Luciano Coelho <coelho@ti.com>,
svenkatr@ti.com, linux-omap@vger.kernel.org,
linux-mmc@vger.kernel.org, cjb@laptop.org, lrg@ti.com,
linux-kernel@vger.kernel.org
Subject: Re: 32kHz clock removal causes problems omap_hsmmc
Date: Wed, 19 Dec 2012 08:28:11 -0800 [thread overview]
Message-ID: <20121219162811.GL4989@atomide.com> (raw)
In-Reply-To: <50D19463.5010605@ti.com>
* Peter Ujfalusi <peter.ujfalusi@ti.com> [121219 02:20]:
> On 12/19/2012 11:09 AM, Mark Brown wrote:
> > On Wed, Dec 19, 2012 at 11:00:32AM +0100, Peter Ujfalusi wrote:
> >
> >> I don't know the state of the common clock framework for OMAPs. Is it already
> >> up in 3.7? Or going for 3.8? 3.9? 3.10?...
> >> We need CCF to resolve this. I can cook up the clock driver for the 32k clock
> >> from twl, but in order to use it we need CCF on OMAP.
> >
> > Well, we at least ought to make sure it doesn't appear in the regulator
> > DT bindings even if it's handled via some OMAP magic - that was the key
> > point here.
>
> Sure. It must be a clock driver. I already have similar driver (for McPDM fclk
> clock) for twl6040.
> Let me check linux-next, if CCF is there for OMAP I can send the 32k clock
> driver soon (after writing it and testing it). It is going to be for 3.9 but
> we can roll it with us I think locally to resolv issues.
The omap common clock patches are now in mainline kernel as of v3.8
merge window.
Tony
next prev parent reply other threads:[~2012-12-19 16:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 8:31 32kHz clock removal causes problems omap_hsmmc Luciano Coelho
2012-12-18 9:54 ` Felipe Balbi
2012-12-19 9:45 ` Mark Brown
2012-12-19 10:00 ` Peter Ujfalusi
2012-12-19 10:09 ` Mark Brown
2012-12-19 10:18 ` Peter Ujfalusi
2012-12-19 10:32 ` Mark Brown
2012-12-19 10:45 ` Luciano Coelho
2012-12-19 10:56 ` Peter Ujfalusi
2012-12-19 11:00 ` Peter Ujfalusi
2012-12-19 11:02 ` Mark Brown
2012-12-19 11:07 ` Luciano Coelho
2012-12-19 13:01 ` Felipe Balbi
2012-12-19 13:51 ` Benoit Cousson
2012-12-19 13:54 ` Felipe Balbi
2012-12-19 13:58 ` Mark Brown
2012-12-19 13:58 ` Luciano Coelho
2012-12-19 14:04 ` Benoit Cousson
2012-12-19 18:06 ` R Sricharan
2012-12-19 14:31 ` Peter Ujfalusi
2012-12-19 16:28 ` Tony Lindgren [this message]
2012-12-19 10:01 ` Luciano Coelho
2012-12-19 10:28 ` Mark Brown
2012-12-19 10:42 ` Luciano Coelho
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=20121219162811.GL4989@atomide.com \
--to=tony@atomide.com \
--cc=balbi@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=cjb@laptop.org \
--cc=coelho@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=svenkatr@ti.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).