From: Brian Gerst <brgerst@gmail.com>
To: hpa@zytor.com
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/7] x86-32: Move XQUAD definitions to numaq.h
Date: Fri, 5 Feb 2010 09:37:03 -0500 [thread overview]
Message-ID: <1265380629-3212-2-git-send-email-brgerst@gmail.com> (raw)
In-Reply-To: <1265380629-3212-1-git-send-email-brgerst@gmail.com>
Signed-off-by: Brian Gerst <brgerst@gmail.com>
---
arch/x86/include/asm/io_32.h | 3 ---
arch/x86/include/asm/numaq.h | 4 ++++
arch/x86/pci/numaq_32.c | 6 +-----
3 files changed, 5 insertions(+), 8 deletions(-)
diff --git a/arch/x86/include/asm/io_32.h b/arch/x86/include/asm/io_32.h
index a299900..e16b9db 100644
--- a/arch/x86/include/asm/io_32.h
+++ b/arch/x86/include/asm/io_32.h
@@ -37,9 +37,6 @@
* - Arnaldo Carvalho de Melo <acme@conectiva.com.br>
*/
-#define XQUAD_PORTIO_BASE 0xfe400000
-#define XQUAD_PORTIO_QUAD 0x40000 /* 256k per quad. */
-
#ifdef __KERNEL__
#include <asm-generic/iomap.h>
diff --git a/arch/x86/include/asm/numaq.h b/arch/x86/include/asm/numaq.h
index 9f0a5f5..13370b9 100644
--- a/arch/x86/include/asm/numaq.h
+++ b/arch/x86/include/asm/numaq.h
@@ -33,6 +33,10 @@ extern int get_memcfg_numaq(void);
extern void *xquad_portio;
+#define XQUAD_PORTIO_BASE 0xfe400000
+#define XQUAD_PORTIO_QUAD 0x40000 /* 256k per quad. */
+#define XQUAD_PORT_ADDR(port, quad) (xquad_portio + (XQUAD_PORTIO_QUAD*quad) + port)
+
/*
* SYS_CFG_DATA_PRIV_ADDR, struct eachquadmem, and struct sys_cfg_data are the
*/
diff --git a/arch/x86/pci/numaq_32.c b/arch/x86/pci/numaq_32.c
index 8eb295e..8884a1c 100644
--- a/arch/x86/pci/numaq_32.c
+++ b/arch/x86/pci/numaq_32.c
@@ -8,9 +8,7 @@
#include <asm/apic.h>
#include <asm/mpspec.h>
#include <asm/pci_x86.h>
-
-#define XQUAD_PORTIO_BASE 0xfe400000
-#define XQUAD_PORTIO_QUAD 0x40000 /* 256k per quad. */
+#include <asm/numaq.h>
#define BUS2QUAD(global) (mp_bus_id_to_node[global])
@@ -18,8 +16,6 @@
#define QUADLOCAL2BUS(quad,local) (quad_local_to_mp_bus_id[quad][local])
-#define XQUAD_PORT_ADDR(port, quad) (xquad_portio + (XQUAD_PORTIO_QUAD*quad) + port)
-
#define PCI_CONF1_MQ_ADDRESS(bus, devfn, reg) \
(0x80000000 | (BUS2LOCAL(bus) << 16) | (devfn << 8) | (reg & ~3))
--
1.6.6
next prev parent reply other threads:[~2010-02-05 14:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 14:37 [PATCH 0/7] x86: Merge 32-bit and 64-bit io.h Brian Gerst
2010-02-05 14:37 ` Brian Gerst [this message]
2010-02-05 22:48 ` [tip:x86/io] x86-32: Move XQUAD definitions to numaq.h tip-bot for Brian Gerst
2010-02-05 14:37 ` [PATCH 2/7] x86-32: Remove _local variants of in/out from io_32.h Brian Gerst
2010-02-05 22:49 ` [tip:x86/io] " tip-bot for Brian Gerst
2010-02-05 14:37 ` [PATCH 3/7] x86-64: Reorganize io_64.h Brian Gerst
2010-02-05 22:49 ` [tip:x86/io] " tip-bot for Brian Gerst
2010-02-05 14:37 ` [PATCH 4/7] x86-64: Use BUILDIO in io_64.h Brian Gerst
2010-02-05 22:49 ` [tip:x86/io] " tip-bot for Brian Gerst
2010-02-05 14:37 ` [PATCH 5/7] x86: Clean up mem*io functions Brian Gerst
2010-02-05 22:49 ` [tip:x86/io] " tip-bot for Brian Gerst
2010-02-05 14:37 ` [PATCH 6/7] x86: Simplify flush_write_buffers() Brian Gerst
2010-02-05 22:50 ` [tip:x86/io] " tip-bot for Brian Gerst
2010-02-05 14:37 ` [PATCH 7/7] x86: Merge io.h Brian Gerst
2010-02-05 22:50 ` [tip:x86/io] " tip-bot for Brian Gerst
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=1265380629-3212-2-git-send-email-brgerst@gmail.com \
--to=brgerst@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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
Powered by JetHome