[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0c002d216fa44df39fef87001079ca84@hyperstone.com>
Date: Mon, 20 Sep 2021 09:34:34 +0000
From: Christian Löhle <CLoehle@...erstone.com>
To: Jesper Nilsson <jesper.nilsson@...s.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
"marten.lindahl@...s.com" <marten.lindahl@...s.com>,
"jh80.chung@...sung.com" <jh80.chung@...sung.com>,
"ulf.hansson@...aro.org" <ulf.hansson@...aro.org>
Subject: Re: [PATCH] mmc: dw_mmc: avoid long timeout if register invalid
From: Jesper Nilsson <jesper.nilsson@...s.com>
Sent: Friday, September 17, 2021 3:41 PM
To: Christian Löhle
Cc: linux-kernel@...r.kernel.org; linux-mmc@...r.kernel.org; marten.lindahl@...s.com; jh80.chung@...sung.com; ulf.hansson@...aro.org
Subject: Re: [PATCH] mmc: dw_mmc: avoid long timeout if register invalid
>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
Yes, apart from it only affecting reads, the calculated timeout is only that high if the register still holds the reset value.
I've only seen and would expect this for initialization 'read' commands, like ACMD13, or ACMD51.
I have chosen 1s to hit an expectation that I would consider normal, that a card is initialized in a couple of seconds after plugging in, or never.
Regards,
Christian=
Hyperstone GmbH | Line-Eid-Strasse 3 | 78467 Konstanz
Managing Directors: Dr. Jan Peter Berns.
Commercial register of local courts: Freiburg HRB381782
Powered by blists - more mailing lists