[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2060921.TrTof4X6qj@wuerfel>
Date: Wed, 26 Nov 2014 22:32:47 +0100
From: Arnd Bergmann <arnd@...db.de>
To: Dave Gerlach <d-gerlach@...com>
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-omap@...r.kernel.org, linux-arch@...r.kernel.org,
devicetree@...r.kernel.org, Russ Dill <russ.dill@...com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Philipp Zabel <p.zabel@...gutronix.de>,
Shawn Guo <shawn.guo@...escale.com>,
Tony Lindgren <tony@...mide.com>, Anson.Huang@...escale.com,
Russ Dill <Russ.Dill@...com>
Subject: Re: [RFC PATCH 1/2] asm-generic: io: Add exec versions of ioremap
On Wednesday 26 November 2014 15:14:00 Dave Gerlach wrote:
> @@ -66,6 +66,11 @@ extern void ioport_unmap(void __iomem *);
> #define ioremap_wc ioremap_nocache
> #endif
>
> +#ifndef ARCH_HAS_IOREMAP_EXEC
> +#define ioremap_exec ioremap
> +#define ioremap_exec_nocache ioremap_nocache
> +#endif
> +
> #ifdef CONFIG_PCI
> /* Destroy a virtual mapping cookie for a PCI BAR (memory or IO) */
> struct pci_dev;
>
ioremap and ioremap_nocache are the same, and there is no
architecture-independent interface to map an MMIO range as
cached because a lot of architectures can't do that.
Also, I think there are architectures that cannot execute
from uncached memory, so I think adding this as a generic
API is not a good idea.
Arnd
--
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