On Tue, 21 Sept 2021 at 16:36, Linus Walleij <linus.walleij@xxxxxxxxxx> wrote:
>
> Put a small comment before assigning IRQ_WAKE_THREAD
> telling us what is going on.
>
> Cc: Russell King <linux@xxxxxxxxxxxxxxx>
> Cc: Yann Gautier <yann.gautier@xxxxxxxxxxx>
> Cc: Ludovic Barre <ludovic.barre@xxxxxx>
> Signed-off-by: Linus Walleij <linus.walleij@xxxxxxxxxx>
Applied for next, thanks!
Kind regards
Uffe
> ---
> drivers/mmc/host/mmci.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/mmc/host/mmci.c b/drivers/mmc/host/mmci.c
> index 3765e2f4ad98..c9cacd4d5b22 100644
> --- a/drivers/mmc/host/mmci.c
> +++ b/drivers/mmc/host/mmci.c
> @@ -1394,6 +1394,10 @@ mmci_cmd_irq(struct mmci_host *host, struct mmc_command *cmd,
> } else if (host->variant->busy_timeout && busy_resp &&
> status & MCI_DATATIMEOUT) {
> cmd->error = -ETIMEDOUT;
> + /*
> + * This will wake up mmci_irq_thread() which will issue
> + * a hardware reset of the MMCI block.
> + */
> host->irq_action = IRQ_WAKE_THREAD;
> } else {
> cmd->resp[0] = readl(base + MMCIRESPONSE0);
> --
> 2.31.1
>
