From: Huang Changming-R66093 <r66093@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Chris Ball <cjb@laptop.org>,
"linuxppc-dev@lists.ozlabs.org list"
<linuxppc-dev@lists.ozlabs.org>,
Anton Vorontsov <cbouatmailru@gmail.com>
Subject: RE: [PATCH 2/3] powerpc/esdhc: add property to disable the CMD23
Date: Thu, 13 Sep 2012 02:02:30 +0000 [thread overview]
Message-ID: <110EED8CC96DFC488B7E717A2027A27C1785D0@039-SN1MPN1-002.039d.mgd.msft.net> (raw)
In-Reply-To: <8B1F0805-759E-417A-B787-40DF197896F3@kernel.crashing.org>
> >
> >> -----Original Message-----
> >> From: Chris Ball [mailto:cjb@laptop.org]
> >> Sent: Wednesday, September 12, 2012 4:59 AM
> >> To: Kumar Gala
> >> Cc: Huang Changming-R66093; linuxppc-dev@lists.ozlabs.org list;
> >> linux- mmc@vger.kernel.org; Anton Vorontsov
> >> Subject: Re: [PATCH 2/3] powerpc/esdhc: add property to disable the
> >> CMD23
> >>
> >> Hi,
> >>
> >> On Tue, Sep 11 2012, Kumar Gala wrote:
> >>> thanks for the info. Do you know what's required on controller side
> >>> to handle cards that support CMD23?
> >>>
> >>> I'm trying to figure out if older controller's on FSL SoCs are
> >>> missing some feature to allow CMD23 to work (vs Auto-CMD23).
> >>
> >> It seems plausible that it's just not implemented on these controllers=
.
> >> It's a little strange, since the command's been specified for so long
> >> and we haven't seen any other controllers with problems. The patch
> >> would be correct if this is true.
> >>
> >
> > I didn't find any description about it, but after testing on FSL
> silicones, I got this result:
> > Some silicones support this command, and some silicones don't support
> it, which will cause I/O error.
>=20
> Can you list out which SoCs support it and which don't. Having this list
> will be useful in understanding which controller versions supported it.
>=20
P1020, p1021, p1022, p1024, p1015 and p4080 can't support it.
Mpc8536, p2020, and the other current DPAA silicon (e.g. p5020, p3041) supp=
ort it.
next prev parent reply other threads:[~2012-09-13 2:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1347347565-17474-1-git-send-email-Chang-Ming.Huang@freescale.com>
[not found] ` <1347347565-17474-2-git-send-email-Chang-Ming.Huang@freescale.com>
[not found] ` <20120911075429.GA27028@lizard>
2012-09-11 8:04 ` [PATCH 2/3] powerpc/esdhc: add property to disable the CMD23 Anton Vorontsov
2012-09-11 9:36 ` Huang Changming-R66093
2012-09-11 12:43 ` Kumar Gala
2012-09-11 12:49 ` Kumar Gala
2012-09-11 14:44 ` Chris Ball
2012-09-11 20:26 ` Kumar Gala
2012-09-11 20:59 ` Chris Ball
2012-09-12 6:18 ` Huang Changming-R66093
2012-09-12 12:13 ` Kumar Gala
2012-09-13 2:02 ` Huang Changming-R66093 [this message]
2012-09-13 12:47 ` Kumar Gala
2012-09-14 2:02 ` Huang Changming-R66093
2012-09-14 12:40 ` Kumar Gala
2012-09-17 12:36 ` Chris Ball
2012-09-17 13:12 ` Kumar Gala
2012-09-17 13:45 ` Chris Ball
2012-09-18 1:09 ` Huang Changming-R66093
2012-09-18 5:00 ` Kumar Gala
2012-09-18 5:07 ` Chris Ball
2012-09-11 18:28 ` Scott Wood
2012-09-12 3:19 ` Huang Changming-R66093
2012-09-12 3:38 ` Anton Vorontsov
2012-09-13 7:57 ` Huang Changming-R66093
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=110EED8CC96DFC488B7E717A2027A27C1785D0@039-SN1MPN1-002.039d.mgd.msft.net \
--to=r66093@freescale.com \
--cc=cbouatmailru@gmail.com \
--cc=cjb@laptop.org \
--cc=galak@kernel.crashing.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).