From: Wolfram Sang <w.sang@pengutronix.de>
To: Chris Ball <cjb@laptop.org>
Cc: linux-mmc@vger.kernel.org, Anton Vorontsov <cbouatmailru@gmail.com>
Subject: Re: [PATCH 2/2] mmc: sdhci: Replace SDHCI_QUIRK_NO_MULTIBLOCK with a platform hook.
Date: Mon, 7 Feb 2011 18:48:39 +0100 [thread overview]
Message-ID: <20110207174839.GF3123@pengutronix.de> (raw)
In-Reply-To: <m3zkq9n115.fsf@pullcord.laptop.org>
[-- Attachment #1: Type: text/plain, Size: 946 bytes --]
On Sun, Feb 06, 2011 at 01:13:26AM -0500, Chris Ball wrote:
> Part of a quirk cleanup run. This quirk was only used by sdhci-esdhc.
> This patch is untested.
>
> Signed-off-by: Chris Ball <cjb@laptop.org>
> Cc: Anton Vorontsov <cbouatmailru@gmail.com>
> Cc: Wolfram Sang <w.sang@pengutronix.de>
Hmm, for now I don't have a better alternative, but I somehow hink there must
be a better solution than to add one hook per
mmc->max_blk_count (changed by SDHCI_QUIRK_NO_MULTIBLOCK)
mmc->max_seg_size (changed by SDHCI_QUIRK_BROKEN_ADMA_ZEROLEN_DESC)
mmc->caps (changed by SDHCI_QUIRK_FORCE_1_BIT_DATA and SDHCI_QUIRK_BROKEN_CARD_DETECTION)
(and maybe this one also?)
mmc->max_blk_size (changed by SDHCI_QUIRK_FORCE_BLK_SZ_2048)
Will think about it...
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-02-07 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 6:13 [PATCH 2/2] mmc: sdhci: Replace SDHCI_QUIRK_NO_MULTIBLOCK with a platform hook Chris Ball
2011-02-07 17:48 ` Wolfram Sang [this message]
2011-02-12 20:22 ` Chris Ball
2011-02-12 20:43 ` Wolfram Sang
2011-02-12 21:05 ` Chris Ball
2011-02-13 21:13 ` Wolfram Sang
2011-05-29 2:28 ` Chris Ball
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=20110207174839.GF3123@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=cbouatmailru@gmail.com \
--cc=cjb@laptop.org \
--cc=linux-mmc@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).