linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Daney <ddaney@caviumnetworks.com>
To: Florian Fainelli <ffainelli@freebox.fr>
Cc: linux-mips@linux-mips.org, Maxime Bizon <mbizon@freebox.fr>,
	ralf@linux-mips.org
Subject: Re: [PATCH 2/2] MIPS: add readl/write_be
Date: Mon, 14 Dec 2009 08:40:21 -0800	[thread overview]
Message-ID: <4B266A75.6020809@caviumnetworks.com> (raw)
In-Reply-To: <200912121757.56365.ffainelli@freebox.fr>

Florian Fainelli wrote:
> MIPS currently lacks the readl_be and writel_be accessors
> which are required by BCM63xx for OHCI and EHCI support.
> Let's define them globally for MIPS. This also fixes the
> compilation of the bcm63xx defconfig against USB.
> 
> Signed-off-by: Florian Fainelli <ffainelli@freebox.fr>
> ---
> diff --git a/arch/mips/include/asm/io.h b/arch/mips/include/asm/io.h
> index 436878e..65cb4e4 100644
> --- a/arch/mips/include/asm/io.h
> +++ b/arch/mips/include/asm/io.h
> @@ -447,6 +447,9 @@ __BUILDIO(q, u64)
>  #define readl_relaxed			readl
>  #define readq_relaxed			readq
>  
> +#define readl_be(addr)			__raw_readl((__force unsigned *)addr)
> +#define writel_be(val, addr)		__raw_writel(val, (__force unsigned *)addr)
> +


Without addressing the need for the patch, as a technical matter, the 
macro parameters should probably be protected by parenthesis.  I.E.:

#define readl_be(addr)			__raw_readl((__force unsigned *)(addr))
#define writel_be(val, addr)		__raw_writel((val), (__force unsigned 
*)(addr))

      parent reply	other threads:[~2009-12-14 16:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-12 16:57 [PATCH 2/2] MIPS: add readl/write_be Florian Fainelli
2009-12-12 19:31 ` Thomas Bogendoerfer
2009-12-14 17:02   ` Florian Fainelli
2009-12-14 19:05     ` Geert Uytterhoeven
2009-12-15  0:44       ` Florian Fainelli
2009-12-15  8:25         ` Ralf Baechle
2009-12-16 10:29           ` Florian Fainelli
2010-01-13 13:48             ` Ralf Baechle
2009-12-15 12:03         ` Sergei Shtylyov
2009-12-14 16:40 ` David Daney [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=4B266A75.6020809@caviumnetworks.com \
    --to=ddaney@caviumnetworks.com \
    --cc=ffainelli@freebox.fr \
    --cc=linux-mips@linux-mips.org \
    --cc=mbizon@freebox.fr \
    --cc=ralf@linux-mips.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).