From: Scott Wood <scottwood@freescale.com>
To: Zhang Haijun <B42677@freescale.com>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"cbouatmailru@gmail.com" <cbouatmailru@gmail.com>,
"cjb@laptop.org" <cjb@laptop.org>,
Wood Scott-B07421 <B07421@freescale.com>,
Xie Xiaobo-R63061 <X.Xie@freescale.com>
Subject: Re: [PATCH 2/4 V2] mmc: esdhc: workaround for dma err in the last system transaction
Date: Mon, 26 Aug 2013 11:36:43 -0500 [thread overview]
Message-ID: <1377535003.3033.6.camel@snotra.buserror.net> (raw)
In-Reply-To: <521AA947.6080209@freescale.com>
On Mon, 2013-08-26 at 09:03 +0800, Zhang Haijun wrote:
> On 08/23/2013 11:40 PM, Scott Wood wrote:
>
> > On Fri, 2013-08-23 at 14:39 +0800, Zhang Haijun wrote:
> > > Hi, Anton and all
> > >
> > > Is there any advice on these two patches ?
> > >
> > > [PATCH 2/4 V2] mmc: esdhc: workaround for dma err in the last system
> > > transaction
> > > [PATCH 3/4 V3] mmc: esdhc: Correct host version of T4240-R1.0-R2.0.
> > >
> > >
> > > [PATCH 1/4 V4] powerpc/85xx: Add support for 85xx cpu type detection
> > > This patch is Act-by Scott.
> > > Patch 4/4 is split to four patches and Act-by Anton.
> > >
> > >
> > > Thanks all.
> > >
> > >
> > >
> > [snip]
> > > > > + if (!(((SVR_SOC_VER(svr) == SVR_T4240) && (SVR_REV(svr) == 0x10))
> > > > > ||
> > > > > + ((SVR_SOC_VER(svr) == SVR_B4860) && (SVR_REV(svr) == 0x10))
> > > > > ||
> > > > > + ((SVR_SOC_VER(svr) == SVR_P1010) && (SVR_REV(svr) == 0x10))
> > > > > ||
> > > > > + ((SVR_SOC_VER(svr) == SVR_P3041) && (SVR_REV(svr) <= 0x20))
> > > > > ||
> > > > > + ((SVR_SOC_VER(svr) == SVR_P2041) && (SVR_REV(svr) <= 0x20))
> > > > > ||
> > > > > + ((SVR_SOC_VER(svr) == SVR_P5040) && SVR_REV(svr) == 0x20)))
> > > > > + return;
> > You need to include variants here. If P5040 is affected, then P5021 is
> > affected. If P2041 is affected, then P2040 is affected, etc.
> >
> > -Scott
> >
> >
> Hi, Scott
>
> This workaround is for CR:ENGR00229586: A-005055, Configs Affected
> only list these soc and its version.
> I was also wonder why only these boards?
>
> But I can't add soc like P5021 as I think it should be. Maybe there
> are some difference between them.
The only difference between P5040 and P5021 is the number of cores
enabled. It is physically the same silicon. Likewise with a lot of
other variants.
-Scott
prev parent reply other threads:[~2013-08-26 16:36 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
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 [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=1377535003.3033.6.camel@snotra.buserror.net \
--to=scottwood@freescale.com \
--cc=B07421@freescale.com \
--cc=B42677@freescale.com \
--cc=X.Xie@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