From: Tony Lindgren <tony@atomide.com>
To: "Hiremath, Vaibhav" <hvaibhav@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Hilman, Kevin" <khilman@ti.com>,
"paul@pwsan.com" <paul@pwsan.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH-V2 0/4] ARM: OMAP2+: am33xx: Add clocktree and hwmod data
Date: Tue, 5 Jun 2012 01:26:29 -0700 [thread overview]
Message-ID: <20120605082628.GM12766@atomide.com> (raw)
In-Reply-To: <79CD15C6BA57404B839C016229A409A83EA41629@DBDE01.ent.ti.com>
* Hiremath, Vaibhav <hvaibhav@ti.com> [120605 01:27]:
> On Tue, Jun 05, 2012 at 13:29:52, Tony Lindgren wrote:
> > * Vaibhav Hiremath <hvaibhav@ti.com> [120529 03:01]:
> > > This patch adds complete clockctree and hwmod data for the
> > > AM33XX family of devices.
> > >
> > > This patch-series is cleaned up further from Paul's cleanup
> > > activity on AM33xx clocktree, where all leaf nodes have been
> > > removed and now modules enable/disable is controlled only
> > > using hwmod framework interface.
> > >
> > > There are certain modules, like clkdiv32k, debugss, etc..., for
> > > which we still doesn't have hwmod_data present, so in order to
> > > disable these modules during boot time, we still have to maintain
> > > clk node for them. Comment has been added to highlight this, and
> > > in the future we will cleanup this.
> > > As far as, CLKDIV32K module, in reality is not module but still
> > > we have MODULEMODE to control it, so we may have to keep this node
> > > alone in the clocktree.
> >
> > Considering that we have the RFC patches available for common
> > clk fwk, we should probably avoid the extra churn and have this
> > use the common clk fwk instead. Of course that is assuming the
> > common clk fwk patches will be mergeable soonish.
> >
>
> Tony,
>
> I am not quite sure how much time it will take to merge common clock changes
> from Rajendra, since it is still in RFC stage and may take couple merge
> windows. I would recommend to merge clock-tree and hwmod patches atleast to
> the linux-next, so that it gets validated for some time and we atleast would
> be able to boot the BeagleBone (community board) from linux-next/master.
> People can start further development using this on BeagleBone platform.
>
> Based on common-clock migration activity on OMAP, we can certainly make
> decision on pushing it to Mainline (Linus's) tree. And also I will start
> basing AM33XX clocktree on Rajendra's patches, so that it will get merged at
> the same time.
OK that sounds fair to me. Let's see what Paul and Rajendra say, it's
really up to them to make the call. We need minimize the extra load for
Paul and Rajendra here as it's already a big effort.
Regards,
Tony
next prev parent reply other threads:[~2012-06-05 8:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 9:56 [PATCH-V2 0/4] ARM: OMAP2+: am33xx: Add clocktree and hwmod data Vaibhav Hiremath
2012-05-29 9:56 ` [PATCH-V2 1/4] ARM: OMAP2+: hwmod: Hook-up am33xx support in omap_hwmod framework Vaibhav Hiremath
2012-05-29 9:56 ` [PATCH-V2 2/4] ARM: OMAP3+: clock: Move common clksel_rate & clock data to common file Vaibhav Hiremath
2012-06-28 15:51 ` Hiremath, Vaibhav
2012-05-29 9:56 ` [PATCH-V2 3/4] ARM: OMAP3+: clock33xx: Add AM33XX clock tree data Vaibhav Hiremath
2012-05-29 9:56 ` [PATCH-V2 4/4] ARM: OMAP3+: hwmod: Add AM33XX HWMOD data Vaibhav Hiremath
2012-07-17 19:59 ` Paul Walmsley
2012-07-18 9:46 ` Hiremath, Vaibhav
2012-07-18 9:54 ` Paul Walmsley
2012-06-05 7:59 ` [PATCH-V2 0/4] ARM: OMAP2+: am33xx: Add clocktree and hwmod data Tony Lindgren
2012-06-05 8:23 ` Hiremath, Vaibhav
2012-06-05 8:26 ` Tony Lindgren [this message]
2012-06-05 13:31 ` Rajendra Nayak
2012-06-05 8:31 ` Hiremath, Vaibhav
2012-06-14 15:12 ` Hiremath, Vaibhav
2012-06-18 18:06 ` Paul Walmsley
2012-06-18 18:18 ` Hiremath, Vaibhav
2012-06-18 18:28 ` Paul Walmsley
2012-06-18 18:46 ` Hiremath, Vaibhav
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=20120605082628.GM12766@atomide.com \
--to=tony@atomide.com \
--cc=hvaibhav@ti.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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).