On 21 November 2017 at 10:34, Shawn Lin <shawn.lin@xxxxxxxxxxxxxx> wrote: > Hi Ulf, > > On 2017/11/21 17:02, Ulf Hansson wrote: >> >> On 20 November 2017 at 05:50, Park Huijin <bbang.huijin.park@xxxxxxxxx> >> wrote: >>> >>> 2017-11-15 18:13 GMT+09:00 Ulf Hansson <ulf.hansson@xxxxxxxxxx>: >>>> >>>> >>>> On 14 November 2017 at 03:48, Huijin Park <huijin.park@xxxxxxxxxxx> >>>> wrote: >>>>> >>>>> Some eMMC products keep busy time a little longer intermittently. >>>>> (eg. prepare free blocks, garbage collection...) >>>>> In this case, we recommend to wait a little longer than fail. >>>> >>>> >>>> Is this an rpmb specific problem, because the code seems only to change >>>> that. >>>> >>>> Is it write and read or only write? >>> >>> Yes. It's rpmb specific problem. >>> RPMB R/W use same flow. but only 'write' case makes the problem(long >>> busy state) sometimes. >>> When I test it, the 5~25ms is not enough although there is not max >>> busy time in the spec. >> >> >> As a matter of fact this isn't specific to RPMB writes at all but to >> all data writes. That's why we call card_busy_detect() after a data >> write. > > > Further more, we should cover all transfer pattern from userspace, not > just data writes. :) > > https://www.spinics.net/lists/linux-mmc/msg46147.html Ack! Kind regards Uffe -- 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
