Lines Matching full:these

54 historical accident, these are named byte, word, long and quad accesses.
63 8 bytes at a time. For these devices, the memcpy_toio(),
112 these cases, although only some platforms will honor the relaxed
126 addresses separate to the normal memory address space. Access to these
138 long. These functions are inb(), inw(),
142 Some variants are provided for these functions. Some devices require
171   These are the most generic accessors, providing serialization against other
174   should generally use these for any access to ``__iomem`` pointers.
183   DMA, these "relaxed" versions of the MMIO accessors only serialize against
185   might use these in a particularly performance sensitive fast path, with a
195   These are an alternative to the normal readl()/writel() functions, with almost
200   other architectures, these are simply aliases.
205   These behave in the same way as the ioread32()/iowrite32() family, but with
235   These are low-level MMIO accessors without barriers or byteorder changes and
239   is only safe to use these to access memory behind a device bus but not MMIO
242   memory, so unlike the other functions, these can be used to copy data between
249   architectures, these are mapped to readl()/writel() style accessors
273   these are aliases to the normal inb/outb helpers.
281   These are helpers that access the same address multiple times, usually to copy
283   MMIO accessors, these do not perform a byteswap on big-endian kernels, so the
291 ioremap_*() variants provide a common abstraction around these
366 rarely useful these days, as framebuffer drivers usually perform writes only,
384 require this particular mapping mode to work correctly. These platforms set the
458 higher-level APIs. These APIs may implement platform-specific logic to
502 Not using these wrappers may make drivers unusable on certain platforms with