[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8C92BC0B-B9F7-4D48-AD24-6096F92D6998@marvell.com>
Date: Thu, 24 Feb 2011 17:25:26 -0800
From: Philip Rakity <prakity@...vell.com>
To: Chris Ball <cjb@...top.org>
CC: "Dong, Chuanxiao" <chuanxiao.dong@...el.com>,
Jae hoon Chung <jh80.chung@...il.com>,
"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"arnd@...db.de" <arnd@...db.de>,
Kyungmin Park <kyungmin.park@...sung.com>
Subject: Re: [PATCH 1/1]mmc: set timeout for SDHCI host before sending busy
cmd
On Feb 24, 2011, at 12:15 PM, Chris Ball wrote:
> On Thu, Feb 24, 2011 at 10:32:30AM -0800, Philip Rakity wrote:
>> proposed this a while ago and strongly support just removing the quirk for broken timeout and setting the timeout value to maximum of 0xE.
>>
>> This also handles the case of the sd device having a timeout value too low. In my testing I have come across SD cards that do not provide the correct value.
>> We force our pxa168, pxa910, and mmp2 controllers to have 0xE.
>
> Yeah, OLPC's CaFe controller -- which might be the same hardware as yours,
> actually -- has the same problem.
different controller not same as on mmp2, pxa168, pxa910
>
> Does anyone know of a reason (beyond strict spec-compliance, I suppose)
> for honoring the timeout value rather than using 0xE everywhere? If not,
> I'm willing to try out Philip's suggestion.
>
> Thanks,
>
> --
> Chris Ball <cjb@...top.org> <http://printf.net/>
> One Laptop Per Child
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists