Messages in this thread | | | Date | Wed, 3 Jun 2015 16:58:24 -0700 | Subject | Re: [PATCH v3 2/6] cleanup IORESOURCE_CACHEABLE vs ioremap() | From | Dan Williams <> |
| |
On Wed, Jun 3, 2015 at 2:34 PM, Dan Williams <dan.j.williams@intel.com> 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@arndb.de>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
| |