From: Tony Lindgren <tony@atomide.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
linux-mmc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-omap@vger.kernel.org,
Kishon Vijay Abraham I <kishon@ti.com>
Subject: Re: All OMAP platforms: MMC is broken
Date: Thu, 24 Sep 2015 18:13:34 -0700 [thread overview]
Message-ID: <20150925011334.GP23801@atomide.com> (raw)
In-Reply-To: <20150924233756.GN23801@atomide.com>
* Tony Lindgren <tony@atomide.com> [150924 16:42]:
> * Russell King - ARM Linux <linux@arm.linux.org.uk> [150924 02:04]:
> > Nightly testing has revealed that both the OMAP3430 LDP and the OMAP4430
> > SDP fail to boot due to lack of working MMC. Both platforms fail to
> > find their rootfs, which is on a SD card.
> >
> > The breakage occurred somewhere between trees of September 9th (commit
> > 4e4adb2f4628) and September 12th (commit b0a1ea51bda4), so during the
> > merge window.
>
> Yes sorry things got messed up in multiple ways :( I've summarized
> the mess here earlier:
>
> http://article.gmane.org/gmane.linux.kernel.mmc/33911
>
> And today commit b9c93646fd5c ("regulator: pbias: program pbias register
> offset in pbias driver") hit mainline so I'll send a pull request for
> the related dts change.
Kishon, while testing I noticed there are still at least two
issues remaining that seem to need fixing in the MMC driver:
1. The legacy booting without device tree does not probe MMC at
all on omap3
2. I'm getting the regulator warning on omap4 duovero
Anyways, I'm sending a pull request for the fixes so far as that
gets MMC working again for most platforms.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: All OMAP platforms: MMC is broken
Date: Thu, 24 Sep 2015 18:13:34 -0700 [thread overview]
Message-ID: <20150925011334.GP23801@atomide.com> (raw)
In-Reply-To: <20150924233756.GN23801@atomide.com>
* Tony Lindgren <tony@atomide.com> [150924 16:42]:
> * Russell King - ARM Linux <linux@arm.linux.org.uk> [150924 02:04]:
> > Nightly testing has revealed that both the OMAP3430 LDP and the OMAP4430
> > SDP fail to boot due to lack of working MMC. Both platforms fail to
> > find their rootfs, which is on a SD card.
> >
> > The breakage occurred somewhere between trees of September 9th (commit
> > 4e4adb2f4628) and September 12th (commit b0a1ea51bda4), so during the
> > merge window.
>
> Yes sorry things got messed up in multiple ways :( I've summarized
> the mess here earlier:
>
> http://article.gmane.org/gmane.linux.kernel.mmc/33911
>
> And today commit b9c93646fd5c ("regulator: pbias: program pbias register
> offset in pbias driver") hit mainline so I'll send a pull request for
> the related dts change.
Kishon, while testing I noticed there are still at least two
issues remaining that seem to need fixing in the MMC driver:
1. The legacy booting without device tree does not probe MMC at
all on omap3
2. I'm getting the regulator warning on omap4 duovero
Anyways, I'm sending a pull request for the fixes so far as that
gets MMC working again for most platforms.
Regards,
Tony
next prev parent reply other threads:[~2015-09-25 1:13 UTC|newest]
Thread overview: 70+ 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 9:00 ` Russell King - ARM Linux
2015-09-24 22:51 ` Grygorii Strashko
2015-09-24 22:51 ` Grygorii Strashko
2015-09-24 22:53 ` Russell King - ARM Linux
2015-09-24 22:53 ` Russell King - ARM Linux
2015-09-24 23:37 ` Tony Lindgren
2015-09-24 23:37 ` Tony Lindgren
2015-09-25 1:13 ` Tony Lindgren [this message]
2015-09-25 1:13 ` Tony Lindgren
2015-09-26 2:54 ` Nishanth Menon
2015-09-26 2:54 ` Nishanth Menon
2015-10-01 9:33 ` Russell King - ARM Linux
2015-10-01 9:33 ` Russell King - ARM Linux
2015-10-01 9:50 ` Ulf Hansson
2015-10-01 9:50 ` Ulf Hansson
2015-10-01 10:03 ` Russell King - ARM Linux
2015-10-01 10:03 ` Russell King - ARM Linux
2015-10-05 11:23 ` Tony Lindgren
2015-10-05 11:23 ` Tony Lindgren
2015-10-05 14:35 ` Tony Lindgren
2015-10-05 14:35 ` Tony Lindgren
2015-10-05 14:51 ` Tony Lindgren
2015-10-05 14:51 ` Tony Lindgren
2015-10-05 17:11 ` Tony Lindgren
2015-10-05 17:11 ` Tony Lindgren
2015-10-05 18:38 ` Russell King - ARM Linux
2015-10-05 18:38 ` Russell King - ARM Linux
2015-10-06 9:00 ` Russell King - ARM Linux
2015-10-06 9:00 ` Russell King - ARM Linux
2015-10-06 9:44 ` Tony Lindgren
2015-10-06 9:44 ` Tony Lindgren
2015-10-06 10:11 ` Ulf Hansson
2015-10-06 10:11 ` Ulf Hansson
2015-10-06 10:36 ` Kishon Vijay Abraham I
2015-10-06 10:36 ` Kishon Vijay Abraham I
2015-10-06 15:07 ` Russell King - ARM Linux
2015-10-06 15:07 ` Russell King - ARM Linux
2015-10-06 19:29 ` Kishon Vijay Abraham I
2015-10-06 19:29 ` Kishon Vijay Abraham I
2015-10-06 19:57 ` Russell King - ARM Linux
2015-10-06 19:57 ` Russell King - ARM Linux
2015-10-08 0:46 ` Kishon Vijay Abraham I
2015-10-08 0:46 ` Kishon Vijay Abraham I
2015-10-06 15:00 ` Russell King - ARM Linux
2015-10-06 15:00 ` Russell King - ARM Linux
2015-10-06 15:37 ` Tony Lindgren
2015-10-06 15:37 ` Tony Lindgren
2015-10-07 12:45 ` Russell King - ARM Linux
2015-10-07 12:45 ` Russell King - ARM Linux
2015-10-07 13:26 ` Tony Lindgren
2015-10-07 13:26 ` Tony Lindgren
2015-10-07 13:41 ` Ulf Hansson
2015-10-07 13:41 ` Ulf Hansson
2015-10-07 15:52 ` Tony Lindgren
2015-10-07 15:52 ` Tony Lindgren
2015-10-07 19:40 ` Ulf Hansson
2015-10-07 19:40 ` Ulf Hansson
2015-10-07 23:13 ` Kishon Vijay Abraham I
2015-10-07 23:13 ` Kishon Vijay Abraham I
2015-10-08 8:40 ` Tony Lindgren
2015-10-08 8:40 ` Tony Lindgren
2015-10-08 9:35 ` Russell King - ARM Linux
2015-10-08 9:35 ` Russell King - ARM Linux
2015-10-08 9:56 ` Tony Lindgren
2015-10-08 9:56 ` Tony Lindgren
2015-10-08 10:00 ` Russell King - ARM Linux
2015-10-08 10:00 ` Russell King - ARM Linux
2015-10-07 17:53 ` 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=20150925011334.GP23801@atomide.com \
--to=tony@atomide.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=ulf.hansson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.