From: Nishanth Menon <nm@ti.com>
To: "J, KEERTHY" <j-keerthy@ti.com>
Cc: "Cousson, Benoit" <b-cousson@ti.com>,
"Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
cpufreq <cpufreq@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Shawn Guo <shawn.guo@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 1/2] cpufreq: cpufreq-cpu0: support for clock which are not in DT yet.
Date: Tue, 12 Mar 2013 10:51:08 -0500 [thread overview]
Message-ID: <20130312155108.GA22409@kahuna> (raw)
In-Reply-To: <DC88CAD03C0052499C1907B327FC63229BF816@DBDE01.ent.ti.com>
On 10:17-20130312, J, KEERTHY wrote:
> > OK. My intent is to remove omap-cpufreq.c. So, I guess I could do
> > something like the following (not tested yet), but would that be the
> > right approach?
>
> Similar attempt was done for am33xx_clks in this by Shawn:
>
> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg84157.html
Thanks on the same and all inputs folks. Based on the discussion, will give it
another shot to make the patch apply for all OMAPs - Since we are
gradually transitioning to DT, we should be able to gradually drop
features to being enabled only in DT supported boot. This will allow us
to remove redundant drivers from the kernel. I hope this sounds
reasonable to all.
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2013-03-12 15:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 23:05 [PATCH 0/2] cpufreq: cpufreq-cpu0: cleanups around DT usage Nishanth Menon
2013-03-11 23:05 ` [PATCH 1/2] cpufreq: cpufreq-cpu0: support for clock which are not in DT yet Nishanth Menon
2013-03-12 5:03 ` Santosh Shilimkar
2013-03-12 14:24 ` Benoit Cousson
2013-03-12 14:35 ` Nishanth Menon
2013-03-12 15:17 ` J, KEERTHY
2013-03-12 15:51 ` Nishanth Menon [this message]
2013-03-12 7:36 ` Shawn Guo
2013-03-11 23:05 ` [PATCH 2/2] cpufreq: cpufreq-cpu0: provide compatibility string for DT matchup Nishanth Menon
2013-03-12 5:07 ` Santosh Shilimkar
2013-03-12 14:28 ` Benoit Cousson
2013-03-12 14:35 ` Santosh Shilimkar
2013-03-12 14:43 ` Nishanth Menon
2013-03-12 15:31 ` Benoit Cousson
[not found] ` <1363043130-30270-3-git-send-email-nm-l0cyMroinI0@public.gmane.org>
2013-03-12 7:57 ` Shawn Guo
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=20130312155108.GA22409@kahuna \
--to=nm@ti.com \
--cc=b-cousson@ti.com \
--cc=cpufreq@vger.kernel.org \
--cc=j-keerthy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=santosh.shilimkar@ti.com \
--cc=shawn.guo@linaro.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).