Re: [PATCH 2/3] mmc: dw_mmc: Fix the CTO timeout calculation

2017-10-11 Thread Doug Anderson
Hi, On Mon, Oct 9, 2017 at 12:03 AM, Shawn Lin wrote: > Hi > > On 2017/9/28 4:56, Douglas Anderson wrote: >> >> In the commit 03de19212ea3 ("mmc: dw_mmc: introduce timer for broken >> command transfer over scheme") we tried to calculate the expected >> hardware command

Re: [PATCH 2/3] mmc: dw_mmc: Fix the CTO timeout calculation

2017-10-11 Thread Doug Anderson
Hi, On Mon, Oct 9, 2017 at 12:03 AM, Shawn Lin wrote: > Hi > > On 2017/9/28 4:56, Douglas Anderson wrote: >> >> In the commit 03de19212ea3 ("mmc: dw_mmc: introduce timer for broken >> command transfer over scheme") we tried to calculate the expected >> hardware command timeout value.

Re: [PATCH 2/3] mmc: dw_mmc: Fix the CTO timeout calculation

2017-10-09 Thread Shawn Lin
Hi On 2017/9/28 4:56, Douglas Anderson wrote: In the commit 03de19212ea3 ("mmc: dw_mmc: introduce timer for broken command transfer over scheme") we tried to calculate the expected hardware command timeout value. Unfortunately that calculation isn't quite correct in all cases. It used

Re: [PATCH 2/3] mmc: dw_mmc: Fix the CTO timeout calculation

2017-10-09 Thread Shawn Lin
Hi On 2017/9/28 4:56, Douglas Anderson wrote: In the commit 03de19212ea3 ("mmc: dw_mmc: introduce timer for broken command transfer over scheme") we tried to calculate the expected hardware command timeout value. Unfortunately that calculation isn't quite correct in all cases. It used

[PATCH 2/3] mmc: dw_mmc: Fix the CTO timeout calculation

2017-09-27 Thread Douglas Anderson
In the commit 03de19212ea3 ("mmc: dw_mmc: introduce timer for broken command transfer over scheme") we tried to calculate the expected hardware command timeout value. Unfortunately that calculation isn't quite correct in all cases. It used "bus_hz" but, as far as I can tell, it's supposed to use

[PATCH 2/3] mmc: dw_mmc: Fix the CTO timeout calculation

2017-09-27 Thread Douglas Anderson
In the commit 03de19212ea3 ("mmc: dw_mmc: introduce timer for broken command transfer over scheme") we tried to calculate the expected hardware command timeout value. Unfortunately that calculation isn't quite correct in all cases. It used "bus_hz" but, as far as I can tell, it's supposed to use