Lines Matching defs:timeout
122 * NVQUIRK_HAS_TMCLK is for SoC's having separate timeout clock for Tegra
123 * SDMMC hardware data timeout.
230 /* Seems like we're getting spurious timeout and crc errors, so
562 /* 10 ms timeout */
652 "nvidia,pad-autocal-pull-up-offset-3v3-timeout",
657 pr_warn("%s: Missing autocal timeout 3v3-pad drvs\n",
663 "nvidia,pad-autocal-pull-down-offset-3v3-timeout",
668 pr_warn("%s: Missing autocal timeout 3v3-pad drvs\n",
674 "nvidia,pad-autocal-pull-up-offset-1v8-timeout",
679 pr_warn("%s: Missing autocal timeout 1v8-pad drvs\n",
685 "nvidia,pad-autocal-pull-down-offset-1v8-timeout",
690 pr_warn("%s: Missing autocal timeout 1v8-pad drvs\n",
844 /* 1 ms sleep, 5 ms timeout */
1189 ktime_t timeout;
1205 timeout = ktime_add_us(ktime_get(), 50);
1207 timed_out = ktime_compare(ktime_get(), timeout) > 0;
1294 * HW busy detection timeout is based on programmed data timeout
1295 * counter and maximum supported timeout is 11s which may not be
1300 * without HW timeout.
1303 * more than maximum HW busy timeout of 11s otherwise use finite
1725 * timeout clock and SW can choose TMCLK or SDCLK for hardware
1726 * data timeout through the bit USE_TMCLK_FOR_DATA_TIMEOUT of
1731 * With TMCLK of 12Mhz provides maximum data timeout period that can
1732 * be achieved is 11s better than using SDCLK for data timeout.