[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7BDF62B4-A11A-4CB4-9F80-F2206C2655F9@marvell.com>
Date: Wed, 26 Jan 2011 17:43:46 -0800
From: Philip Rakity <prakity@...vell.com>
To: Tomoya MORINAGA <tomoya-linux@....okisemi.com>
CC: Chris Ball <cjb@...top.org>, Kyungmin Park <kmpark@...radead.org>,
"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"andrew.chih.howe.khor@...el.com" <andrew.chih.howe.khor@...el.com>,
"kok.howg.ewe@...el.com" <kok.howg.ewe@...el.com>,
Toshiharu Okada <toshiharu-linux@....okisemi.com>
Subject: Re: A MMC card transfer issue
There is no good answer.
Doing this patch for 2.6.20 or so a long time ago had problems because some controllers did not work. The failures were equally unpleasant.
The failure you see today is at least not a regression since 1 bit did not work before.
We hope that developers who know their h/w works add the CAP.
On Jan 26, 2011, at 5:31 PM, Tomoya MORINAGA wrote:
> Hi Philip,
>
>> which MMC driver are you using.
> Could you teach me how to get the information ?
>
>> you need to have the driver or the low level code enable this QUIRK.
> BTW, Is the above permanent treatment?
> I think modifying kernel source code isn't preferred.
>
> Thanks,
> -----------------------------------------
> Tomoya MORINAGA
> OKI SEMICONDUCTOR CO., LTD.
>
>> -----Original Message-----
>> From: Philip Rakity [mailto:prakity@...vell.com]
>> Sent: Thursday, January 27, 2011 10:04 AM
>> To: Tomoya MORINAGA
>> Cc: Chris Ball; Kyungmin Park; linux-mmc@...r.kernel.org;
>> linux-kernel@...r.kernel.org;
>> andrew.chih.howe.khor@...el.com; kok.howg.ewe@...el.com
>> Subject: Re: A MMC card transfer issue
>>
>>
>> yes
>>
>> you need to have the driver or the low level code enable this QUIRK.
>>
>> which mmc driver are you using.
>>
>> On Jan 26, 2011, at 5:00 PM, Tomoya MORINAGA wrote:
>>
>>> Hi Philip,
>>>
>>> On Thursday, January 27, 2011 12:42 AM, Philip Rakity wrote:
>>>> Did you define the CAP for BUS WIDTH ?
>>>>
>>>> MMC_CAP_BUS_WIDTH_TEST
>>>>
>>>> in the driver or the platform driver ?
>>>
>>> Let me make the above meaning clear.
>>>
>>> I don't modify kernel source code "drivers/mmc" at all Is the above
>>> mean I must modify something kernel source code ?
>>>
>>> Thanks,
>>> -----------------------------------------
>>> Tomoya MORINAGA
>>> OKI SEMICONDUCTOR CO., LTD.
>>>
>>
>
--
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