On Fri, Sep 17, 2021 at 07:50:44AM +0000, Christian Löhle wrote:
> Set the limit to 1s if the register is at reset value.
One second could be to short, we have seen some cards take up
to 10s on write operations. Although that was quite a few years ago.
TMOUT is only used for reads if I understand correctly,
so it should be ok anyways.
/Jesper
> Signed-off-by: Christian Loehle <cloehle@xxxxxxxxxxxxxx>
> ---
> drivers/mmc/host/dw_mmc.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/mmc/host/dw_mmc.c b/drivers/mmc/host/dw_mmc.c
> index 6578cc64ae9e..cd9a6e0a7449 100644
> --- a/drivers/mmc/host/dw_mmc.c
> +++ b/drivers/mmc/host/dw_mmc.c
> @@ -1983,6 +1983,14 @@ static void dw_mci_set_drto(struct dw_mci *host)
> /* add a bit spare time */
> drto_ms += 10;
>
> + /*
> + * If TMOUT register still holds the reset value the above calculation
> + * would yield a timeout of over 167 seconds, limit it to 1000ms.
> + * Normal reads/writes should not take anywhere close to 120s.
> + */
> + if (drto_ms > 120000)
> + drto_ms = 1000;
> +
> spin_lock_irqsave(&host->irq_lock, irqflags);
> if (!test_bit(EVENT_DATA_COMPLETE, &host->pending_events))
> mod_timer(&host->dto_timer,
> --
> 2.32.0
> Hyperstone GmbH | Line-Eid-Strasse 3 | 78467 Konstanz
> Managing Directors: Dr. Jan Peter Berns.
> Commercial register of local courts: Freiburg HRB381782
/^JN - Jesper Nilsson
--
Jesper Nilsson -- jesper.nilsson@xxxxxxxx
