From: Fabio Estevam <festevam@gmail.com>
To: Angus Ainslie <angus@akkea.ca>
Cc: "Ulf Hansson" <ulf.hansson@linaro.org>,
"Guido Günther" <agx@sigxcpu.org>,
linux-mmc <linux-mmc@vger.kernel.org>,
"Adrian Hunter" <adrian.hunter@intel.com>,
"BOUGH CHEN" <haibo.chen@nxp.com>,
dl-linux-imx <linux-imx@nxp.com>,
"Sascha Hauer" <kernel@pengutronix.de>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: sdhci timeout on imx8mq
Date: Tue, 7 Jul 2020 09:44:45 -0300 [thread overview]
Message-ID: <CAOMZO5BarV1=6rx9L_hkJJLUQSicwPNUO4HFKWAXSQ6n0N+Kzg@mail.gmail.com> (raw)
In-Reply-To: <5ad361195f2e191484c8a231be0f5a07@akkea.ca>
Hi Angus,
On Tue, Jun 30, 2020 at 4:39 PM Angus Ainslie <angus@akkea.ca> wrote:
> Has there been any progress with this. I'm getting this on about 50% of
Not from my side, sorry.
Bough,
Do you know why this problem affects the imx8mq-evk versions that are
populated with the Micron eMMC and not the ones with Sandisk eMMC?
Thanks
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-07-07 12:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 19:19 sdhci timeout on imx8mq Fabio Estevam
2020-02-05 9:26 ` Guido Günther
2020-02-05 13:18 ` Fabio Estevam
2020-02-07 2:11 ` BOUGH CHEN
[not found] ` <VI1PR04MB504091C7991353F6092A8D91901A0@VI1PR04MB5040.eurprd04.prod.outlook.com>
2020-02-13 10:53 ` Fabio Estevam
2020-06-30 19:39 ` Angus Ainslie
2020-07-07 12:44 ` Fabio Estevam [this message]
2020-07-08 1:32 ` BOUGH CHEN
2020-12-18 20:07 ` Lucas Stach
2020-12-18 20:45 ` Angus Ainslie
2020-12-23 21:06 ` Angus Ainslie
2021-01-05 15:06 ` Lucas Stach
2021-01-06 9:29 ` Bough Chen
2021-01-06 15:09 ` Lucas Stach
2021-01-07 1:47 ` Bough Chen
2021-01-06 18:56 ` Fabio Estevam
2021-01-07 1:30 ` Jacky Bai
2021-01-07 11:26 ` Lucas Stach
2021-01-08 1:27 ` Jacky Bai
2021-03-09 7:35 ` Heiko Thiery
2021-01-19 2:35 ` Peng Fan
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='CAOMZO5BarV1=6rx9L_hkJJLUQSicwPNUO4HFKWAXSQ6n0N+Kzg@mail.gmail.com' \
--to=festevam@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=agx@sigxcpu.org \
--cc=angus@akkea.ca \
--cc=haibo.chen@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-mmc@vger.kernel.org \
--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 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).