From: Paul Walmsley <paul@pwsan.com>
To: linux-omap@vger.kernel.org, linux-mmc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: sakoman@gmail.com, dhylands@gmail.com, cjb@laptop.org
Subject: [PATCH 0/2] MMC: disable multiblock reads on controllers that don't support them
Date: Thu, 06 Oct 2011 14:50:30 -0600 [thread overview]
Message-ID: <20111006205002.7083.94088.stgit@dusk> (raw)
Hello,
Some MMC controller instances integrated on older OMAP34xx/35xx chips
don't work correctly with multiple-block reads, due to a hardware bug.
This series fixes the problem by adding an MMC capability flag for this
case and making the appropriate changes to the MMC core code and OMAP HSMMC
driver to support this.
Once this series is merged, a subsequent patch will be needed by us OMAP
folks to pass the appropriate device data via hwmod - this will be posted
separately.
- Paul
---
mmc_errata_2.1.1.128_fix_3.2
text data bss dec hex filename
6325283 655708 5591124 12572115 bfd5d3 vmlinux.omap2plus_defconfig.orig
6329423 655700 5591124 12576247 bfe5f7 vmlinux.omap2plus_defconfig.patched
Paul Walmsley (2):
MMC: add workaround for controllers with broken multiblock reads
MMC: omap_hsmmc: disable multiblock reads when platform_data indicates that they are broken
arch/arm/plat-omap/include/plat/mmc.h | 19 ++++++++++++++++++-
drivers/mmc/card/block.c | 21 ++++++++++++++-------
drivers/mmc/host/omap_hsmmc.c | 4 ++++
include/linux/mmc/host.h | 1 +
4 files changed, 37 insertions(+), 8 deletions(-)
next reply other threads:[~2011-10-06 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 20:50 Paul Walmsley [this message]
2011-10-06 20:50 ` [PATCH 1/2] MMC: add workaround for controllers with broken multiblock reads Paul Walmsley
2011-10-06 20:50 ` [PATCH 2/2] MMC: omap_hsmmc: disable multiblock reads when platform_data indicates that they are broken Paul Walmsley
2011-10-07 23:22 ` [PATCH 0/2] MMC: disable multiblock reads on controllers that don't support them Steve Sakoman
2011-10-24 9:27 ` 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=20111006205002.7083.94088.stgit@dusk \
--to=paul@pwsan.com \
--cc=cjb@laptop.org \
--cc=dhylands@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=sakoman@gmail.com \
/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