public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] fsl_esdhc driver is broken with DM
Date: Sun, 1 Oct 2017 10:49:30 -0400	[thread overview]
Message-ID: <20171001144930.GG3503@bill-the-cat> (raw)
In-Reply-To: <CAOMZO5DSZFrARVj3u7rcQxMpt+aFjv--yaGR5Fwnh_J1xPRzQQ@mail.gmail.com>

On Sun, Oct 01, 2017 at 11:29:58AM -0300, Fabio Estevam wrote:
> On Sat, Sep 30, 2017 at 12:35 PM, Fabio Estevam <festevam@gmail.com> wrote:
> > Hi,
> >
> > I noticed that  fsl_esdhc is broken on 2017.09 for mx6slevk, when
> > CONFIG_DM_MMC is selected:
> >
> > U-Boot 2017.09 (Sep 30 2017 - 12:31:17 -0300)
> >
> > CPU:   Freescale i.MX6SL rev1.0 792 MHz (running at 396 MHz)
> > CPU:   Commercial temperature grade (0C to 95C) at 35C
> > Reset cause: WDOG
> > Model: Freescale i.MX6 SoloLite EVK Board
> > Board: MX6SLEVK
> > DRAM:  1 GiB
> > PMIC: PFUZE100! DEV_ID=0x10 REV_ID=0x11
> > MMC:
> > MMC Device 1 not found
> > *** Warning - No MMC card found, using default environment
> 
> Same regression is observed with mx7dsabresd board as well.

It's likely to be all i.MX :(

Have all of the changes gone in such that an i.MX platform with SPL can
be non-interactively booted via imx_usb?  Not having my iMX platforms in
automated testing means that I always end up not testing them nearly
often enough.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171001/e202112b/attachment.sig>

  reply	other threads:[~2017-10-01 14:49 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-30 15:35 [U-Boot] fsl_esdhc driver is broken with DM Fabio Estevam
2017-10-01 14:29 ` Fabio Estevam
2017-10-01 14:49   ` Tom Rini [this message]
2017-10-01 15:50     ` Fabio Estevam
2017-10-01 17:46       ` Łukasz Majewski
2017-10-01 19:13       ` Fabio Estevam
2017-10-02 10:23       ` Jagan Teki
2017-10-02 11:06         ` Fabio Estevam
2017-10-09 18:05           ` Jagan Teki
2017-10-10 11:48             ` Fabio Estevam
2017-10-11 10:17               ` Jagan Teki
2017-10-11 15:49                 ` Fabio Estevam
2017-10-11 16:06                   ` Jagan Teki
2017-10-11 16:09                     ` Fabio Estevam
2017-10-11 16:29                       ` Jagan Teki
2017-10-11 18:41                       ` Tom Rini
2017-10-13  8:16                         ` Lukasz Majewski
2017-10-13 13:33                           ` Fabio Estevam
2017-10-16 20:51                             ` Jagan Teki
2017-10-16 21:52                               ` Fabio Estevam
2017-10-19 21:52                                 ` Adam Ford
2017-10-19 22:44                                   ` Fabio Estevam
2017-10-20  2:18                                     ` Adam Ford
2017-10-20 11:41                                       ` Fabio Estevam
2017-10-24 22:38                               ` Jagan Teki

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=20171001144930.GG3503@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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