All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] mmc erase fails from U-Boot command line
Date: Wed, 2 Dec 2015 15:23:16 -0200	[thread overview]
Message-ID: <CAOMZO5Bw8fiOOsvD99Qwb-trcNcXN9ysEMy5AoUCFYKtg4tfnw@mail.gmail.com> (raw)
In-Reply-To: <565DEF80.90204@nelint.com>

Hi Eric,

On Tue, Dec 1, 2015 at 5:05 PM, Eric Nelson <eric@nelint.com> wrote:

> I've also recently seen this on two different custom boards. Both are
> running i.MX6Q TO1.2 and both are using eMMC from Micron.

One colleague of mine tested eMMC erasure on a mx6qsabresd revC5 board
with a eMMC from Micron and it worked fine.

So far I see:

revB and revC5: works
revC2 and revC4: don't work

>
> The code which is generating the error message:
>
>         http://git.denx.de/?p=u-boot.git;a=blob;f=drivers/mmc/fsl_esdhc.c;h=c5054d66bdcda029f0485958c87bd5154ccee591;hb=HEAD#l390
>
> Seems to refer to an errata for the i.MX35 (ENGcm03648):
>         http://cache.freescale.com/files/dsp/doc/errata/IMX35CE.pdf
>
> I don't see any reference to the errata in the i.MX6 docs.

This piece of code came from:
7a5b80297bc6cef ("mmc: fsl_esdhc: Poll until card is not busy anymore")

Yes, ENGcm03648 is not listed in mx6 errata document.

> Ignoring the error (removing the return statement) seems to leave things
> in a workable state, so I suspect the problem isn't with an insufficient
> timeout.

May I see your change, please?

Thanks,

Fabio Estevam

  reply	other threads:[~2015-12-02 17:23 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16 11:46 [U-Boot] mmc erase fails from U-Boot command line Cliff Brust
2015-10-19 11:06 ` Hector Palacios
2015-11-12 20:56   ` Fabio Estevam
2015-11-13 12:26     ` Palacios, Hector
2015-11-13 14:37       ` Fabio Estevam
2015-11-16 15:23         ` Fabio Estevam
2015-11-16 15:30           ` Fabio Estevam
2015-12-01 19:05             ` Eric Nelson
2015-12-02 17:23               ` Fabio Estevam [this message]
2015-12-02 18:47                 ` Eric Nelson
2015-12-02 18:52                   ` Fabio Estevam
2015-12-02 19:28                     ` Eric Nelson
2015-12-02 19:53                       ` Fabio Estevam
2015-12-04 16:35                         ` Eric Nelson
2015-12-04 16:37                           ` Fabio Estevam
2015-12-04 22:42                           ` Eric Nelson
2015-12-05  0:19                             ` Fabio Estevam
2015-12-07  0:21                             ` Fabio Estevam
2015-12-07 14:36                               ` Eric Nelson
2015-12-02 19:37                     ` Michael Trimarchi
2015-12-02 19:54                       ` Fabio Estevam
2015-12-02 20:00                         ` Michael Trimarchi
2015-12-04 16:08                           ` Eric Nelson
2015-12-04 16:50                             ` Eric Nelson
2015-12-04 17:06                               ` Michael Trimarchi
2015-12-07 14:50                               ` [U-Boot] [PATCH] mmc: update MMC_ERASE argument to match Linux kernel Eric Nelson
2015-12-09 10:55                                 ` Hector Palacios
2015-12-22  9:55                                   ` Fabio Estevam
2016-01-04 22:23                                 ` [U-Boot] " Tom Rini

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=CAOMZO5Bw8fiOOsvD99Qwb-trcNcXN9ysEMy5AoUCFYKtg4tfnw@mail.gmail.com \
    --to=festevam@gmail.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 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.