Hi Sergei
> > + if (card->host->caps2 & MMC_CAP2_2BLKS_LIMIT) {
> > + /*
> > +* In some controllers, when performing a
> > +* multiple block read of one or two blocks,
> > +
On 05/30/2014 02:40 PM, Kuninori Morimoto wrote:
From: Kuninori Morimoto
In some controllers, when performing a multiple block read of
You've typoed in the subject: "lultiple".
one or two blocks, depending on the timing with which the
response register is read, the response value may
On Fri, May 30, 2014 at 08:00:17PM +0900, Jaehoon Chung wrote:
> Hi, Kuninori.
>
> Subject has the typo. lultiple -> multiple?
> I didn't know why you need this patch. Would you use the
> MMC_CAP2_NO_MULTI_READ?
> And I think...it's not good that used the card's capability flags to fix your
> H/
Hi Jaehoon
> Subject has the typo. lultiple -> multiple?
grr..
> I didn't know why you need this patch. Would you use the
> MMC_CAP2_NO_MULTI_READ?
> And I think...it's not good that used the card's capability flags to fix your
> H/W bug.
Actually, current platform is using MMC_CAP2_NO_MULTI
Hi, Kuninori.
Subject has the typo. lultiple -> multiple?
I didn't know why you need this patch. Would you use the MMC_CAP2_NO_MULTI_READ?
And I think...it's not good that used the card's capability flags to fix your
H/W bug.
Best Regards,
Jaehoon Chung
On 05/30/2014 07:40 PM, Kuninori Morimoto
From: Kuninori Morimoto
In some controllers, when performing a multiple block read of
one or two blocks, depending on the timing with which the
response register is read, the response value may not
be read properly.
Use single block read for this HW bug
Signed-off-by: Kuninori Morimoto
---
dri
