Lines Matching refs:ioremap
39 should call ioremap(). An address suitable for accessing
45 time you call ioremap(), and they can run out unless you
156 operated on an ``__iomem`` token, in particular the ioremap() and
160 While on most architectures, ioremap() creates a page table entry for an
294 ioremap() is the most common mapping type, and is applicable to typical device
299 ioremap()
303 registers. Memory mapped using ioremap() has the following characteristics:
323 On many platforms and buses (e.g. PCI), writes issued through ioremap()
333 Maps I/O memory as normal memory with write combining. Unlike ioremap(),
346 not guaranteed to be ordered with respect to normal ioremap() MMIO register
373 Like ioremap(), but explicitly requests non-posted write semantics. On some
374 architectures and buses, ioremap() mappings have posted write semantics, which
387 selects it where appropriate (see the `Higher-level ioremap abstractions`_
393 supported, and can fall back to ioremap() otherwise. The normal approach to
395 explained in `Accessing the device`_, which works with ioremap() on all
411 ioremap_uc() behaves like ioremap() except that on the x86 architecture without
443 | ioremap() | Device-nGnRE |
449 | ioremap_wt() | (not implemented; fallback to ioremap) |
454 Higher-level ioremap abstractions
457 Instead of using the above raw ioremap() modes, drivers are encouraged to use
459 automatically choose an appropriate ioremap mode on any given bus, allowing for
461 cases. At the time of this writing, the following ioremap() wrappers have such
466 Can automatically select ioremap_np() over ioremap() according to platform