On Wed, Jul 1, 2015 at 8:23 AM, Christoph Hellwig <hch(a)lst.de> wrote:
> One useful feature of the ifdef mess as implemented in the patch
> that you could test for whether ioremap_cache() is actually
> implemented or falls back to default ioremap(). I think for
> completeness archs should publish an ioremap type capabilities mask
> for drivers that care... (I can imagine pmem caring), or default to
> being permissive if something like IOREMAP_STRICT is not set. There's
> also the wrinkle of archs that can only support certain types of
> mappings at a given alignment.
I think doing this at runtime might be a better idea. E.g. a
ioremap_flags with the CACHED argument will return -EOPNOTSUP unless
actually implemented. On various architectures different CPUs or
boards will have different capabilities in this area.
So it would be the responsibility of the caller to fall back from
ioremap(..., CACHED) to ioremap(..., UNCACHED)?
I.e. all drivers using it should be changed...
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert(a)linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like
-- Linus Torvalds