From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: All OMAP platforms: MMC is broken
Date: Wed, 7 Oct 2015 13:45:51 +0100 [thread overview]
Message-ID: <20151007124551.GI21626@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20151006153710.GS23801@atomide.com>
On Tue, Oct 06, 2015 at 08:37:11AM -0700, Tony Lindgren wrote:
> * Russell King - ARM Linux <linux@arm.linux.org.uk> [151006 08:04]:
> > On Tue, Oct 06, 2015 at 02:44:25AM -0700, Tony Lindgren wrote:
> > >
> > > Hmm DT-based boot finds the MMC card for LDP, dmesg below from DT boot [1].
> > > Looks like you're on on -rc4 and not -rc3. My guess is that MMC is not
> > > working for you with DT-based booting because you don't seem to have
> > > CONFIG_REGULATOR_PBIAS in your seed config for. Care to try enabling that
> > > for both your omap3 and omap4 seed config files?
> >
> > This is precisely the kind of crap I'm objecting to. New kernel versions
> > come along, and things break because people add extra Kconfig symbols that
> > previous versions did not rely upon - and there's no communication of
> > what's required for new kernel versions.
> >
> > This stuff needs documenting, so that people are aware what changes they
> > need to make - please put something in Documentation/arm/OMAP which
> > tracks what new additions are required to the Kconfig to keep things
> > working.
>
> Good idea, how about something like the following? AFAIK that's the
> only .config option needed as MFD_SYSCON is selected by Kconfig
> already.
Right, that resolves the issue. Now, what's the story on the revert
and the other patch - have they already been taken for -rc kernels?
--
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-10-07 12:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 9:00 All OMAP platforms: MMC is broken Russell King - ARM Linux
2015-09-24 22:51 ` Grygorii Strashko
2015-09-24 22:53 ` Russell King - ARM Linux
2015-09-24 23:37 ` Tony Lindgren
2015-09-25 1:13 ` Tony Lindgren
2015-09-26 2:54 ` Nishanth Menon
2015-10-01 9:33 ` Russell King - ARM Linux
2015-10-01 9:50 ` Ulf Hansson
2015-10-01 10:03 ` Russell King - ARM Linux
2015-10-05 11:23 ` Tony Lindgren
2015-10-05 14:35 ` Tony Lindgren
2015-10-05 14:51 ` Tony Lindgren
2015-10-05 17:11 ` Tony Lindgren
2015-10-05 18:38 ` Russell King - ARM Linux
2015-10-06 9:00 ` Russell King - ARM Linux
2015-10-06 9:44 ` Tony Lindgren
2015-10-06 10:11 ` Ulf Hansson
2015-10-06 10:36 ` Kishon Vijay Abraham I
2015-10-06 15:07 ` Russell King - ARM Linux
2015-10-06 19:29 ` Kishon Vijay Abraham I
2015-10-06 19:57 ` Russell King - ARM Linux
2015-10-08 0:46 ` Kishon Vijay Abraham I
2015-10-06 15:00 ` Russell King - ARM Linux
2015-10-06 15:37 ` Tony Lindgren
2015-10-07 12:45 ` Russell King - ARM Linux [this message]
2015-10-07 13:26 ` Tony Lindgren
2015-10-07 13:41 ` Ulf Hansson
2015-10-07 15:52 ` Tony Lindgren
2015-10-07 19:40 ` Ulf Hansson
2015-10-07 23:13 ` Kishon Vijay Abraham I
2015-10-08 8:40 ` Tony Lindgren
2015-10-08 9:35 ` Russell King - ARM Linux
2015-10-08 9:56 ` Tony Lindgren
2015-10-08 10:00 ` Russell King - ARM Linux
2015-10-07 17:53 ` Russell King - ARM Linux
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=20151007124551.GI21626@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).