1 .\" Copyright (c) 2002, 2003 Hiten M. Pandya.
2 .\" All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions, and the following disclaimer,
9 .\" without modification, immediately at the beginning of the file.
10 .\" 2. The name of the author may not be used to endorse or promote products
11 .\" derived from this software without specific prior written permission.
13 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
14 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
15 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
16 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR, CONTRIBUTORS OR THE
17 .\" VOICES IN HITEN PANDYA'S HEAD BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
18 .\" SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
19 .\" TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
20 .\" PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
21 .\" LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
22 .\" NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
23 .\" SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
25 .\" Copyright (c) 1996, 1997, 1998, 2001 The NetBSD Foundation, Inc.
26 .\" All rights reserved.
28 .\" This code is derived from software contributed to The NetBSD Foundation
29 .\" by Jason R. Thorpe of the Numerical Aerospace Simulation Facility,
30 .\" NASA Ames Research Center.
32 .\" Redistribution and use in source and binary forms, with or without
33 .\" modification, are permitted provided that the following conditions
35 .\" 1. Redistributions of source code must retain the above copyright
36 .\" notice, this list of conditions and the following disclaimer.
37 .\" 2. Redistributions in binary form must reproduce the above copyright
38 .\" notice, this list of conditions and the following disclaimer in the
39 .\" documentation and/or other materials provided with the distribution.
40 .\" 3. All advertising materials mentioning features or use of this software
41 .\" must display the following acknowledgment:
42 .\" This product includes software developed by the NetBSD
43 .\" Foundation, Inc. and its contributors.
44 .\" 4. Neither the name of The NetBSD Foundation nor the names of its
45 .\" contributors may be used to endorse or promote products derived
46 .\" from this software without specific prior written permission.
48 .\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS
49 .\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
50 .\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
51 .\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
52 .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
53 .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
54 .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
55 .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
56 .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
57 .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
58 .\" POSSIBILITY OF SUCH DAMAGE.
61 .\" $NetBSD: bus_dma.9,v 1.25 2002/10/14 13:43:16 wiz Exp $
68 .Nm bus_dma_tag_create ,
69 .Nm bus_dma_tag_destroy ,
70 .Nm bus_dmamap_create ,
71 .Nm bus_dmamap_destroy ,
73 .Nm bus_dmamap_load_mbuf ,
74 .Nm bus_dmamap_load_mbuf_sg ,
75 .Nm bus_dmamap_load_uio ,
76 .Nm bus_dmamap_unload ,
78 .Nm bus_dmamem_alloc ,
80 .Nd Bus and Machine Independent DMA Mapping Interface
84 .Fn bus_dma_tag_create "bus_dma_tag_t parent" "bus_size_t alignment" \
85 "bus_size_t boundary" "bus_addr_t lowaddr" "bus_addr_t highaddr" \
86 "bus_dma_filter_t *filtfunc" "void *filtfuncarg" "bus_size_t maxsize" \
87 "int nsegments" "bus_size_t maxsegsz" "int flags" "bus_dma_lock_t *lockfunc" \
88 "void *lockfuncarg" "bus_dma_tag_t *dmat"
90 .Fn bus_dma_tag_destroy "bus_dma_tag_t dmat"
92 .Fn bus_dmamap_create "bus_dma_tag_t dmat" "int flags" "bus_dmamap_t *mapp"
94 .Fn bus_dmamap_destroy "bus_dma_tag_t dmat" "bus_dmamap_t map"
96 .Fn bus_dmamap_load "bus_dma_tag_t dmat" "bus_dmamap_t map" "void *buf" \
97 "bus_size_t buflen" "bus_dmamap_callback_t *callback" "void *callback_arg" \
100 .Fn bus_dmamap_load_mbuf "bus_dma_tag_t dmat" "bus_dmamap_t map" \
101 "struct mbuf *mbuf" "bus_dmamap_callback2_t *callback" "void *callback_arg" \
104 .Fn bus_dmamap_load_mbuf_sg "bus_dma_tag_t dmat" "bus_dmamap_t map" \
105 "struct mbuf *mbuf" "bus_dma_segment_t *segs" "int *nsegs" "int flags"
107 .Fn bus_dmamap_load_uio "bus_dma_tag_t dmat" "bus_dmamap_t map" \
108 "struct uio *uio" "bus_dmamap_callback2_t *callback" "void *callback_arg" \
111 .Fn bus_dmamap_unload "bus_dma_tag_t dmat" "bus_dmamap_t map"
113 .Fn bus_dmamap_sync "bus_dma_tag_t dmat" "bus_dmamap_t map" \
116 .Fn bus_dmamem_alloc "bus_dma_tag_t dmat" "void **vaddr" \
117 "int flags" "bus_dmamap_t *mapp"
119 .Fn bus_dmamem_free "bus_dma_tag_t dmat" "void *vaddr" \
122 Direct Memory Access (DMA) is a method of transferring data
123 without involving the CPU, thus providing higher performance.
124 A DMA transaction can be achieved between device to memory,
125 device to device, or memory to memory.
129 API is a bus, device, and machine-independent (MI) interface to
131 It provides the client with flexibility and simplicity by
132 abstracting machine dependent issues like setting up
133 DMA mappings, handling cache issues, bus specific features
135 .Sh STRUCTURES AND TYPES
136 .Bl -tag -width indent
138 A machine-dependent (MD) opaque type that describes the
139 characteristics of DMA transactions.
140 DMA tags are organized into a hierarchy, with each child
141 tag inheriting the restrictions of its parent.
142 This allows all devices along the path of DMA transactions
143 to contribute to the constraints of those transactions.
144 .It Vt bus_dma_filter_t
145 Client specified address filter having the format:
146 .Bl -tag -width indent
148 .Fn "client_filter" "void *filtarg" "bus_addr_t testaddr"
151 Address filters can be specified during tag creation to allow
152 for devices whose DMA address restrictions cannot be specified
156 is client specified during tag creation to be passed to all
157 invocations of the callback.
160 argument contains a potential starting address of a DMA mapping.
161 The filter function operates on the set of addresses from
164 .Ql trunc_page(testaddr) + PAGE_SIZE - 1 ,
166 The filter function should return zero for any mapping in this range
167 that can be accommodated by the device and non-zero otherwise.
168 .It Vt bus_dma_segment_t
169 A machine-dependent type that describes individual
178 field contains the device visible address of the DMA segment, and
180 contains the length of the DMA segment.
181 Although the DMA segments returned by a mapping call will adhere to
182 all restrictions necessary for a successful DMA operation, some conversion
183 (e.g.\& a conversion from host byte order to the device's byte order) is
184 almost always required when presenting segment information to the device.
186 A machine-dependent opaque type describing an individual mapping.
187 One map is used for each memory allocation that will be loaded.
188 Maps can be reused once they have been unloaded.
189 Multiple maps can be associated with one DMA tag.
190 While the value of the map may evaluate to
192 on some platforms under certain conditions,
193 it should never be assumed that it will be
196 .It Vt bus_dmamap_callback_t
197 Client specified callback for receiving mapping information resulting from
201 .Fn bus_dmamap_load .
202 Callbacks are of the format:
203 .Bl -tag -width indent
205 .Fn "client_callback" "void *callback_arg" "bus_dma_segment_t *segs" \
206 "int nseg" "int error"
211 is the callback argument passed to dmamap load functions.
216 parameters describe an array of
217 .Vt bus_dma_segment_t
218 structures that represent the mapping.
219 This array is only valid within the scope of the callback function.
220 The success or failure of the mapping is indicated by the
223 More information on the use of callbacks can be found in the
224 description of the individual dmamap load functions.
225 .It Vt bus_dmamap_callback2_t
226 Client specified callback for receiving mapping information resulting from
230 .Fn bus_dmamap_load_uio
232 .Fn bus_dmamap_load_mbuf .
234 Callback2s are of the format:
235 .Bl -tag -width indent
237 .Fn "client_callback2" "void *callback_arg" "bus_dma_segment_t *segs" \
238 "int nseg" "bus_size_t mapsize" "int error"
241 Callback2's behavior is the same as
242 .Vt bus_dmamap_callback_t
243 with the addition that the length of the data mapped is provided via
245 .It Vt bus_dmasync_op_t
246 Memory synchronization operation specifier.
247 Bus DMA requires explicit synchronization of memory with its device
248 visible mapping in order to guarantee memory coherency.
251 allows the type of DMA operation that will be or has been performed
252 to be communicated to the system so that the correct coherency measures
254 The operations are represented as bitfield flags that can be combined together,
255 though it only makes sense to combine PRE flags or POST flags, not both.
258 description below for more details on how to use these operations.
260 All operations specified below are performed from the host memory point of view,
261 where a read implies data coming from the device to the host memory, and a write
262 implies data going from the host memory to the device.
263 Alternatively, the operations can be thought of in terms of driver operations,
264 where reading a network packet or storage sector corresponds to a read operation
267 .Bl -tag -width ".Dv BUS_DMASYNC_POSTWRITE"
268 .It Dv BUS_DMASYNC_PREREAD
269 Perform any synchronization required prior to an update of host memory by the
271 .It Dv BUS_DMASYNC_PREWRITE
272 Perform any synchronization required after an update of host memory by the CPU
273 and prior to device access to host memory.
274 .It Dv BUS_DMASYNC_POSTREAD
275 Perform any synchronization required after an update of host memory by the
276 device and prior to CPU access to host memory.
277 .It Dv BUS_DMASYNC_POSTWRITE
278 Perform any synchronization required after the device access to host memory.
280 .It Vt bus_dma_lock_t
281 Client specified lock/mutex manipulation method.
282 This will be called from
283 within busdma whenever a client lock needs to be manipulated.
284 In its current form, the function will be called immediately before
285 the callback for a dma load operation that has been deferred with
287 and immediately after with
289 If the load operation does not need to be deferred, then it
290 will not be called since the function loading the map should
291 be holding the appropriate locks.
292 This method is of the format:
293 .Bl -tag -width indent
295 .Fn "lockfunc" "void *lockfunc_arg" "bus_dma_lock_op_t op"
300 implementations are provided for convenience.
301 .Fn busdma_lock_mutex
302 performs standard mutex operations on the sleep mutex provided via the
305 .Fn bus_dma_tag_create .
307 will generate a system panic if it is called.
308 It is substituted into the tag when
313 .Fn bus_dma_tag_create .
314 .It Vt bus_dma_lock_op_t
315 Operations to be performed by the client-specified
317 .Bl -tag -width ".Dv BUS_DMA_UNLOCK"
319 Acquires and/or locks the client locking primitive.
320 .It Dv BUS_DMA_UNLOCK
321 Releases and/or unlocks the client locking primitive.
325 .Bl -tag -width indent
326 .It Fn bus_dma_tag_create "parent" "alignment" "boundary" "lowaddr" \
327 "highaddr" "*filtfunc" "*filtfuncarg" "maxsize" "nsegments" "maxsegsz" \
328 "flags" "lockfunc" "lockfuncarg" "*dmat"
329 Allocates a device specific DMA tag, and initializes it according to
330 the arguments provided:
331 .Bl -tag -width ".Fa filtfuncarg"
333 Indicates restrictions between the parent bridge, CPU memory, and the
335 Each device must use a master parent tag by calling
336 .Fn bus_get_dma_tag .
338 Alignment constraint, in bytes, of any mappings created using this tag.
339 The alignment must be a power of 2.
340 Hardware that can DMA starting at any address would specify
343 Hardware requiring DMA transfers to start on a multiple of 4K
347 Boundary constraint, in bytes, of the target DMA memory region.
348 The boundary indicates the set of addresses, all multiples of the
349 boundary argument, that cannot be crossed by a single
350 .Vt bus_dma_segment_t .
351 The boundary must be a power of 2 and must be no smaller than the
352 maximum segment size.
354 indicates that there are no boundary restrictions.
355 .It Fa lowaddr , highaddr
356 Bounds of the window of bus address space that
358 be directly accessed by the device.
359 The window contains all addresses greater than lowaddr and
360 less than or equal to highaddr.
361 For example, a device incapable of DMA above 4GB, would specify
363 .Dv BUS_SPACE_MAXADDR
365 .Dv BUS_SPACE_MAXADDR_32BIT .
366 Similarly a device that can only dma to addresses bellow 16MB would
367 specify a highaddr of
368 .Dv BUS_SPACE_MAXADDR
370 .Dv BUS_SPACE_MAXADDR_24BIT .
371 Some implementations requires that some region of device visible
372 address space, overlapping available host memory, be outside the
376 is used to bounce requests that would otherwise conflict with
377 the exclusion window.
379 Optional filter function (may be
381 to be called for any attempt to
382 map memory into the window described by
386 A filter function is only required when the single window described
391 cannot adequately describe the constraints of the device.
392 The filter function will be called for every machine page
393 that overlaps the exclusion window.
395 Argument passed to all calls to the filter function for this tag.
399 Maximum size, in bytes, of the sum of all segment lengths in a given
400 DMA mapping associated with this tag.
402 Number of discontinuities (scatter/gather segments) allowed
403 in a DMA mapped region.
404 If there is no restriction,
405 .Dv BUS_SPACE_UNRESTRICTED
408 Maximum size, in bytes, of a segment in any DMA mapped region associated
413 .Bl -tag -width ".Dv BUS_DMA_ALLOCNOW"
414 .It Dv BUS_DMA_ALLOCNOW
415 Pre-allocate enough resources to handle at least one map load operation on
417 If sufficient resources are not available,
420 This should not be used for tags that only describe buffers that will be
422 .Fn bus_dmamem_alloc .
423 Also, due to resource sharing with other tags, this flag does not guarantee
424 that resources will be allocated or reserved exclusively for this tag.
425 It should be treated only as a minor optimization.
428 Optional lock manipulation function (may be
430 to be called when busdma
431 needs to manipulate a lock on behalf of the client.
438 Optional argument to be passed to the function specified by
441 Pointer to a bus_dma_tag_t where the resulting DMA tag will
447 if sufficient memory is not available for tag creation
448 or allocating mapping resources.
449 .It Fn bus_dma_tag_destroy "dmat"
450 Deallocate the DMA tag
453 .Fn bus_dma_tag_create .
457 if any DMA maps remain associated with
462 .It Fn bus_dmamap_create "dmat" "flags" "*mapp"
463 Allocates and initializes a DMA map.
464 Arguments are as follows:
465 .Bl -tag -width ".Fa nsegments"
469 The value of this argument is currently undefined and should be
475 where the resulting DMA map will be stored.
480 if sufficient memory is not available for creating the
481 map or allocating mapping resources.
482 .It Fn bus_dmamap_destroy "dmat" "map"
483 Frees all resources associated with a given DMA map.
484 Arguments are as follows:
485 .Bl -tag -width ".Fa dmat"
487 DMA tag used to allocate
490 The DMA map to destroy.
495 if a mapping is still active for
497 .It Fn bus_dmamap_load "dmat" "map" "buf" "buflen" "*callback" \
498 "callback_arg" "flags"
499 Creates a mapping in device visible address space of
503 associated with the DMA map
505 This call will always return immediately and will not block for any reason.
506 Arguments are as follows:
507 .Bl -tag -width ".Fa buflen"
509 DMA tag used to allocate
512 A DMA map without a currently active mapping.
514 A kernel virtual address pointer to a contiguous (in KVA) buffer, to be
515 mapped into device visible address space.
517 The size of the buffer.
518 .It Fa callback Fa callback_arg
519 The callback function, and its argument.
520 This function is called once sufficient mapping resources are available for
522 If resources are temporarily unavailable, this function will be deferred until
523 later, but the load operation will still return immediately to the caller.
524 Thus, callers should not assume that the callback will be called before the
525 load returns, and code should be structured appropriately to handle this.
526 See below for specific flags and error codes that control this behavior.
529 .Bl -tag -width ".Dv BUS_DMA_NOWAIT"
530 .It Dv BUS_DMA_NOWAIT
531 The load should not be deferred in case of insufficient mapping resources,
532 and instead should return immediately with an appropriate error.
536 Return values to the caller are as follows:
537 .Bl -tag -width ".Er EINPROGRESS"
539 The callback has been called and completed.
540 The status of the mapping has been delivered to the callback.
542 The mapping has been deferred for lack of resources.
543 The callback will be called as soon as resources are available.
544 Callbacks are serviced in FIFO order.
545 To ensure that ordering is guaranteed, all subsequent load requests will also
546 be deferred until all callbacks have been processed.
548 The load request has failed due to insufficient resources, and the caller
549 specifically used the
553 The load request was invalid.
554 The callback has been called and has been provided the same error.
555 This error value may indicate that
565 argument used to create the dma tag
569 When the callback is called, it is presented with an error value
570 indicating the disposition of the mapping.
571 Error may be one of the following:
572 .Bl -tag -width ".Er EINPROGRESS"
574 The mapping was successful and the
576 callback argument contains an array of
577 .Vt bus_dma_segment_t
578 elements describing the mapping.
579 This array is only valid during the scope of the callback function.
581 A mapping could not be achieved within the segment constraints provided
582 in the tag even though the requested allocation size was less than maxsize.
584 .It Fn bus_dmamap_load_mbuf "dmat" "map" "mbuf" "callback2" "callback_arg" \
586 This is a variation of
588 which maps mbuf chains
592 argument is also passed to the callback routine, which
593 contains the mbuf chain's packet header length.
596 flag is implied, thus no callback deferral will happen.
598 Mbuf chains are assumed to be in kernel virtual address space.
600 Beside the error values listed for
601 .Fn bus_dmamap_load ,
603 will be returned if the size of the mbuf chain exceeds the maximum limit of the
605 .It Fn bus_dmamap_load_mbuf_sg "dmat" "map" "mbuf" "segs" "nsegs" "flags"
607 .Fn bus_dmamap_load_mbuf
608 except that it returns immediately without calling a callback function.
609 It is provided for efficiency.
610 The scatter/gather segment array
612 is provided by the caller and filled in directly by the function.
615 argument is returned with the number of segments filled in.
616 Returns the same errors as
617 .Fn bus_dmamap_load_mbuf .
618 .It Fn bus_dmamap_load_uio "dmat" "map" "uio" "callback2" "callback_arg" "flags"
619 This is a variation of
621 which maps buffers pointed to by
626 argument is also passed to the callback routine, which contains the size of
632 flag is implied, thus no callback deferral will happen.
633 Returns the same errors as
634 .Fn bus_dmamap_load .
640 then it is assumed that the buffer,
643 .Fa "uio->uio_td->td_proc" Ns 's
645 User space memory must be in-core and wired prior to attempting a map
647 Pages may be locked using
649 .It Fn bus_dmamap_unload "dmat" "map"
651 Arguments are as follows:
652 .Bl -tag -width ".Fa dmam"
654 DMA tag used to allocate
657 The DMA map that is to be unloaded.
660 .Fn bus_dmamap_unload
661 will not perform any implicit synchronization of DMA buffers.
662 This must be done explicitly by a call to
664 prior to unloading the map.
665 .It Fn bus_dmamap_sync "dmat" "map" "op"
666 Performs synchronization of a device visible mapping with the CPU visible
667 memory referenced by that mapping.
668 Arguments are as follows:
669 .Bl -tag -width ".Fa dmat"
671 DMA tag used to allocate
674 The DMA mapping to be synchronized.
676 Type of synchronization operation to perform.
677 See the definition of
679 for a description of the acceptable values for
686 is the method used to ensure that CPU's and device's direct
687 memory access (DMA) to shared
689 For example, the CPU might be used to set up the contents of a buffer
690 that is to be made available to a device.
691 To ensure that the data are visible via the device's mapping of that
692 memory, the buffer must be loaded and a DMA sync operation of
693 .Dv BUS_DMASYNC_PREWRITE
695 If later CPU modifies this buffer again, another
696 .Dv BUS_DMASYNC_PREWRITE
697 sync operation must be performed before an additional
698 access to this memory by a device.
699 Conversely, a device updates the memory that is to be read by a CPU.
700 In this case, the buffer must be loaded, and a DMA sync operation of
701 .Dv BUS_DMASYNC_PREREAD
703 The CPU will only be able to see the results of this memory update
704 once the DMA operation has completed and a
705 .Dv BUS_DMASYNC_POSTREAD
706 sync operation has been performed.
708 If read and write operations are not preceded and followed by the
709 appropriate synchronization operations, behavior is undefined.
710 .It Fn bus_dmamem_alloc "dmat" "**vaddr" "flags" "*mapp"
711 Allocates memory that is mapped into KVA at the address returned
714 that is permanently loaded into the newly created
718 Arguments are as follows:
719 .Bl -tag -width ".Fa alignment"
721 DMA tag describing the constraints of the DMA mapping.
723 Pointer to a pointer that will hold the returned KVA mapping of
724 the allocated region.
726 Flags are defined as follows:
727 .Bl -tag -width ".Dv BUS_DMA_NOWAIT"
728 .It Dv BUS_DMA_WAITOK
729 The routine can safely wait (sleep) for resources.
730 .It Dv BUS_DMA_NOWAIT
731 The routine is not allowed to wait for resources.
732 If resources are not available,
735 .It Dv BUS_DMA_COHERENT
736 Attempt to map this memory such that cache sync operations are
737 as cheap as possible.
738 This flag is typically set on memory that will be accessed by both
739 a CPU and a DMA engine, frequently.
740 Use of this flag does not remove the requirement of using
741 bus_dmamap_sync, but it may reduce the cost of performing
745 flag is currently implemented on sparc64 and arm.
747 Causes the allocated memory to be set to all zeros.
752 where the resulting DMA map will be stored.
755 The size of memory to be allocated is
760 The current implementation of
762 will allocate all requests as a single segment.
764 An initial load operation is required to obtain the bus address of the allocated
765 memory, and an unload operation is required before freeing the memory, as
767 .Fn bus_dmamem_free .
768 Maps are automatically handled by this function and should not be explicitly
769 allocated or destroyed.
771 Although an explicit load is not required for each access to the memory
772 referenced by the returned map, the synchronization requirements
775 section still apply and should be used to achieve portability on architecutures
776 without coherent buses.
780 if sufficient memory is not available for completing
782 .It Fn bus_dmamem_free "dmat" "*vaddr" "map"
783 Frees memory previously allocated by
784 .Fn bus_dmamem_alloc .
787 Arguments are as follows:
788 .Bl -tag -width ".Fa vaddr"
792 Kernel virtual address of the memory.
794 DMA map to be invalidated.
798 Behavior is undefined if invalid arguments are passed to
799 any of the above functions.
800 If sufficient resources cannot be allocated for a given
805 routines that are not of type,
807 will return 0 on success or an error
808 code, as discussed above.
812 routines will succeed if provided with valid arguments.
814 Two locking protocols are used by
816 The first is a private global lock that is used to synchronize access to the
817 bounce buffer pool on the architectures that make use of them.
818 This lock is strictly a leaf lock that is only used internally to
820 and is not exposed to clients of the API.
822 The second protocol involves protecting various resources stored in the tag.
825 operations are done through requests from the driver that created the tag,
826 the most efficient way to protect the tag resources is through the lock that
830 acts on its own without being called by the driver, the lock primitive
831 specified in the tag is acquired and released automatically.
832 An example of this is when the
834 callback function is called from a deferred context instead of the driver
836 This means that certain
838 functions must always be called with the same lock held that is specified in the
840 These functions include:
842 .Bl -item -offset indent -compact
846 .Fn bus_dmamap_load_uio
848 .Fn bus_dmamap_load_mbuf
850 .Fn bus_dmamap_load_mbuf_sg
852 .Fn bus_dmamap_unload
857 There is one exception to this rule.
858 It is common practice to call some of these functions during driver start-up
859 without any locks held.
860 So long as there is a guarantee of no possible concurrent use of the tag by
861 different threads during this operation, it is safe to not hold a lock for
866 operations should not be called with the driver lock held, either because
867 they are already protected by an internal lock, or because they might sleep
868 due to memory or resource allocation.
869 The following functions must not be
870 called with any non-sleepable locks held:
872 .Bl -item -offset indent -compact
874 .Fn bus_dma_tag_create
876 .Fn bus_dmamap_create
881 All other functions do not have a locking protocol and can thus be
882 called with or without and system or driver locks held.
891 .%A "Jason R. Thorpe"
892 .%T "A Machine-Independent DMA Framework for NetBSD"
893 .%J "Proceedings of the Summer 1998 USENIX Technical Conference"
894 .%Q "USENIX Association"
900 interface first appeared in
907 for use in the CAM SCSI subsystem.
908 The alterations to the original API were aimed to remove the need for
910 .Vt bus_dma_segment_t
913 while allowing callers to queue up on scarce resources.
917 interface was designed and implemented by
919 of the Numerical Aerospace Simulation Facility, NASA Ames Research Center.
920 Additional input on the
922 design was provided by
924 .An Chris Demetriou ,
936 benefits from the contributions of
937 .An Justin T. Gibbs ,
940 .An Matthew N. Dodd ,
943 .An Jake Burkholder ,
944 .An Takahashi Yoshihiro ,
948 This manual page was written by
951 .An Justin T. Gibbs .