Lines Matching refs:it

112 GFP_ATOMIC to prevent blocking, or if it's permitted (not
131 memory back to the pool before you destroy it.
143 Returns: 1 if it can and 0 if it can't.
154 streaming and coherent DMA mask parameters if it is.
162 parameters if it is.
170 parameters if it is.
184 wish to take advantage of it, you should issue a dma_set_mask()
195 Maps a piece of processor virtual memory so it can be accessed by the
210 capability, it will fail if the user tries to map a non-physically
212 this API should be obtained from sources which guarantee it to be
238 requirement.  Therefore, it is recommended that driver writers who
244 of the memory region by the software and before it is handed off to
247 may write to it at any point, it should be DMA_BIDIRECTIONAL (see
253 to it at any point, it should be DMA_BIDIRECTIONAL (see below).
255 DMA_BIDIRECTIONAL requires special handling: it means that the driver
257 device and also isn't sure if the device will also modify it.  Thus,
282 and <size> parameters are provided to do partial page mapping, it is
304 Please note that the sg cannot be mapped again if it has been mapped once.
307 As with the other mapping interfaces, dma_map_sg() can fail. When it
327 physically contiguous) and returns the actual number of sg entries it
457 choose to return either consistent or non-consistent memory as it sees
460 driver should it choose to return non-consistent memory.
462 Note: where the platform can return consistent memory, it will
486 line, but it will guarantee that one or more cache lines fit exactly
505 it's asked for coherent memory for this device.
532 it's out of memory in the declared region.
542 isn't prepared to handle this contingency, it should not specify
566 (dma_alloc_coherent() will hand out the first free region it finds).
581 the advent of hardware IOMMUs it becomes more and more important that drivers
587 violations. If your architecture supports it you can select the "Enable
589 option has a performance impact. Do not enable it in production kernels.
593 error it prints a warning message with some details into your kernel log. An
641 				will print a warning for every error it finds
643 				option, as it can easily flood your logs.
647 				happen when it runs out of memory or if it was
655 				before it stops. This number is initialized to
664 				because it is not longer reliable.
677 If you have this code compiled into your kernel it will be enabled by default.
680 Notice that you can not enable it again at runtime. You have to reboot to do
688 When the code disables itself at runtime this is most likely because it ran
690 of preallocated entries is defined per architecture. If it is too low for you