[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <cover.1327877053.git.mst@redhat.com>
Date: Mon, 30 Jan 2012 14:18:25 +0200
From: "Michael S. Tsirkin" <mst@...hat.com>
To: Kevin Cernekee <cernekee@...il.com>
Cc: Ralf Baechle <ralf@...ux-mips.org>,
Paul Mundt <lethal@...ux-sh.org>,
Arnd Bergmann <arnd@...db.de>,
"Michael S. Tsirkin" <mst@...hat.com>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
Myron Stowe <myron.stowe@...hat.com>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
Lucas De Marchi <lucas.demarchi@...fusion.mobi>,
Dmitry Kasatkin <dmitry.kasatkin@...el.com>,
James Morris <jmorris@...ei.org>,
"John W. Linville" <linville@...driver.com>,
Michael Witten <mfwitten@...il.com>, linux-mips@...ux-mips.org,
linux-kernel@...r.kernel.org, linux-sh@...r.kernel.org,
linux-arch@...r.kernel.org
Subject: [PATCH 0/3] arch: fix ioport mapping on mips,sh
Kevin Cernekee reported that recent cleanup
that replaced pci_iomap with a generic function
failed to take into account the differences
in io port handling on mips and sh architectures.
Rather than revert the changes reintroducing the
code duplication, this patchset fixes this
by adding ability for architectures to override
ioport mapping for pci devices.
I put this in my tree that feeds into linux-next
and intend to ask Linus to pull this fix if this
doesn't cause any issues and there are no objections.
The patches were tested on x86 and compiled on mips and sh.
Would appreciate reviews/acks/testing reports.
Michael S. Tsirkin (3):
lib: add NO_GENERIC_PCI_IOPORT_MAP
mips: use the the PCI controller's io_map_base
sh: use the the PCI channels's io_map_base
arch/mips/Kconfig | 1 +
arch/mips/lib/iomap-pci.c | 4 ++--
arch/sh/Kconfig | 1 +
arch/sh/drivers/pci/pci.c | 4 ++--
include/asm-generic/pci_iomap.h | 5 +++++
lib/Kconfig | 3 +++
lib/pci_iomap.c | 12 +++++++++++-
7 files changed, 25 insertions(+), 5 deletions(-)
--
1.7.8.2.325.g247f9
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists