linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Haijun Zhang <Haijun.Zhang@freescale.com>
Cc: linux-mmc@vger.kernel.org, AFLEMING@freescale.com,
	cbouatmailru@gmail.com, cjb@laptop.org,
	linuxppc-dev@lists.ozlabs.org,
	Haijun Zhang <haijun.zhang@freescale.com>
Subject: Re: [PATCH 4/4 V2] mmc: esdhc: Add broken timeout quirk for p4/p5 board
Date: Wed, 17 Jul 2013 12:13:49 -0500	[thread overview]
Message-ID: <1374081229.8183.361@snotra> (raw)
In-Reply-To: <1374055891-20703-3-git-send-email-Haijun.Zhang@freescale.com> (from Haijun.Zhang@freescale.com on Wed Jul 17 05:11:31 2013)

On 07/17/2013 05:11:31 AM, Haijun Zhang wrote:
> Sometimes command can't be completed within the time give
> in eSDHC_SYSCTL[DTOCV]. So just give the max value 0x14 to
> avoid this issue.
>=20
> Signed-off-by: Haijun Zhang <haijun.zhang@freescale.com>
> ---
> changes for v2:
> 	- Rebuild patch of eSDHC host need long time to generate
> 	 command interrupt
>=20
>  drivers/mmc/host/sdhci-of-esdhc.c | 6 ++++++
>  1 file changed, 6 insertions(+)
>=20
> diff --git a/drivers/mmc/host/sdhci-of-esdhc.c =20
> b/drivers/mmc/host/sdhci-of-esdhc.c
> index 570bca8..30bfb5c 100644
> --- a/drivers/mmc/host/sdhci-of-esdhc.c
> +++ b/drivers/mmc/host/sdhci-of-esdhc.c
> @@ -325,6 +325,12 @@ static void esdhc_of_platform_init(struct =20
> sdhci_host *host)
>=20
>  	if (vvn > VENDOR_V_22)
>  		host->quirks &=3D ~SDHCI_QUIRK_NO_BUSY_IRQ;
> +
> +	if ((SVR_SOC_VER(svr) =3D=3D SVR_B4860) ||
> +		(SVR_SOC_VER(svr) =3D=3D SVR_P5020) ||
> +		(SVR_SOC_VER(svr) =3D=3D SVR_P5040) ||
> +		(SVR_SOC_VER(svr) =3D=3D SVR_P4080))
> +		host->quirks |=3D SDHCI_QUIRK_BROKEN_TIMEOUT_VAL;
>  }

Please don't line up the continuation lines of the if-condition with =20
the if-body.

Please check variant SoCs as well.  If the bug exists on p4080, then it =20
exists on p4040.  Likewise with p5040/p5021, and p5020/p5010.

Is it present on all revisions of these SoCs?  How about p3041, which =20
is usually pretty similar to p5020?  p2040/p2041?  Is there an erratum =20
number for this problem?

-Scott=

  reply	other threads:[~2013-07-17 17:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-17 10:11 [PATCH 2/4 V2] mmc: esdhc: workaround for dma err in the last system transaction Haijun Zhang
2013-07-17 10:11 ` [PATCH 3/4 V2] mmc: esdhc: Correct host version of T4240-R1.0 Haijun Zhang
2013-07-17 17:11   ` Scott Wood
2013-07-18  2:30     ` Zang Roy-R61911
2013-07-18 15:24       ` Scott Wood
2013-07-22 14:30   ` Kumar Gala
2013-07-23  2:03     ` Zhang Haijun-B42677
2013-07-17 10:11 ` [PATCH 4/4 V2] mmc: esdhc: Add broken timeout quirk for p4/p5 board Haijun Zhang
2013-07-17 17:13   ` Scott Wood [this message]
2013-07-19  2:19     ` Zhang Haijun-B42677
2013-07-19 17:24       ` Scott Wood
2013-07-22  1:57         ` Zhang Haijun-B42677
2013-07-19  2:21 ` [PATCH 2/4 V2] mmc: esdhc: workaround for dma err in the last system transaction Zhang Haijun-B42677
2013-08-23  6:39   ` Zhang Haijun
2013-08-23 15:40     ` Scott Wood
2013-08-26  1:03       ` Zhang Haijun
2013-08-26  1:50         ` Zhang Haijun
2013-08-26 16:36         ` Scott Wood

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=1374081229.8183.361@snotra \
    --to=scottwood@freescale.com \
    --cc=AFLEMING@freescale.com \
    --cc=Haijun.Zhang@freescale.com \
    --cc=cbouatmailru@gmail.com \
    --cc=cjb@laptop.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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).