[PATCH v9 01/12] Fix ioport_map() for !CONFIG_GENERIC_IOMAP cases.

Liviu Dudau Liviu.Dudau at arm.com
Tue Aug 12 09:25:14 PDT 2014

The inline version of ioport_map() that gets used when !CONFIG_GENERIC_IOMAP
is wrong. It returns a mapped (i.e. virtual) address that can start from
zero and completely ignores the PCI_IOBASE and IO_SPACE_LIMIT that most
architectures that use !CONFIG_GENERIC_MAP define.

Signed-off-by: Liviu Dudau <Liviu.Dudau at arm.com>
Acked-by: Arnd Bergmann <arnd at arndb.de>
Tested-by: Tanmay Inamdar <tinamdar at apm.com>
 include/asm-generic/io.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/asm-generic/io.h b/include/asm-generic/io.h
index 975e1cc..2e2161b 100644
--- a/include/asm-generic/io.h
+++ b/include/asm-generic/io.h
@@ -331,7 +331,7 @@ static inline void iounmap(void __iomem *addr)
 static inline void __iomem *ioport_map(unsigned long port, unsigned int nr)
-	return (void __iomem *) port;
+	return (void __iomem *)(PCI_IOBASE + (port & IO_SPACE_LIMIT));
 static inline void ioport_unmap(void __iomem *p)

More information about the linux-arm-kernel mailing list