Re: [PATCH v3 2/6] cleanup IORESOURCE_CACHEABLE vs ioremap()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Jun 3, 2015 at 2:34 PM, Dan Williams <dan.j.williams@xxxxxxxxx> wrote:
> Quoting Arnd:
>     I was thinking the opposite approach and basically removing all uses
>     of IORESOURCE_CACHEABLE from the kernel. There are only a handful of
>     them.and we can probably replace them all with hardcoded
>     ioremap_cached() calls in the cases they are actually useful.
>
> All existing usages of IORESOURCE_CACHEABLE call ioremap() instead of
> ioremap_nocache() if the resource is cacheable, however ioremap() is
> uncached by default.  Clearly none of the existing usages care about the
> cacheability, so let's clean that up before introducing generic
> ioremap_cache() support across architectures.
>
> Suggested-by: Arnd Bergmann <arnd@xxxxxxxx>

Signed-off-by: Dan Williams <dan.j.williams@xxxxxxxxx>

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]