Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1359969 > unrolled thread

Re: [PATCH] mmc: dw_mmc-rockchip: fix failing to mount partition with "discard"

Started byShawn Lin <shawn.lin@rock-chips.com>
First post2016-03-17 16:50 +0100
Last post2016-03-18 05:50 +0100
Articles 3 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH] mmc: dw_mmc-rockchip: fix failing to mount partition with  "discard" Shawn Lin <shawn.lin@rock-chips.com> - 2016-03-17 16:50 +0100
    Re: [PATCH] mmc: dw_mmc-rockchip: fix failing to mount partition with  "discard" Jaehoon Chung <jh80.chung@samsung.com> - 2016-03-18 02:50 +0100
      Re: [PATCH] mmc: dw_mmc-rockchip: fix failing to mount partition with  "discard" Shawn Lin <shawn.lin@rock-chips.com> - 2016-03-18 05:50 +0100

#1359969 — Re: [PATCH] mmc: dw_mmc-rockchip: fix failing to mount partition with "discard"

FromShawn Lin <shawn.lin@rock-chips.com>
Date2016-03-17 16:50 +0100
SubjectRe: [PATCH] mmc: dw_mmc-rockchip: fix failing to mount partition with "discard"
Message-ID<rdIls-MU-19@gated-at.bofh.it>
Hi jaehoon,

On 2016/3/2 9:29, Jaehoon Chung wrote:
> 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.
>

Any good news? :)
Or let add it for dw_mmc by default?

> 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,
>>
>
>
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip
>


-- 
Best Regards
Shawn Lin

[toc] | [next] | [standalone]

#1360302

FromJaehoon Chung <jh80.chung@samsung.com>
Date2016-03-18 02:50 +0100
Message-ID<rdRI6-7c5-3@gated-at.bofh.it>
In reply to#1359969
Hi Shawn,

On 03/18/2016 12:46 AM, Shawn Lin wrote:
> Hi jaehoon,
> 
> On 2016/3/2 9:29, Jaehoon Chung wrote:
>> 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.
>>
> 
> Any good news? :)
> Or let add it for dw_mmc by default?

Sorry for replying too late..I had other tasks..:(
Today or Tomorrow, i will apply the patches related with dw-mmcc controller.
And will request to pull to Ulf.

I didn't check...but i think this patch will be applied on dw_mmc-rockchip.
After then..we can use it by default in future.

Refer to below.
https://patchwork.kernel.org/patch/4240491/

Best Regards,
Jaehoon Chung

> 
>> 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,
>>>
>>
>>
>> _______________________________________________
>> Linux-rockchip mailing list
>> Linux-rockchip@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-rockchip
>>
> 
>

[toc] | [prev] | [next] | [standalone]

#1360337

FromShawn Lin <shawn.lin@rock-chips.com>
Date2016-03-18 05:50 +0100
Message-ID<rdUwh-G8-1@gated-at.bofh.it>
In reply to#1360302
Hi Jaehoon,

On 2016-3-18 9:47, Jaehoon Chung wrote:
> Hi Shawn,
>
> On 03/18/2016 12:46 AM, Shawn Lin wrote:
>> Hi jaehoon,
>>
>> On 2016/3/2 9:29, Jaehoon Chung wrote:
>>> 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.
>>>
>>
>> Any good news? :)
>> Or let add it for dw_mmc by default?
>
> Sorry for replying too late..I had other tasks..:(
> Today or Tomorrow, i will apply the patches related with dw-mmcc controller.
> And will request to pull to Ulf.
>
> I didn't check...but i think this patch will be applied on dw_mmc-rockchip.
> After then..we can use it by default in future.
>

Thanks. That's a good plan.

> Refer to below.
> https://patchwork.kernel.org/patch/4240491/

yes, I also found this patch and it was not merge yet.
So we still need MMC_CAP_ERASE to make sure we can enable
discard unless the cap is removed in future.


>
> Best Regards,
> Jaehoon Chung
>
>>
>>> 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,
>>>>
>>>
>>>
>>> _______________________________________________
>>> Linux-rockchip mailing list
>>> Linux-rockchip@lists.infradead.org
>>> http://lists.infradead.org/mailman/listinfo/linux-rockchip
>>>
>>
>>
>
>
>
>

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web