From: Paul Thomas <pthomas8589@gmail.com>
To: Michal Simek <michal.simek@xilinx.com>
Cc: linux-mmc@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>,
Ulf Hansson <ulf.hansson@linaro.org>, git <git@xilinx.com>,
Manish Narani <manish.narani@xilinx.com>
Subject: Re: mmc: sdhci-of-arasan: Issue DLL reset explicitly
Date: Mon, 30 Nov 2020 09:23:43 -0500 [thread overview]
Message-ID: <CAD56B7ePLTSAbcc8RkMt3WxOEezRN_cTv9Cq1_YCRTDQ0VLtDQ@mail.gmail.com> (raw)
In-Reply-To: <9e5da13d-cb0d-3190-11d1-556d05178966@xilinx.com>
On Fri, Nov 27, 2020 at 2:12 AM Michal Simek <michal.simek@xilinx.com> wrote:
>
> Hi Paul, +Manish
>
> On 27. 11. 20 4:49, Paul Thomas wrote:
> > Hi Everyone,
> >
> > The recent commit d06d60d5 'mmc: sdhci-of-arasan: Issue DLL reset
> > explicitly' seems to break the eMMC on our zynqmp boards, we get
> > messages like this:
> > mmc0: error -110 whilst initialising MMC card
> > We're using the XCZU2EG-1SFVC784I parts [1]. I see that this is moving
> > the DLL reset out of ATF. So part of the issue might be that we're
> > using the 2019.1 ATF version.
> >
> > thanks,
> > Paul
> >
> > [1] Enclustra modules:
> > https://www.enclustra.com/en/products/system-on-chip-modules/mercury-xu5/
> >
>
> Can you please try any latest version if that fix your problem?
>
> Manish: Please take look at this issue and try to replicate it.
>
> Thanks,
> Michal
Manish pointed me at the firmware patch here:
https://lore.kernel.org/patchwork/patch/1338926/
This fixed the issue for me. Thanks everyone.
-Paul
prev parent reply other threads:[~2020-11-30 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 3:49 mmc: sdhci-of-arasan: Issue DLL reset explicitly Paul Thomas
2020-11-27 7:12 ` Michal Simek
2020-11-30 14:23 ` Paul Thomas [this message]
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=CAD56B7ePLTSAbcc8RkMt3WxOEezRN_cTv9Cq1_YCRTDQ0VLtDQ@mail.gmail.com \
--to=pthomas8589@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=git@xilinx.com \
--cc=linux-mmc@vger.kernel.org \
--cc=manish.narani@xilinx.com \
--cc=michal.simek@xilinx.com \
--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).