From: Tony Lindgren <tony@atomide.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
linux-omap@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Olof Johansson <olof@lixom.net>
Subject: Re: arm-soc + rmk's tree boot failure on OMAP4430SDP
Date: Mon, 19 Mar 2012 12:21:09 -0700 [thread overview]
Message-ID: <20120319192108.GC9859@atomide.com> (raw)
In-Reply-To: <1332165550.2144.85.camel@deskari>
* Tomi Valkeinen <tomi.valkeinen@ti.com> [120319 07:01]:
> On Mon, 2012-03-19 at 15:02 +0200, Tomi Valkeinen wrote:
>
> > I'll see if I can make a single patch that fixes the issue. The patch
> > series I mentioned earlier does lots of things, but I think just moving
> > the driver registration out of the probe function should be enough to
> > avoid the problem.
>
> Here's a patch that fixes the issue for me. Tested on OMAP4 Blaze with
> omapdss both as module and built-in. I'll queue this up after testing it
> a bit more.
OK works for me too.
> This still leaves the issue of initialization order, but I think that's
> not a big issue at the moment. It doesn't happen in practice, as the
> current driver framework will probe the devices at driver registration
> time. I'll fix this for the next merge window.
Yes that's something that needs fixing.
Regards,
Tony
next prev parent reply other threads:[~2012-03-19 19:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 23:11 arm-soc + rmk's tree boot failure on OMAP4430SDP Russell King - ARM Linux
2012-03-17 0:47 ` Tony Lindgren
2012-03-17 21:15 ` Russell King - ARM Linux
2012-03-19 9:33 ` Tomi Valkeinen
2012-03-19 12:30 ` Russell King - ARM Linux
2012-03-19 12:41 ` Tomi Valkeinen
2012-03-19 12:59 ` Russell King - ARM Linux
2012-03-19 13:02 ` Tomi Valkeinen
2012-03-19 13:59 ` Tomi Valkeinen
2012-03-19 19:21 ` Tony Lindgren [this message]
2012-03-22 1:15 ` Russ Dill
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=20120319192108.GC9859@atomide.com \
--to=tony@atomide.com \
--cc=arnd@arndb.de \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=olof@lixom.net \
--cc=tomi.valkeinen@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;
as well as URLs for NNTP newsgroup(s).