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? > Because of 2), we might also want to add a new mmc DT binding or > perhaps try interpret a combination of them to enable > MMC_CAP2_NO_SDIO!? Probably I'm missing something but what would be the difference with the 'non-removable' parameter we already have? >> >> Signed-off-by: Carlo Caione <carlo@xxxxxxxxxxxx> > > Thanks, applied for next! Thanks, -- Carlo Caione | +39.340.80.30.096 | Endless -- 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
