linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: BOUGH CHEN <haibo.chen@nxp.com>
To: "Fabio Estevam" <festevam@gmail.com>, "Guido Günther" <agx@sigxcpu.org>
Cc: Ulf Hansson <ulf.hansson@linaro.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: Fri, 7 Feb 2020 02:11:51 +0000	[thread overview]
Message-ID: <VI1PR04MB5040A046E5D93265AE636B29901C0@VI1PR04MB5040.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <CAOMZO5AAzK0QprHpKHaFOANjspJKd_4YaoMqAoGYG4KftcyiYw@mail.gmail.com>


> -----Original Message-----
> From: Fabio Estevam <festevam@gmail.com>
> Sent: 2020年2月5日 21:18
> To: Guido Günther <agx@sigxcpu.org>
> Cc: Ulf Hansson <ulf.hansson@linaro.org>; Adrian Hunter
> <adrian.hunter@intel.com>; linux-mmc <linux-mmc@vger.kernel.org>;
> 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
> 
> Hi Guido,
> 
> On Wed, Feb 5, 2020 at 6:26 AM Guido Günther <agx@sigxcpu.org> wrote:
> 
> > I've seen the same occasionally on the librem 5 with older linux-next
> > as well. Do you have a good reproducer?
> 
> Yes, with linux-next I always get this timeout by just booting the kernel and
> waiting 1 or 2 minutes without any activity.

I will reserve some time next week to check this issue.

Bough Chen
> 
> Regards,
> 
> Fabio Estevam
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-02-07  2:12 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 [this message]
     [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
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=VI1PR04MB5040A046E5D93265AE636B29901C0@VI1PR04MB5040.eurprd04.prod.outlook.com \
    --to=haibo.chen@nxp.com \
    --cc=adrian.hunter@intel.com \
    --cc=agx@sigxcpu.org \
    --cc=festevam@gmail.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).