From: Eduardo Valentin <eduardo.valentin@ti.com>
To: t-kristo@ti.com
Cc: linux-omap@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
Paul Walmsley <paul@pwsan.com>,
mturquette@linaro.org, "Shilimkar,
Santosh" <santosh.shilimkar@ti.com>,
"Nayak, Rajendra" <rnayak@ti.com>
Subject: Re: OMAP CLK / CM data move to /drivers/clk
Date: Wed, 27 Feb 2013 07:00:10 -0400 [thread overview]
Message-ID: <512DE73A.3020601@ti.com> (raw)
In-Reply-To: <1361954659.8362.70.camel@sokoban>
On 27-02-2013 04:44, Tero Kristo wrote:
> Hi Paul and Mike,
>
> It looks like we need to start putting more effort into this clock data
> move now, as this is starting to hinder us on several fronts.
> Unfortunately I still can't personally participate in this work myself
> as I am now allocated to some hwmod related work, but Eduardo should
> have plenty of time to help with this...
hehe.. That's a bit stretching, but yes, I can help with this move :-)
>
> Anyway, Paul, I think you have been working a bit with this topic, what
> is the latest status with this? Do you see any areas Eduardo can help
> with? If you have some partially finished work also which you don't have
> time yourself, we can even take a look at that.
Paul,
Couple of initial questions. Would we move also the existing CM / PRM
code? Is there any cross dependency with SCM?
Paul, would be you who would be queuing these changes?
>
> Also, I would like to receive some initial comments about the approach
> we should take, and I added Mike here for this as you are the maintainer
> for the /drivers/clk. I believe we should start by moving the clock data
> under /drivers/clk/omap, and potentially move also some other stuff
> here, like CM code, clockdomain code and clockdomain data even. Do you
> have any opinions on this?
>
> -Tero
>
>
>
>
next prev parent reply other threads:[~2013-02-27 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 8:44 OMAP CLK / CM data move to /drivers/clk Tero Kristo
2013-02-27 11:00 ` Eduardo Valentin [this message]
2013-02-27 18:43 ` Mike Turquette
2013-02-28 13:48 ` Eduardo Valentin
2013-03-04 16:01 ` Paul Walmsley
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=512DE73A.3020601@ti.com \
--to=eduardo.valentin@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=santosh.shilimkar@ti.com \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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