From: Joe Perches <joe@perches.com>
To: Mischa Jonker <Mischa.Jonker@synopsys.com>
Cc: Vineet.Gupta1@synopsys.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARC: Fix __udelay parentheses
Date: Wed, 28 Aug 2013 11:45:39 -0700 [thread overview]
Message-ID: <1377715539.1928.45.camel@joe-AO722> (raw)
In-Reply-To: <1377714588-2144-1-git-send-email-mjonker@synopsys.com>
On Wed, 2013-08-28 at 20:29 +0200, Mischa Jonker wrote:
> Make sure that usecs is casted to long long, to ensure that the
> (usecs * 4295 * HZ) multiplication is 64 bit.
>
> Initially, the (usecs * 4295 * HZ) part was done as a 32 bit
> multiplication, with the result casted to 64 bit. This led to some bits
> falling off.
>
> Signed-off-by: Mischa Jonker <mjonker@synopsys.com>
> ---
> arch/arc/include/asm/delay.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arc/include/asm/delay.h b/arch/arc/include/asm/delay.h
> index 442ce5d..8d35fe1 100644
> --- a/arch/arc/include/asm/delay.h
> +++ b/arch/arc/include/asm/delay.h
> @@ -56,8 +56,8 @@ static inline void __udelay(unsigned long usecs)
> /* (long long) cast ensures 64 bit MPY - real or emulated
> * HZ * 4295 is pre-evaluated by gcc - hence only 2 mpy ops
> */
> - loops = ((long long)(usecs * 4295 * HZ) *
> - (long long)(loops_per_jiffy)) >> 32;
> + loops = (((long long) usecs) * 4295 * HZ *
> + (long long) loops_per_jiffy) >> 32;
Shouldn't this be unsigned long long or u64?
Why is it >> 32 again?
The comment above it doesn't seem to match the code.
next prev parent reply other threads:[~2013-08-28 18:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 18:29 Mischa Jonker
2013-08-28 18:45 ` Joe Perches [this message]
2013-08-28 18:53 ` Mischa Jonker
2013-08-28 19:01 ` Joe Perches
2013-08-28 19:12 ` Mischa Jonker
2013-08-29 1:43 ` Joe Perches
2013-08-29 5:55 ` Vineet Gupta
2013-08-29 6:01 ` Joe Perches
2013-08-29 6:24 ` Vineet Gupta
2013-08-29 6:37 ` Joe Perches
2013-08-29 6:49 ` Vineet Gupta
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=1377715539.1928.45.camel@joe-AO722 \
--to=joe@perches.com \
--cc=Mischa.Jonker@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®