From: Shawn Lin <shawn.lin@rock-chips.com>
To: Jaehoon Chung <jh80.chung@samsung.com>,
Ulf Hansson <ulf.hansson@linaro.org>
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
Subject: Re: [PATCH] mmc: dw_mmc-rockchip: fix failing to mount partition with "discard"
Date: Wed, 2 Mar 2016 09:46:14 +0800 [thread overview]
Message-ID: <56D645E6.80508@rock-chips.com> (raw)
In-Reply-To: <56D641FA.8010606@samsung.com>
在 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 <shawn.lin@rock-chips.com>
>> ---
>>
>> 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
next prev parent reply other threads:[~2016-03-02 1:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 7:12 [PATCH] mmc: dw_mmc-rockchip: fix failing to mount partition with "discard" Shawn Lin
2016-03-02 1:29 ` Jaehoon Chung
2016-03-02 1:46 ` Shawn Lin [this message]
2016-03-17 15:46 ` Shawn Lin
2016-03-18 1:47 ` Jaehoon Chung
2016-03-18 4:46 ` Shawn Lin
2016-03-29 1:17 ` Jaehoon Chung
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56D645E6.80508@rock-chips.com \
--to=shawn.lin@rock-chips.com \
--cc=jh80.chung@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=shawn.lin@kernel-upstream.org \
--cc=ulf.hansson@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox