From: Tom Rini <trini@konsulko.com>
To: Robert Marko <robert.marko@sartura.hr>
Cc: "Jaehoon Chung" <jh80.chung@samsung.com>,
"Stefan Roese" <sr@denx.de>,
peng.fan@nxp.com, stcarlso@linux.microsoft.com,
U-Boot-Denx <u-boot@lists.denx.de>,
"Pali Rohár" <pali@kernel.org>
Subject: Re: [PATCH] mmc: xenon_sdhci: remove wait_dat0 SDHCI OP
Date: Tue, 15 Mar 2022 08:22:55 -0400 [thread overview]
Message-ID: <20220315122255.GX9986@bill-the-cat> (raw)
In-Reply-To: <CA+HBbNEDWUN47RR2FAJWA-_pN7YCN2fPDL4v0+bFUxjEckSm0w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1600 bytes --]
On Tue, Mar 15, 2022 at 10:47:57AM +0100, Robert Marko wrote:
> On Mon, Mar 14, 2022 at 2:10 PM Tom Rini <trini@konsulko.com> wrote:
> >
> > On Mon, Mar 14, 2022 at 06:37:02PM +0900, Jaehoon Chung wrote:
> > > On 3/12/22 03:14, Robert Marko wrote:
> > > > Generic SDHCI driver received support for checking the busy status by
> > > > polling the DAT[0] level instead of waiting for the worst MMC switch time.
> > > >
> > > > Unfortunately, it appears that this does not work for Xenon controllers
> > > > despite being a part of the standard SDHCI registers and the Armada 3720
> > > > datasheet itself telling that BIT(20) is useful for detecting the DAT[0]
> > > > busy signal.
> > > >
> > > > I have tried increasing the timeout value, but I have newer managed to
> > > > catch DAT_LEVEL bits change from 0 at all.
> > > >
> > > > This issue appears to hit most if not all SoC-s supported by Xenon driver,
> > > > at least A3720, A8040 and CN9130 have non working eMMC currently.
> > > >
> > > > So, until a better solution is found drop the wait_dat0 OP for Xenon.
> > > > I was able to only test it on A3720, but it should work for others as well.
> > > >
> > > > Fixes: 40e6f52454fc ("drivers: mmc: Add wait_dat0 support for sdhci driver")
> > > > Signed-off-by: Robert Marko <robert.marko@sartura.hr>
> > >
> > > Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
> >
> > Since this is a regression fix, will this be in the PR with the imx fix
> > as well? Thanks!
>
> Hi Tom,
> Was this question directed at me or?
Sorry, to Jaehoon or Peng.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-03-15 12:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220311181417epcas1p4207a65f5b292a3ff7bb8e4c0092f0f18@epcas1p4.samsung.com>
2022-03-11 18:14 ` [PATCH] mmc: xenon_sdhci: remove wait_dat0 SDHCI OP Robert Marko
2022-03-11 18:52 ` Pali Rohár
2022-03-12 17:39 ` Marek Behún
2022-03-14 9:37 ` Jaehoon Chung
2022-03-14 13:10 ` Tom Rini
2022-03-15 9:47 ` Robert Marko
2022-03-15 12:22 ` Tom Rini [this message]
2022-03-16 7:48 ` Jaehoon Chung
2022-03-14 12:03 ` Stefan Roese
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=20220315122255.GX9986@bill-the-cat \
--to=trini@konsulko.com \
--cc=jh80.chung@samsung.com \
--cc=pali@kernel.org \
--cc=peng.fan@nxp.com \
--cc=robert.marko@sartura.hr \
--cc=sr@denx.de \
--cc=stcarlso@linux.microsoft.com \
--cc=u-boot@lists.denx.de \
/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