On 27 January 2014 11:40, Adrian Hunter adrian.hun...@intel.com wrote:
On 23/01/14 16:11, Ulf Hansson wrote:
On 23 January 2014 11:10, Adrian Hunter adrian.hun...@intel.com wrote:
On 22/01/14 17:00, Ulf Hansson wrote:
If the host controller supports busy detection in HW, we expect the
On 23/01/14 16:11, Ulf Hansson wrote:
On 23 January 2014 11:10, Adrian Hunter adrian.hun...@intel.com wrote:
On 22/01/14 17:00, Ulf Hansson wrote:
If the host controller supports busy detection in HW, we expect the
MMC_CAP_WAIT_WHILE_BUSY to be set. Likewise the corresponding
On 22/01/14 17:00, Ulf Hansson wrote:
If the host controller supports busy detection in HW, we expect the
MMC_CAP_WAIT_WHILE_BUSY to be set. Likewise the corresponding
host-max_busy_timeout shall reflect the maximum busy detection timeout
supported by the host. A timeout set to zero, is
On 23 January 2014 11:10, Adrian Hunter adrian.hun...@intel.com wrote:
On 22/01/14 17:00, Ulf Hansson wrote:
If the host controller supports busy detection in HW, we expect the
MMC_CAP_WAIT_WHILE_BUSY to be set. Likewise the corresponding
host-max_busy_timeout shall reflect the maximum busy
If the host controller supports busy detection in HW, we expect the
MMC_CAP_WAIT_WHILE_BUSY to be set. Likewise the corresponding
host-max_busy_timeout shall reflect the maximum busy detection timeout
supported by the host. A timeout set to zero, is interpreted as the
host supports whatever
