On Thu, 2018-05-31 at 12:38 +0200, Ulf Hansson wrote: > There is no obvious reasons to why mvsdio shouldn't be able to > support > erase/trim/discard operations, hence let's set MMC_CAP_ERASE for it. > > Cc: Damien Thebault <damien.thebault@xxxxxxxxx> > Signed-off-by: Ulf Hansson <ulf.hansson@xxxxxxxxxx> > --- > drivers/mmc/host/mvsdio.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/drivers/mmc/host/mvsdio.c b/drivers/mmc/host/mvsdio.c > index 4c70829cffd7..e22bbff89c8d 100644 > --- a/drivers/mmc/host/mvsdio.c > +++ b/drivers/mmc/host/mvsdio.c > @@ -757,6 +757,8 @@ static int mvsd_probe(struct platform_device > *pdev) > if (maxfreq) > mmc->f_max = maxfreq; > > + mmc->caps |= MMC_CAP_ERASE; > + > spin_lock_init(&host->lock); > > host->base = devm_ioremap_resource(&pdev->dev, r); Tested using blkdiscard and blkdiscard -s on an eMMC. Tested-By: Damien Thébault <damien.thebault@xxxxxxxxx> -- Damien Thébault R&D Engineer VITEC T. +33 1 46 73 06 06 F. +33 9 59 85 99 92 E. damien.thebault@xxxxxxxxx http://www.vitec.com��.n��������+%����;��w��{.n�����{��i��)�� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
