public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH-V2 0/4] ARM: OMAP2+: am33xx: Add clocktree and hwmod data
Date: Tue, 5 Jun 2012 00:59:52 -0700	[thread overview]
Message-ID: <20120605075952.GJ12766@atomide.com> (raw)
In-Reply-To: <1338285402-11306-1-git-send-email-hvaibhav@ti.com>

* 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.

Regards,

Tony

  parent reply	other threads:[~2012-06-05  7:59 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 ` Tony Lindgren [this message]
2012-06-05  8:23   ` [PATCH-V2 0/4] ARM: OMAP2+: am33xx: Add clocktree and hwmod data Hiremath, Vaibhav
2012-06-05  8:26     ` Tony Lindgren
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=20120605075952.GJ12766@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.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