From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: Fscking OMAP
Date: Mon, 20 Apr 2015 10:20:34 -0700 [thread overview]
Message-ID: <20150420172034.GL18048@atomide.com> (raw)
In-Reply-To: <20150420171421.GY4027@n2100.arm.linux.org.uk>
* Russell King - ARM Linux <linux@arm.linux.org.uk> [150420 10:15]:
> On Mon, Apr 20, 2015 at 09:25:16AM -0700, Tony Lindgren wrote:
> > * Russell King - ARM Linux <linux@arm.linux.org.uk> [150420 08:50]:
> > > Guys,
> > >
> > > If you're going to introduce a dependency on some infrastructure which
> > > you absolutely require for booting, then _please_ ensure that the
> > > configuration system is updated such that pre-existing kernel
> > > configurations continue to work.
> > >
> > > Don't leave it such that the infrastructure ends up returning -ENOSYS,
> > > which then filters down into your SoC specific code, and aborts the
> > > initialisation of critical infrastructure, leaving you with a totally
> > > silent boot failure.
> > >
> > > In this case, it's the addition of syscon to OMAP internals,
> > > specifically in omap_control_init().
> > >
> > > This is explicitly targetted at OMAP people, who have wasted much of
> > > my day today investigating why their platforms no longer boot in DT
> > > mode.
> >
> > Ouch, yeah missing dependencies are a pain to debug.
> >
> > Looks like we get MFD_SYSCON selected with omap2plus_defconfig,
> > but that's not always the case like you pointed out.
> >
> > Does the patch below fix the issue for you?
>
> Yes, that fixes it, thanks.
OK let's get this merged immediately and then Tero can add some more
checks to the init code like you suggested with a follow-up patch.
Regards,
Tony
> > 8< -----------------------
> > From: Tony Lindgren <tony@atomide.com>
> > Date: Mon, 20 Apr 2015 09:23:25 -0700
> > Subject: [PATCH] ARM: OMAP2+: Fix booting with configs that don't have MFD_SYSCON
> >
> > With the recent changes omaps have developed a dependency to MFD_SYSCON.
> > This is used for system control module generic register area and some
> > clocks.
> >
> > We do have it selected in omap2plus_defconfig, but targeted config
> > files may not have it selected. Let's make sure it's selected like
> > few other ARM platforms are already doing.
> >
> > Reported-by: Russell King <rmk+kernel@arm.linux.org.uk>
> > Signed-off-by: Tony Lindgren <tony@atomide.com>
> >
> > --- a/arch/arm/mach-omap2/Kconfig
> > +++ b/arch/arm/mach-omap2/Kconfig
> > @@ -81,6 +81,7 @@ config ARCH_OMAP2PLUS
> > select GENERIC_IRQ_CHIP
> > select MACH_OMAP_GENERIC
> > select MEMORY
> > + select MFD_SYSCON
> > select OMAP_DM_TIMER
> > select OMAP_GPMC
> > select PINCTRL
>
> --
> FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
> according to speedtest.net.
prev parent reply other threads:[~2015-04-20 17:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 15:49 Fscking OMAP Russell King - ARM Linux
2015-04-20 16:04 ` Russell King - ARM Linux
2015-04-20 16:25 ` Tony Lindgren
2015-04-20 17:14 ` Russell King - ARM Linux
2015-04-20 17:20 ` Tony Lindgren [this message]
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=20150420172034.GL18048@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;
as well as URLs for NNTP newsgroup(s).