devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Fritz <chf.fritz@googlemail.com>
To: "Tony Lindgren" <tony@atomide.com>,
	"Javier Martinez Canillas" <martinez.javier@gmail.com>,
	"Liam Girdwood" <lrg@ti.com>, "Benoît Cousson" <b-cousson@ti.com>,
	"Tomi Valkeinen" <tomi.valkeinen@ti.com>,
	"Alessandro Zummo" <a.zummo@towertech.it>,
	"Peter Ujfalusi" <peter.ujfalusi@ti.com>,
	"Samuel Ortiz" <sameo@linux.intel.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	devicetree-discuss@lists.ozlabs.org,
	Daniel Mack <daniel@zonque.org>,
	"Hans J. Koch" <hjk@hansjkoch.de>
Subject: [BUG] omap: mfd/regulator: twl/core: init order
Date: Sat, 13 Apr 2013 20:27:39 +0200	[thread overview]
Message-ID: <1365877659.3812.110.camel@mars> (raw)

Hi

 while testing an omap3 board with device tree support I stumbled upon a
bug which is due to wrong initialization order of twl-core and
twl-regulator (I suppose): In the boot process they get loaded way too
late so that a lot of drivers before where configured wrong or just
refuse to load.

For example the real time clock driver: The RTC kicks in way before
twl_probe() and due to that it configures its register map wrong
(at this time twl_priv->twl_id isn't configured yet).

Another example is the omap display subsystem. It (DSS) fails loading
while trying to register some not yet existent regulators and because it
lacks EPROBE_DEFER.

USB and MMC is also not working and I'm suspicious of the same cause.

Any ideas?

 Thanks
  -- Christoph


             reply	other threads:[~2013-04-13 18:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-13 18:27 Christoph Fritz [this message]
2013-04-15 10:20 ` [BUG] omap: mfd/regulator: twl/core: init order Grygorii Strashko
2013-04-15 10:56   ` Christoph Fritz
2013-04-15 10:59     ` Grygorii Strashko
2013-04-15 16:25       ` Tony Lindgren
     [not found]         ` <20130415162541.GO10155-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2013-04-16  7:45           ` Peter Ujfalusi
2013-04-16  8:33             ` Grygorii Strashko
2013-04-16 17:54               ` Tony Lindgren

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=1365877659.3812.110.camel@mars \
    --to=chf.fritz@googlemail.com \
    --cc=a.zummo@towertech.it \
    --cc=b-cousson@ti.com \
    --cc=daniel@zonque.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=hjk@hansjkoch.de \
    --cc=linux-omap@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=martinez.javier@gmail.com \
    --cc=peter.ujfalusi@ti.com \
    --cc=sameo@linux.intel.com \
    --cc=tomi.valkeinen@ti.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).