From: Michael Cree <mcree@orcon.net.nz>
To: linux-alpha@vger.kernel.org
Cc: Michael Cree <mcree@orcon.net.nz>,
linux-kernel@vger.kernel.org, Matt Turner <mattst88@gmail.com>,
Richard Henderson <rth@twiddle.net>,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
649468@bugs.debian.org, Ben Hutchings <ben@decadent.org.uk>
Subject: [PATCH] alpha: add io{read,write}{16,32}be functions
Date: Wed, 30 Nov 2011 21:01:40 +1300 [thread overview]
Message-ID: <1322640100-14534-1-git-send-email-mcree@orcon.net.nz> (raw)
These functions are used in some PCI drivers with big-endian
MMIO space.
Admittedly it is almost certain that no one this side of the
Moon would use such a card in an Alpha but it does get us
closer to being able to build allyesconfig or allmodconfig,
and it enables the Debian default generic config to build.
Signed-off-by: Michael Cree <mcree@orcon.net.nz>
---
arch/alpha/include/asm/io.h | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/arch/alpha/include/asm/io.h b/arch/alpha/include/asm/io.h
index 56ff965..6365ef2 100644
--- a/arch/alpha/include/asm/io.h
+++ b/arch/alpha/include/asm/io.h
@@ -490,6 +490,11 @@ extern inline void writeq(u64 b, volatile void __iomem *addr)
}
#endif
+#define ioread16be(p) be16_to_cpu(ioread16(p))
+#define ioread32be(p) be32_to_cpu(ioread32(p))
+#define iowrite16be(v,p) iowrite16(cpu_to_be16(v), (p))
+#define iowrite32be(v,p) iowrite32(cpu_to_be32(v), (p))
+
#define inb_p inb
#define inw_p inw
#define inl_p inl
--
1.7.4.3
next reply other threads:[~2011-11-30 8:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 8:01 Michael Cree [this message]
2011-12-06 18:02 ` [PATCH] alpha: add io{read,write}{16,32}be functions Raúl Porcel
2012-04-24 5:51 ` Jonathan Nieder
2012-04-24 20:01 ` Matt Turner
2012-04-25 2:11 ` Jonathan Nieder
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=1322640100-14534-1-git-send-email-mcree@orcon.net.nz \
--to=mcree@orcon.net.nz \
--cc=649468@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=rth@twiddle.net \
/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