Hi Paul, On Thu, Oct 06 2011, Paul Walmsley wrote: > 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. Thanks, both pushed to mmc-next for 3.2. We've run out of MMC caps nad moved onto CAPS2, so I modified these patches to define and test MMC_CAP2_NO_MULTI_READ instead of MMC_CAP_NO_MULTI_READ: http://dev.laptop.org/git/users/cjb/mmc/commit/?h=mmc-next&id=a4b35b6acf2e9edc52132d34015f0a90b02e2df2 http://dev.laptop.org/git/users/cjb/mmc/commit/?h=mmc-next&id=6d621423128909f09072835445ce36dd357a758a (This shouldn't affect your hwmod patch, since that just uses an OMAP-internal flag.) - Chris. -- Chris Ball <cjb@xxxxxxxxxx> <http://printf.net/> One Laptop Per Child -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
