On 25 November 2015 at 18:16, Carlo Caione <carlo@xxxxxxxxxxxx> wrote: > On Wed, Nov 25, 2015 at 5:34 PM, Ulf Hansson <ulf.hansson@xxxxxxxxxx> wrote: >> On 25 November 2015 at 15:39, Carlo Caione <carlo@xxxxxxxxxx> wrote: >>> From: Carlo Caione <carlo@xxxxxxxxxxxx> >>> >>> This patch introduce a new MMC_CAP2_NO_SDIO cap used to tell the mmc >>> core to not send SDIO specific commands. >> >> I guess there are two reasons to why such capability is useful. >> 1) The host controller/driver doesn't support SDIO. >> 2) There is an embedded/non-removable eMMC/SD card. >> >> Within that context, we might also want to add MMC_CAP2_NO_MMC|SD, or >> what do you think? > > Is there really any driver / controller not supporting MMC|SD commands? Probably not. I was thinking of optimizing the time it takes to detect a card. For example, if we know it's a non-removable eMMC, we can skip the SDIO and SD part in the initialization sequence. Whether that's really worth to optimize I don't know without measuring the times. [...] 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
