[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <05af228c-139b-2b7f-f626-36fb34634be5@broadcom.com>
Date: Sun, 26 May 2019 20:42:04 +0200
From: Arend Van Spriel <arend.vanspriel@...adcom.com>
To: Douglas Anderson <dianders@...omium.org>,
Ulf Hansson <ulf.hansson@...aro.org>,
Kalle Valo <kvalo@...eaurora.org>,
Adrian Hunter <adrian.hunter@...el.com>
Cc: linux-rockchip@...ts.infradead.org,
Double Lo <double.lo@...ress.com>, briannorris@...omium.org,
Madhan Mohan R <madhanmohan.r@...ress.com>, mka@...omium.org,
Wright Feng <wright.feng@...ress.com>,
Chi-Hsien Lin <chi-hsien.lin@...ress.com>,
Jiong Wu <lohengrin1024@...il.com>,
Ritesh Harjani <riteshh@...eaurora.org>,
linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org,
Shawn Lin <shawn.lin@...k-chips.com>,
Wolfram Sang <wsa+renesas@...g-engineering.com>,
Avri Altman <avri.altman@....com>, Martin Hicks <mort@...k.org>
Subject: Re: [PATCH 2/3] mmc: core: API for temporarily disabling
auto-retuning due to errors
On 5/18/2019 12:54 AM, Douglas Anderson wrote:
> Normally when the MMC core sees an "-EILSEQ" error returned by a host
> controller then it will trigger a retuning of the card. This is
> generally a good idea.
Probably a question for Adrian, but how is this retuning scheduled. I
recall seeing something in mmc_request_done. How about deferring the
retuning upon a release host or is that too sdio specific.
Regards,
Arend
Powered by blists - more mailing lists