[...] >>> If I am not wrong, in current implementation of runtime suspend, >>> the driver stops BKOPS (send HPI) just before sending sleep command, >>> see _mmc_suspend(), depends on “MMC_CAP_AGGRESSIVE_PM” flag. >>> In this case, the eMMC device will not have enough time to perform internal >>> BKOPS in both – Manual and Auto BKOPS configurations. >>> >> >> ye, so it seems a pre-exiting issue before introducing auto bkops? >> I think we can push another patch to improve it but not handling >> it for this $SUBJECT, does it sound ok to you? > > Runtime suspend for eMMC has a default auto-suspend delay of 3 seconds > (refer mmc_blk_probe()). Isn't that when auto bkops would happen? That's correct. So perhaps we should extend the default auto-suspend delay? The SD case actually have the same issue, as I some background operations exists there as well. [...] Kind regards Uffe -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
