public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: robert.foss@collabora.com, ulf.hansson@linaro.org,
	linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andrew Bresticker <abrestic@chromium.org>,
	Kevin Cernekee <cernekee@chromium.org>,
	Benson Leung <bleung@chromium.org>
Cc: Christopher Freeman <cfreeman@nvidia.com>
Subject: Re: [PACTH v3] mmc: sdhci: Do not allow tuning procedure to be interrupted
Date: Wed, 17 Aug 2016 13:47:33 +0300	[thread overview]
Message-ID: <eee256ca-3366-b25c-0936-0a80b1510325@intel.com> (raw)
In-Reply-To: <1471382729-28472-1-git-send-email-robert.foss@collabora.com>

On 17/08/16 00:25, robert.foss@collabora.com wrote:
> From: Christopher Freeman <cfreeman@nvidia.com>
> 
> wait_event_interruptible_timeout() will return early if the blocked
> process receives a signal, causing the driver to abort the tuning
> procedure and possibly leaving the controller in a bad state.  Since the
> tuning command is expected to complete quickly (<50ms) and we've set a
> timeout, use wait_event_timeout() instead.
> 
> Signed-off-by: Christopher Freeman <cfreeman@nvidia.com>
> Tested-by: Robert Foss <robert.foss@collabora.com>
> Signed-off-by: Robert Foss <robert.foss@collabora.com>
> Reviewed-by: Benson Leung <bleung@chromium.org>

The mmc block queues are kernel threads which I would expect ignore signals,
so I am curious how you hit this?

In any case:

Acked-by: Adrian Hunter <adrian.hunter@intel.com>

> ---
>  drivers/mmc/host/sdhci.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/mmc/host/sdhci.c b/drivers/mmc/host/sdhci.c
> index 0e3d7c0..9e80203 100644
> --- a/drivers/mmc/host/sdhci.c
> +++ b/drivers/mmc/host/sdhci.c
> @@ -1960,7 +1960,7 @@ static int sdhci_execute_tuning(struct mmc_host *mmc, u32 opcode)
>  
>  		spin_unlock_irqrestore(&host->lock, flags);
>  		/* Wait for Buffer Read Ready interrupt */
> -		wait_event_interruptible_timeout(host->buf_ready_int,
> +		wait_event_timeout(host->buf_ready_int,
>  					(host->tuning_done == 1),
>  					msecs_to_jiffies(50));
>  		spin_lock_irqsave(&host->lock, flags);
> 


  reply	other threads:[~2016-08-17 10:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-16 21:25 [PACTH v3] mmc: sdhci: Do not allow tuning procedure to be interrupted robert.foss
2016-08-17 10:47 ` Adrian Hunter [this message]
2016-08-17 17:31   ` Robert Foss
2016-08-17 22:12     ` Christopher Freeman
2016-08-18 13:46       ` Adrian Hunter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=eee256ca-3366-b25c-0936-0a80b1510325@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=abrestic@chromium.org \
    --cc=bleung@chromium.org \
    --cc=cernekee@chromium.org \
    --cc=cfreeman@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=robert.foss@collabora.com \
    --cc=ulf.hansson@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox