Dan Williams 92b19ff50e cleanup IORESOURCE_CACHEABLE vs ioremap()
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. Particularly devm_ioremap_resource() never worked as
advertised since it always fell back to plain ioremap().

Clean this up as the new direction we want is to convert
ioremap_<type>() usages to memremap(..., flags).

Suggested-by: Arnd Bergmann <arnd@arndb.de>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
2015-08-10 23:07:06 -04:00
..
2014-04-18 14:20:41 +02:00
2014-11-27 09:32:58 +11:00
2014-12-11 17:48:14 -08:00
2014-08-13 15:13:42 +10:00
2014-09-25 23:14:46 +10:00
2014-11-03 12:12:32 +11:00
2014-11-03 12:12:32 +11:00
2015-02-17 14:34:51 -08:00
2015-07-01 19:40:18 -07:00
2015-03-24 13:15:52 +11:00
2014-12-11 17:48:14 -08:00
2014-09-25 23:14:41 +10:00
2014-08-06 13:04:32 +02:00
2015-04-07 17:15:13 +10:00
2015-06-24 17:49:38 -07:00
2015-05-14 16:59:21 +10:00