linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: delay: allow timer-based delay implementation to be selected
Date: Tue, 26 Jun 2012 17:28:02 +0100	[thread overview]
Message-ID: <20120626162802.GS27996@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <4FE9DC95.30408@gmail.com>

On Tue, Jun 26, 2012 at 05:00:21PM +0100, Rob Herring wrote:
> On 06/26/2012 10:54 AM, Will Deacon wrote:
> > The reason this is slightly problematic is due to gas's inability to
> > represent unsigned constants -- namely that the 'U' suffix causes it to
> > barf. I can fix it with the diff below, but please let me know what you
> > think.
> 
> [snip]
> 
> > +#ifndef __ASSEMBLY__
> > +
> 
> 
> > +#define UDELAY_MULT_HZ	2199023U
> > +#else
> > +#define UDELAY_MULT_HZ	2199023
> 
> Doesn't UL() macro do what you need?

Indeed, thanks for pointing that out as I'd failed to spot it.
I'll include this change for v2.

Will

  reply	other threads:[~2012-06-26 16:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-22 15:09 [PATCH 0/2] Use architected timers for delay loop Will Deacon
2012-06-22 15:09 ` [PATCH 1/2] ARM: arch timer: implement read_current_timer and get_cycles Will Deacon
2012-06-25 21:39   ` Stephen Boyd
2012-06-26 10:37     ` Will Deacon
2012-06-26 17:44       ` Stephen Boyd
2012-06-22 15:09 ` [PATCH 2/2] ARM: delay: allow timer-based delay implementation to be selected Will Deacon
2012-06-25 21:39   ` Stephen Boyd
2012-06-26 10:49     ` Will Deacon
2012-06-26 15:54       ` Will Deacon
2012-06-26 16:00         ` Rob Herring
2012-06-26 16:28           ` Will Deacon [this message]
2012-06-27  2:07       ` Stephen Boyd
2012-06-27  9:41         ` Will Deacon
2012-06-22 22:26 ` [PATCH 0/2] Use architected timers for delay loop Russell King - ARM Linux
2012-06-25 10:03   ` Will Deacon
2012-06-25 21:38 ` Stephen Boyd
2012-06-26 10:35   ` Will Deacon
2012-06-26 17:42     ` Stephen Boyd

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=20120626162802.GS27996@mudshark.cambridge.arm.com \
    --to=will.deacon@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).