From: Angus Ainslie <angus@akkea.ca>
To: Fabio Estevam <festevam@gmail.com>
Cc: "BOUGH CHEN" <haibo.chen@nxp.com>,
"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>,
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, 30 Jun 2020 12:39:18 -0700 [thread overview]
Message-ID: <5ad361195f2e191484c8a231be0f5a07@akkea.ca> (raw)
In-Reply-To: <CAOMZO5CkSSidzLUSBUvJNAio3SnmU-fisTbDCiLN9v1EjS+HHQ@mail.gmail.com>
Hi Fabio, Bough
On 2020-02-13 02:53, Fabio Estevam wrote:
> Hi Bough,
>
> On Wed, Feb 12, 2020 at 11:33 PM BOUGH CHEN <haibo.chen@nxp.com> wrote:
>
>> The board I use is SCH-29615 REV B4. This board use Sandisk eMMC
>> chip. Maybe your board use Micron eMMC.
>
> Mine is REV B3 with the Micron eMMC.
>
>> I attach the bootloader I use. Please try this bootloader on your
>> side.
>
> I hope we don't have a bootloader dependency here.
>
Has there been any progress with this. I'm getting this on about 50% of
boots with 5.7.5 in some configurations. I'm working on the USB
subsystem so nothing that should directly influence the sdhci code.
Our device tree setup for the usdhc is the same as the imx8mq-evk
https://source.puri.sm/Librem5/linux-next/-/blob/imx8-current-librem5/arch/arm64/boot/dts/freescale/imx8mq-librem5.dts#L836
Thanks
Angus
> Thanks
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Angus Ainslie <angus@akkea.ca>
To: Fabio Estevam <festevam@gmail.com>
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, 30 Jun 2020 12:39:18 -0700 [thread overview]
Message-ID: <5ad361195f2e191484c8a231be0f5a07@akkea.ca> (raw)
In-Reply-To: <CAOMZO5CkSSidzLUSBUvJNAio3SnmU-fisTbDCiLN9v1EjS+HHQ@mail.gmail.com>
Hi Fabio, Bough
On 2020-02-13 02:53, Fabio Estevam wrote:
> Hi Bough,
>
> On Wed, Feb 12, 2020 at 11:33 PM BOUGH CHEN <haibo.chen@nxp.com> wrote:
>
>> The board I use is SCH-29615 REV B4. This board use Sandisk eMMC
>> chip. Maybe your board use Micron eMMC.
>
> Mine is REV B3 with the Micron eMMC.
>
>> I attach the bootloader I use. Please try this bootloader on your
>> side.
>
> I hope we don't have a bootloader dependency here.
>
Has there been any progress with this. I'm getting this on about 50% of
boots with 5.7.5 in some configurations. I'm working on the USB
subsystem so nothing that should directly influence the sdhci code.
Our device tree setup for the usdhc is the same as the imx8mq-evk
https://source.puri.sm/Librem5/linux-next/-/blob/imx8-current-librem5/arch/arm64/boot/dts/freescale/imx8mq-librem5.dts#L836
Thanks
Angus
> Thanks
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
_______________________________________________
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-06-30 19:44 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 19:19 sdhci timeout on imx8mq Fabio Estevam
2020-02-03 19:19 ` Fabio Estevam
2020-02-05 9:26 ` Guido Günther
2020-02-05 9:26 ` Guido Günther
2020-02-05 13:18 ` Fabio Estevam
2020-02-05 13:18 ` Fabio Estevam
2020-02-07 2:11 ` BOUGH CHEN
2020-02-07 2:11 ` BOUGH CHEN
[not found] ` <VI1PR04MB504091C7991353F6092A8D91901A0@VI1PR04MB5040.eurprd04.prod.outlook.com>
2020-02-13 10:53 ` Fabio Estevam
2020-02-13 10:53 ` Fabio Estevam
2020-06-30 19:39 ` Angus Ainslie [this message]
2020-06-30 19:39 ` Angus Ainslie
2020-07-07 12:44 ` Fabio Estevam
2020-07-07 12:44 ` Fabio Estevam
2020-07-08 1:32 ` BOUGH CHEN
2020-07-08 1:32 ` BOUGH CHEN
2020-12-18 20:07 ` Lucas Stach
2020-12-18 20:07 ` Lucas Stach
2020-12-18 20:45 ` Angus Ainslie
2020-12-18 20:45 ` Angus Ainslie
2020-12-23 21:06 ` Angus Ainslie
2020-12-23 21:06 ` Angus Ainslie
2021-01-05 15:06 ` Lucas Stach
2021-01-05 15:06 ` Lucas Stach
2021-01-06 9:29 ` Bough Chen
2021-01-06 9:29 ` Bough Chen
2021-01-06 15:09 ` Lucas Stach
2021-01-06 15:09 ` Lucas Stach
2021-01-07 1:47 ` Bough Chen
2021-01-07 1:47 ` Bough Chen
2021-01-06 18:56 ` Fabio Estevam
2021-01-06 18:56 ` Fabio Estevam
2021-01-07 1:30 ` Jacky Bai
2021-01-07 1:30 ` Jacky Bai
2021-01-07 11:26 ` Lucas Stach
2021-01-07 11:26 ` Lucas Stach
2021-01-08 1:27 ` Jacky Bai
2021-01-08 1:27 ` Jacky Bai
2021-03-09 7:35 ` Heiko Thiery
2021-03-09 7:35 ` Heiko Thiery
2021-01-19 2:35 ` Peng Fan
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=5ad361195f2e191484c8a231be0f5a07@akkea.ca \
--to=angus@akkea.ca \
--cc=adrian.hunter@intel.com \
--cc=agx@sigxcpu.org \
--cc=festevam@gmail.com \
--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 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.