From: Jaehoon Chung <jh80.chung@samsung.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: Jaehoon Chung <jh80.chung@samsung.com>,
linux-mmc@vger.kernel.org, Chris Ball <cjb@laptop.org>,
kyungmin Park <kyungmin.park@samsung.com>,
Andrew Morton <akpm@linux-foundation.org>,
matt@console-pimps.org
Subject: Re: [RFC Patch] SDHCI: add quirk for data timeout value when card busy.
Date: Tue, 30 Nov 2010 19:13:28 +0900 [thread overview]
Message-ID: <4CF4CE48.7040102@samsung.com> (raw)
In-Reply-To: <20101130095618.GA6408@pengutronix.de>
Hi Wolfram.
Maybe, happen for all sdhci-controllers...
Card is configurable with eMMC spec..But sdhci-controller didn't support that card.
So SDHCI controller need to use quriks..
Thanks,
Jaehoon Chung
Wolfram Sang wrote:
> Hi,
>
> On Tue, Nov 30, 2010 at 03:13:48PM +0900, Jaehoon Chung wrote:
>> This patch is added quirks for data timeout value.
>>
>> Some card have problem when suspend/resume.
>> CMD6(switch command) to switch the bus to high speed mode
>> and to set the bus width.
>>
>> After resuming, the card was initialized...in that time, some
>> card need set a correct timeout value.
>> so we add SDHCI_QUIRK_SET_DATA_TIMEOUT_VAL.
>
> If this is a flaw of the _card_, why do we need a controller quirk here?
> Shouldn't this happen for all sdhci-controllers?
>
> Kind regards,
>
> Wolfram
>
next prev parent reply other threads:[~2010-11-30 10:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 6:13 [RFC Patch] SDHCI: add quirk for data timeout value when card busy Jaehoon Chung
2010-11-30 6:42 ` Philip Rakity
2010-11-30 7:15 ` Jaehoon Chung
2010-11-30 9:56 ` Wolfram Sang
2010-11-30 10:13 ` Jaehoon Chung [this message]
2010-11-30 10:54 ` Wolfram Sang
2010-11-30 11:37 ` Jaehoon Chung
2010-11-30 15:56 ` Philip Rakity
2010-12-01 5:44 ` Jaehoon Chung
2010-12-01 5:51 ` Philip Rakity
2010-12-01 12:29 ` Jaehoon Chung
2010-12-01 16:21 ` Philip Rakity
2010-12-02 7:40 ` Jaehoon Chung
2010-12-02 9:09 ` Wolfram Sang
2010-12-02 16:00 ` Philip Rakity
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=4CF4CE48.7040102@samsung.com \
--to=jh80.chung@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=cjb@laptop.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-mmc@vger.kernel.org \
--cc=matt@console-pimps.org \
--cc=w.sang@pengutronix.de \
/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