From: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel@vger.kernel.org, Daniel Mack <daniel@caiaq.de>,
Sven Neumann <s.neumann@raumfeld.com>,
Janine Kropp <nin@directfb.org>,
Denis Oliver Kropp <dok@directfb.org>,
linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] video: pxa3xx-gcu: Simplify the logic to exit while loop in pxa3xx_gcu_wait_idle
Date: Thu, 12 Apr 2012 02:22:11 +0000 [thread overview]
Message-ID: <4F863C53.5060205@gmx.de> (raw)
In-Reply-To: <1332818156.21855.4.camel@phoenix>
On 03/27/2012 03:15 AM, Axel Lin wrote:
> If wait_event_interruptible_timeout returns a positive value, it means
> the condition evaluated is true. Which means priv->shared->hw_running is false.
> And then we will exit the loop.
>
> This patch simplifies the logic to exit the while loop.
>
> Signed-off-by: Axel Lin <axel.lin@gmail.com>
Applied.
Thanks,
Florian Tobias Schandinat
> ---
> drivers/video/pxa3xx-gcu.c | 5 +----
> 1 files changed, 1 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/video/pxa3xx-gcu.c b/drivers/video/pxa3xx-gcu.c
> index 1d71c08..0b4ae0c 100644
> --- a/drivers/video/pxa3xx-gcu.c
> +++ b/drivers/video/pxa3xx-gcu.c
> @@ -316,12 +316,9 @@ pxa3xx_gcu_wait_idle(struct pxa3xx_gcu_priv *priv)
> ret = wait_event_interruptible_timeout(priv->wait_idle,
> !priv->shared->hw_running, HZ*4);
>
> - if (ret < 0)
> + if (ret != 0)
> break;
>
> - if (ret > 0)
> - continue;
> -
> if (gc_readl(priv, REG_GCRBEXHR) = rbexhr &&
> priv->shared->num_interrupts = num) {
> QERROR("TIMEOUT");
prev parent reply other threads:[~2012-04-12 2:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 3:15 [PATCH] video: pxa3xx-gcu: Simplify the logic to exit while loop in pxa3xx_gcu_wait_idle Axel Lin
2012-04-12 2:22 ` Florian Tobias Schandinat [this message]
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=4F863C53.5060205@gmx.de \
--to=florianschandinat@gmx.de \
--cc=axel.lin@gmail.com \
--cc=daniel@caiaq.de \
--cc=dok@directfb.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nin@directfb.org \
--cc=s.neumann@raumfeld.com \
/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;
as well as URLs for NNTP newsgroup(s).