Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Thara Gopinath <thara@ti.com>
Cc: linux-omap@vger.kernel.org, paul@pwsan.com, b-cousson@ti.com,
	vishwanath.bs@ti.com, sawant@ti.com, dderrick@ti.com
Subject: Re: [PATCHv2 1/8] OMAP: PM: Allowing an early init of pm debugfs driver.
Date: Tue, 24 Aug 2010 15:21:43 -0700	[thread overview]
Message-ID: <1282688503.11841.47.camel@localhost> (raw)
In-Reply-To: <87aaobmzby.fsf@deeprootsystems.com>

On Tue, 2010-08-24 at 15:16 -0700, Kevin Hilman wrote:
> Thara Gopinath <thara@ti.com> writes:
> 
> > This patch changes the pm_db_init from arch initcall to a postcore
> > initcall. With arch initcall, it is impossible for pm driver that
> > gets initialized prior to this driver to use one of the
> > pm debug fs entries during its init. Making it a postcore initcall
> > ensures that this drver gets initialized early on before any pm
> > drivers. 
> 
> Instead of tinkering with initcall ordering, how about calling the pm
> debug init from pm.c

ignore this comment, pm.c is a device_initcall, so wont solve your
problem.

But I'd still like to know what PM drivers are being initialized so
early they need this to be a postcore_initcall.

Kevin



  reply	other threads:[~2010-08-24 22:21 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-13 13:47 [PATCHv2 0/8] OMAP3: Adding Smartreflex and Voltage driver support Thara Gopinath
2010-08-13 13:47 ` [PATCHv2 1/8] OMAP: PM: Allowing an early init of pm debugfs driver Thara Gopinath
2010-08-24 22:16   ` Kevin Hilman
2010-08-24 22:21     ` Kevin Hilman [this message]
2010-09-14 14:56       ` Gopinath, Thara
2010-08-13 13:47 ` [PATCHv2 2/8] OMAP3: PM: Adding voltage driver support for OMAP3 Thara Gopinath
2010-08-25  0:01   ` Kevin Hilman
2010-09-14 15:32     ` Gopinath, Thara
2010-08-30 23:06   ` Kevin Hilman
2010-08-30 23:21   ` Kevin Hilman
2010-08-13 13:47 ` [PATCHv2 3/8] OMAP3: PM: Adding smartreflex driver support Thara Gopinath
2010-08-25 22:21   ` Kevin Hilman
2010-09-14 15:58     ` Gopinath, Thara
2010-09-14 17:04       ` Kevin Hilman
2010-08-13 13:47 ` [PATCHv2 4/8] OMAP3: PM: Adding smartreflex device file Thara Gopinath
2010-08-25 22:26   ` Kevin Hilman
2010-09-14 15:36     ` Gopinath, Thara
2010-09-14 16:03       ` Kevin Hilman
2010-09-15  6:12         ` Gopinath, Thara
2010-08-13 13:47 ` [PATCHv2 5/8] OMAP3: PM: Adding smartreflex hwmod data Thara Gopinath
2010-08-25 22:29   ` Kevin Hilman
2010-08-13 13:47 ` [PATCHv2 6/8] OMAP3: PM: Adding smartreflex class3 driver Thara Gopinath
2010-08-25 22:31   ` Kevin Hilman
2010-09-14 15:58     ` Gopinath, Thara
2010-08-13 13:47 ` [PATCHv2 7/8] OMAP3: PM: Adding T2 enabling of smartreflex support Thara Gopinath
2010-08-13 13:47 ` [PATCHv2 8/8] OMAP3: PM: Adding debug support to Voltage and Smartreflex drivers Thara Gopinath
2010-08-24 23:53   ` Kevin Hilman
2010-09-14 14:58     ` Gopinath, Thara
2010-09-14 16:05       ` Kevin Hilman

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=1282688503.11841.47.camel@localhost \
    --to=khilman@deeprootsystems.com \
    --cc=b-cousson@ti.com \
    --cc=dderrick@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=sawant@ti.com \
    --cc=thara@ti.com \
    --cc=vishwanath.bs@ti.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