From: Meenakshi Aggarwal <meenakshi.aggarwal@nxp.com>
To: Jun Nie <jun.nie@linaro.org>, Leif Lindholm <leif.lindholm@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Haojian Zhuang <haojian.zhuang@linaro.org>
Subject: Re: [PATCH 1/2] MMC : Recieve response was missing after CMD12
Date: Thu, 31 Aug 2017 14:14:31 +0000 [thread overview]
Message-ID: <VI1PR04MB1005C7F49F4CD5A25EACF6FA8E9D0@VI1PR04MB1005.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <38973291-6c06-ca22-e006-123b711c30ae@linaro.org>
Hi Leif and Jun,
Thanks for the review.
-----Original Message-----
From: Jun Nie [mailto:jun.nie@linaro.org]
Sent: Thursday, August 31, 2017 7:03 PM
To: Leif Lindholm <leif.lindholm@linaro.org>; Meenakshi Aggarwal <meenakshi.aggarwal@nxp.com>
Cc: edk2-devel@lists.01.org; Haojian Zhuang <haojian.zhuang@linaro.org>
Subject: Re: [edk2] [PATCH 1/2] MMC : Recieve response was missing after CMD12
On 2017年08月31日 19:22, Leif Lindholm wrote:
> On Wed, Aug 30, 2017 at 07:50:58PM +0530, Meenakshi Aggarwal wrote:
>> We are not recieving the response from memory card after sending CMD
>> 12. It was not resulting in any failure but we should recieve
>> response after sending a command.
Per spec, there is response data for CMD12. It is reasonable to read it.
Reviewed-by: Jun Nie <jun.nie@linaro.org>
next prev parent reply other threads:[~2017-08-31 14:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 14:20 [PATCH 1/2] MMC : Recieve response was missing after CMD12 Meenakshi Aggarwal
2017-08-30 14:20 ` [PATCH 2/2] SD : Updated CMD 6 implememtation Meenakshi Aggarwal
2017-08-31 6:06 ` Meenakshi Aggarwal
2017-08-31 12:06 ` Leif Lindholm
2017-08-31 14:43 ` Jun Nie
2017-09-01 9:32 ` Meenakshi Aggarwal
2017-09-04 8:37 ` Meenakshi Aggarwal
2017-08-31 6:05 ` [PATCH 1/2] MMC : Recieve response was missing after CMD12 Meenakshi Aggarwal
2017-08-31 11:22 ` Leif Lindholm
2017-08-31 13:33 ` Jun Nie
2017-08-31 14:14 ` Meenakshi Aggarwal [this message]
2017-09-01 10:45 ` Leif Lindholm
2017-09-01 10:46 ` Meenakshi Aggarwal
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-list 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=VI1PR04MB1005C7F49F4CD5A25EACF6FA8E9D0@VI1PR04MB1005.eurprd04.prod.outlook.com \
--to=devel@edk2.groups.io \
/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