Hi,
Please find a report on an issue that calls for an update of the HSMMC driver for OMAP4:
"It seems like it is the sanitize command feature that was introduced in eMMC 4.5 specification that is not supported by the MMC controller on OMAP4.
For now I have disabled the sanitize command for all OMAP4 processors by applying the following patch to the kernel:
diff --git a/drivers/mmc/core/core.c b/drivers/mmc/core/core.c index 95902a7..f9cb0f7 100644
--- a/drivers/mmc/core/core.c
+++ b/drivers/mmc/core/core.c
@@ -1735,6 +1735,8 @@ EXPORT_SYMBOL(mmc_can_discard);
int mmc_can_sanitize(struct mmc_card *card) {
+ if (cpu_is_omap44xx())
+ return 0;
if (!mmc_can_trim(card) && !mmc_can_erase(card))
return 0;
if (card->ext_csd.sec_feature_support & EXT_CSD_SEC_SANITIZE)
It isn't ideal, as it belongs into the omap_hsmmc.c driver in my opinion.
I did not find a method for altering the MMC feature list after the device has been probed.
- Is there a better and more permanent fix?
For the record, the two eMMC devices are:
1) Samsung KLM4G1FE3B-B001-4GB, eMMC version 4.41. Works fine.
2) Sandisk SDIN7DP2-4G, eMMC version: 4.5. Produces I/O errors.
Thanks for looking into this.
/Magnus Aman