Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756751AbcCBBql (ORCPT ); Tue, 1 Mar 2016 20:46:41 -0500 Received: from lucky1.263xmail.com ([211.157.147.132]:45990 "EHLO lucky1.263xmail.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754161AbcCBBqi (ORCPT ); Tue, 1 Mar 2016 20:46:38 -0500 X-263anti-spam: KSV:0; X-MAIL-GRAY: 1 X-MAIL-DELIVERY: 0 X-KSVirus-check: 0 X-ABS-CHECKED: 4 X-ADDR-CHECKED: 0 X-RL-SENDER: shawn.lin@rock-chips.com X-FST-TO: linux-rockchip@lists.infradead.org X-SENDER-IP: 58.22.7.114 X-LOGIN-NAME: shawn.lin@rock-chips.com X-UNIQUE-TAG: <910bd50deb2da31b5cbbf2aa14c302ae> X-ATTACHMENT-NUM: 0 X-DNS-TYPE: 0 Subject: Re: [PATCH] mmc: dw_mmc-rockchip: fix failing to mount partition with "discard" To: Jaehoon Chung , Ulf Hansson References: <1456816373-32518-1-git-send-email-shawn.lin@rock-chips.com> <56D641FA.8010606@samsung.com> Cc: shawn.lin@rock-chips.com, shawn.lin@kernel-upstream.org, linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org From: Shawn Lin Message-ID: <56D645E6.80508@rock-chips.com> Date: Wed, 2 Mar 2016 09:46:14 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <56D641FA.8010606@samsung.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2208 Lines: 71 在 2016/3/2 9:29, Jaehoon Chung 写道: > Hi Shawn. > > On 03/01/2016 04:12 PM, Shawn Lin wrote: >> Without MMC_CAP_ERASE support, we fail to mount partition >> with "discard" option since mmc_queue_setup_discard is limited >> for checking mmc_can_erase. Without doing mmc_queue_setup_discard, >> blk_queue_discard fails to test QUEUE_FLAG_DISCARD flag, so we get >> the following log from f2fs(actually similar to other file system): >> >> mounting with "discard" option, but the device does not support discard > > We can enable MMC_CAP_ERASE by default, since other SoC also needs this capability. > I had sent some patch for enabling by default, but at that time i didn't remember why not enabled by default. > I will check that reason..and share the information. Hi Jaehoon, Thanks for checking that. I didn't notice this part of code either until I began to develop f2fs last month. yes, I can't find any reasons not to enable it for dw_mmc because I look more into dwmmc-databooks to see if any version of IP can't support ERASE/TRIM command, and find none of them. So, enabling it by default is safe. > > Best Regards, > Jaehoon Chung > >> >> Signed-off-by: Shawn Lin >> --- >> >> drivers/mmc/host/dw_mmc-rockchip.c | 9 +++++++++ >> 1 file changed, 9 insertions(+) >> >> diff --git a/drivers/mmc/host/dw_mmc-rockchip.c b/drivers/mmc/host/dw_mmc-rockchip.c >> index 84e50f3..2eda118 100644 >> --- a/drivers/mmc/host/dw_mmc-rockchip.c >> +++ b/drivers/mmc/host/dw_mmc-rockchip.c >> @@ -234,11 +234,20 @@ static int dw_mci_rockchip_init(struct dw_mci *host) >> return 0; >> } >> >> +/* Common capabilities of RK3288 SoC */ >> +static unsigned long dw_mci_rk3288_dwmmc_caps[4] = { >> + MMC_CAP_ERASE, >> + MMC_CAP_ERASE, >> + MMC_CAP_ERASE, >> + MMC_CAP_ERASE, >> +}; >> + >> static const struct dw_mci_drv_data rk2928_drv_data = { >> .init = dw_mci_rockchip_init, >> }; >> >> static const struct dw_mci_drv_data rk3288_drv_data = { >> + .caps = dw_mci_rk3288_dwmmc_caps, >> .set_ios = dw_mci_rk3288_set_ios, >> .execute_tuning = dw_mci_rk3288_execute_tuning, >> .parse_dt = dw_mci_rk3288_parse_dt, >> > > > > -- Best Regards Shawn Lin