From: Fabio Estevam <festevam@gmail.com>
To: Bough Chen <haibo.chen@nxp.com>
Cc: linux-mmc <linux-mmc@vger.kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
dl-linux-imx <linux-imx@nxp.com>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Martin Fuzzey <martin.fuzzey@flowbird.group>
Subject: Re: imx7d: Timeout waiting for hardware interrupt.
Date: Thu, 26 May 2022 16:07:28 -0300 [thread overview]
Message-ID: <CAOMZO5Dmk_OWTZGEafTZO451Zo6W8UMUJAZguW85y0b2BmCpWA@mail.gmail.com> (raw)
In-Reply-To: <VI1PR04MB40163FEB8AEC32F55E51931890D69@VI1PR04MB4016.eurprd04.prod.outlook.com>
Hi Bough,
On Wed, May 25, 2022 at 7:21 AM Bough Chen <haibo.chen@nxp.com> wrote:
> Hi Fabio,
>
> According to the log, ADMA Err: 0x00000007, seems meet ADMA length miss match issue, please double check whether the following patch is on your side:
> commit e30be063d6dbcc0f18b1eb25fa709fdef89201fb mmc: sdhci-esdhc-imx: correct the fix of ERR004536
>
> also please add the following patch for suspend/resume case
> commit a26a4f1baca55a05aecd8d7181802979a93e3d46 mmc: sdhci-esdhci-imx: retune needed for Mega/Mix enabled SoCs
Both commits are present in 5.10 stable, thanks.
I am testing a devicetree change.
Thanks
next prev parent reply other threads:[~2022-05-26 19:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 13:31 imx7d: Timeout waiting for hardware interrupt Fabio Estevam
2022-05-25 10:21 ` Bough Chen
2022-05-26 19:07 ` Fabio Estevam [this message]
2022-10-18 12:29 ` Fabio Estevam
2022-10-18 17:20 ` Fabio Estevam
2022-10-19 10:48 ` Bough Chen
2022-10-19 13:10 ` Fabio Estevam
2022-10-19 14:26 ` Fabio Estevam
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=CAOMZO5Dmk_OWTZGEafTZO451Zo6W8UMUJAZguW85y0b2BmCpWA@mail.gmail.com \
--to=festevam@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=haibo.chen@nxp.com \
--cc=linux-imx@nxp.com \
--cc=linux-mmc@vger.kernel.org \
--cc=martin.fuzzey@flowbird.group \
--cc=sebastian.reichel@collabora.com \
/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.