From: Rajendra Nayak <rnayak@ti.com>
To: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: paul@pwsan.com, tony@atomide.com, Rajendra Nayak <rnayak@ti.com>
Subject: [RFC 0/2] OMAP2+: Convert hwmod to do clock inits and reset when drivers initialize
Date: Mon, 29 Jul 2013 14:42:40 +0530 [thread overview]
Message-ID: <1375089162-30664-1-git-send-email-rnayak@ti.com> (raw)
hwmod framework today does a module enable/reset/idle for all hwmods registered
for a platform quite early at boot.
This has a few downsides like
-1- An early crash failing to enable/reset a device/module needs earlyprintk
for anyone to see the crash logs
-2- Puts a dependency to have all PM frameworks initialized and ready quite
early which inturn prevents some of these to be converted to be independent
drivers
This RFC is an attempt to remove some of these dependencies and do the
hwmod inits (which need other PM frameworks) and resets when the module
is first enabled.
For modules which never get enabled through the boot, there is late call
to do the inits and resets for rest of those modules.
I have been experimenting with some of these on my omap4 panda es and that
boots fine with these patches. If the approach looks fine I will continue
to work some more in this direction and get rid of the early timer need for
hwmod and other PM frameworks.
Rajendra Nayak (2):
ARM: OMAP2+: hwmod: Split _init() into _init_early() and _init_late()
ARM: OMAP2+: hwmod: Do the late part of init and setup/reset on first
enable
arch/arm/mach-omap2/omap_hwmod.c | 47 +++++++++++++++++++++++++++++++++-----
1 file changed, 41 insertions(+), 6 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-07-29 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 9:12 Rajendra Nayak [this message]
2013-07-29 9:12 ` [RFC 1/2] ARM: OMAP2+: hwmod: Split _init() into _init_early() and _init_late() Rajendra Nayak
2013-07-29 9:12 ` [RFC 2/2] ARM: OMAP2+: hwmod: Do the late part of init and setup/reset on first enable Rajendra Nayak
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=1375089162-30664-1-git-send-email-rnayak@ti.com \
--to=rnayak@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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;
as well as URLs for NNTP newsgroup(s).