€•™U      Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ&/translations/zh_CN/driver-api/usb/dma”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ&/translations/zh_TW/driver-api/usb/dma”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ&/translations/it_IT/driver-api/usb/dma”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ&/translations/ja_JP/driver-api/usb/dma”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ&/translations/ko_KR/driver-api/usb/dma”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ&/translations/sp_SP/driver-api/usb/dma”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒUSB DMA”h]”hŒUSB DMA”…””}”(hh¨hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh£hžhhŸŒ@/var/lib/git/docbuild/linux/Documentation/driver-api/usb/dma.rst”h KubhŒ	paragraph”“”)”}”(hŒÞIn Linux 2.5 kernels (and later), USB device drivers have additional control
over how DMA may be used to perform I/O operations.  The APIs are detailed
in the kernel usb programming guide (kerneldoc, from the source code).”h]”hŒÞIn Linux 2.5 kernels (and later), USB device drivers have additional control
over how DMA may be used to perform I/O operations.  The APIs are detailed
in the kernel usb programming guide (kerneldoc, from the source code).”…””}”(hh¹hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khh£hžhubh¢)”}”(hhh]”(h§)”}”(hŒAPI overview”h]”hŒAPI overview”…””}”(hhÊhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hhÇhžhhŸh¶h K	ubh¸)”}”(hX  The big picture is that USB drivers can continue to ignore most DMA issues,
though they still must provide DMA-ready buffers (see
Documentation/core-api/dma-api-howto.rst).  That's how they've worked through
the 2.4 (and earlier) kernels, or they can now be DMA-aware.”h]”hX  The big picture is that USB drivers can continue to ignore most DMA issues,
though they still must provide DMA-ready buffers (see
Documentation/core-api/dma-api-howto.rst).  Thatâ€™s how theyâ€™ve worked through
the 2.4 (and earlier) kernels, or they can now be DMA-aware.”…””}”(hhØhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KhhÇhžhubh¸)”}”(hŒDMA-aware usb drivers:”h]”hŒDMA-aware usb drivers:”…””}”(hhæhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KhhÇhžhubhŒbullet_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hŒŠNew calls enable DMA-aware drivers, letting them allocate dma buffers and
manage dma mappings for existing dma-ready buffers (see below).
”h]”h¸)”}”(hŒ‰New calls enable DMA-aware drivers, letting them allocate dma buffers and
manage dma mappings for existing dma-ready buffers (see below).”h]”hŒ‰New calls enable DMA-aware drivers, letting them allocate dma buffers and
manage dma mappings for existing dma-ready buffers (see below).”…””}”(hhÿhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khhûubah}”(h]”h ]”h"]”h$]”h&]”uh1hùhhöhžhhŸh¶h Nubhú)”}”(hŒ¬URBs have an additional "transfer_dma" field, as well as a transfer_flags
bit saying if it's valid.  (Control requests also have "setup_dma", but
drivers must not use it.)
”h]”h¸)”}”(hŒ«URBs have an additional "transfer_dma" field, as well as a transfer_flags
bit saying if it's valid.  (Control requests also have "setup_dma", but
drivers must not use it.)”h]”hŒµURBs have an additional â€œtransfer_dmaâ€ field, as well as a transfer_flags
bit saying if itâ€™s valid.  (Control requests also have â€œsetup_dmaâ€, but
drivers must not use it.)”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hùhhöhžhhŸh¶h Nubhú)”}”(hŒ"usbcore" will map this DMA address, if a DMA-aware driver didn't do
it first and set ``URB_NO_TRANSFER_DMA_MAP``.  HCDs
don't manage dma mappings for URBs.
”h]”h¸)”}”(hŒœ"usbcore" will map this DMA address, if a DMA-aware driver didn't do
it first and set ``URB_NO_TRANSFER_DMA_MAP``.  HCDs
don't manage dma mappings for URBs.”h]”(hŒ\â€œusbcoreâ€ will map this DMA address, if a DMA-aware driver didnâ€™t do
it first and set ”…””}”(hj/  hžhhŸNh NubhŒliteral”“”)”}”(hŒ``URB_NO_TRANSFER_DMA_MAP``”h]”hŒURB_NO_TRANSFER_DMA_MAP”…””}”(hj9  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j7  hj/  ubhŒ-.  HCDs
donâ€™t manage dma mappings for URBs.”…””}”(hj/  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khj+  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hùhhöhžhhŸh¶h Nubhú)”}”(hŒÇThere's a new "generic DMA API", parts of which are usable by USB device
drivers.  Never use dma_set_mask() on any USB interface or device; that
would potentially break all devices sharing that bus.
”h]”h¸)”}”(hŒÆThere's a new "generic DMA API", parts of which are usable by USB device
drivers.  Never use dma_set_mask() on any USB interface or device; that
would potentially break all devices sharing that bus.”h]”hŒÌThereâ€™s a new â€œgeneric DMA APIâ€, parts of which are usable by USB device
drivers.  Never use dma_set_mask() on any USB interface or device; that
would potentially break all devices sharing that bus.”…””}”(hj[  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KhjW  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hùhhöhžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1hôhŸh¶h KhhÇhžhubeh}”(h]”Œapi-overview”ah ]”h"]”Œapi overview”ah$]”h&]”uh1h¡hh£hžhhŸh¶h K	ubh¢)”}”(hhh]”(h§)”}”(hŒEliminating copies”h]”hŒEliminating copies”…””}”(hj‚  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj  hžhhŸh¶h K"ubh¸)”}”(hŒˆIt's good to avoid making CPUs copy data needlessly.  The costs can add up,
and effects like cache-trashing can impose subtle penalties.”h]”hŒŠItâ€™s good to avoid making CPUs copy data needlessly.  The costs can add up,
and effects like cache-trashing can impose subtle penalties.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K$hj  hžhubhõ)”}”(hhh]”(hú)”}”(hXè  If you're doing lots of small data transfers from the same buffer all
the time, that can really burn up resources on systems which use an
IOMMU to manage the DMA mappings.  It can cost MUCH more to set up and
tear down the IOMMU mappings with each request than perform the I/O!

For those specific cases, USB has primitives to allocate less expensive
memory.  They work like kmalloc and kfree versions that give you the right
kind of addresses to store in urb->transfer_buffer and urb->transfer_dma.
You'd also set ``URB_NO_TRANSFER_DMA_MAP`` in urb->transfer_flags::

      void *usb_alloc_coherent (struct usb_device *dev, size_t size,
              int mem_flags, dma_addr_t *dma);

      void usb_free_coherent (struct usb_device *dev, size_t size,
              void *addr, dma_addr_t dma);

Most drivers should **NOT** be using these primitives; they don't need
to use this type of memory ("dma-coherent"), and memory returned from
:c:func:`kmalloc` will work just fine.

The memory buffer returned is "dma-coherent"; sometimes you might need to
force a consistent memory access ordering by using memory barriers.  It's
not using a streaming DMA mapping, so it's good for small transfers on
systems where the I/O would otherwise thrash an IOMMU mapping.  (See
Documentation/core-api/dma-api-howto.rst for definitions of "coherent" and
"streaming" DMA mappings.)

Asking for 1/Nth of a page (as well as asking for N pages) is reasonably
space-efficient.

On most systems the memory returned will be uncached, because the
semantics of dma-coherent memory require either bypassing CPU caches
or using cache hardware with bus-snooping support.  While x86 hardware
has such bus-snooping, many other systems use software to flush cache
lines to prevent DMA conflicts.
”h]”(h¸)”}”(hX  If you're doing lots of small data transfers from the same buffer all
the time, that can really burn up resources on systems which use an
IOMMU to manage the DMA mappings.  It can cost MUCH more to set up and
tear down the IOMMU mappings with each request than perform the I/O!”h]”hX  If youâ€™re doing lots of small data transfers from the same buffer all
the time, that can really burn up resources on systems which use an
IOMMU to manage the DMA mappings.  It can cost MUCH more to set up and
tear down the IOMMU mappings with each request than perform the I/O!”…””}”(hj¥  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K'hj¡  ubh¸)”}”(hX   For those specific cases, USB has primitives to allocate less expensive
memory.  They work like kmalloc and kfree versions that give you the right
kind of addresses to store in urb->transfer_buffer and urb->transfer_dma.
You'd also set ``URB_NO_TRANSFER_DMA_MAP`` in urb->transfer_flags::”h]”(hŒîFor those specific cases, USB has primitives to allocate less expensive
memory.  They work like kmalloc and kfree versions that give you the right
kind of addresses to store in urb->transfer_buffer and urb->transfer_dma.
Youâ€™d also set ”…””}”(hj³  hžhhŸNh Nubj8  )”}”(hŒ``URB_NO_TRANSFER_DMA_MAP``”h]”hŒURB_NO_TRANSFER_DMA_MAP”…””}”(hj»  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j7  hj³  ubhŒ in urb->transfer_flags:”…””}”(hj³  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K,hj¡  ubhŒliteral_block”“”)”}”(hŒÊvoid *usb_alloc_coherent (struct usb_device *dev, size_t size,
        int mem_flags, dma_addr_t *dma);

void usb_free_coherent (struct usb_device *dev, size_t size,
        void *addr, dma_addr_t dma);”h]”hŒÊvoid *usb_alloc_coherent (struct usb_device *dev, size_t size,
        int mem_flags, dma_addr_t *dma);

void usb_free_coherent (struct usb_device *dev, size_t size,
        void *addr, dma_addr_t dma);”…””}”hjÕ  sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1jÓ  hŸh¶h K1hj¡  ubh¸)”}”(hŒ³Most drivers should **NOT** be using these primitives; they don't need
to use this type of memory ("dma-coherent"), and memory returned from
:c:func:`kmalloc` will work just fine.”h]”(hŒMost drivers should ”…””}”(hjå  hžhhŸNh NubhŒstrong”“”)”}”(hŒ**NOT**”h]”hŒNOT”…””}”(hjï  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jí  hjå  ubhŒx be using these primitives; they donâ€™t need
to use this type of memory (â€œdma-coherentâ€), and memory returned from
”…””}”(hjå  hžhhŸNh Nubh)”}”(hŒ:c:func:`kmalloc`”h]”j8  )”}”(hj  h]”hŒ	kmalloc()”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”(Œxref”Œc”Œc-func”eh"]”h$]”h&]”uh1j7  hj  ubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”Œdriver-api/usb/dma”Œ	refdomain”j  Œreftype”Œfunc”Œrefexplicit”‰Œrefwarn”‰Œ	reftarget”Œkmalloc”uh1hhŸh¶h K7hjå  ubhŒ will work just fine.”…””}”(hjå  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K7hj¡  ubh¸)”}”(hX…  The memory buffer returned is "dma-coherent"; sometimes you might need to
force a consistent memory access ordering by using memory barriers.  It's
not using a streaming DMA mapping, so it's good for small transfers on
systems where the I/O would otherwise thrash an IOMMU mapping.  (See
Documentation/core-api/dma-api-howto.rst for definitions of "coherent" and
"streaming" DMA mappings.)”h]”hX•  The memory buffer returned is â€œdma-coherentâ€; sometimes you might need to
force a consistent memory access ordering by using memory barriers.  Itâ€™s
not using a streaming DMA mapping, so itâ€™s good for small transfers on
systems where the I/O would otherwise thrash an IOMMU mapping.  (See
Documentation/core-api/dma-api-howto.rst for definitions of â€œcoherentâ€ and
â€œstreamingâ€ DMA mappings.)”…””}”(hj.  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K;hj¡  ubh¸)”}”(hŒYAsking for 1/Nth of a page (as well as asking for N pages) is reasonably
space-efficient.”h]”hŒYAsking for 1/Nth of a page (as well as asking for N pages) is reasonably
space-efficient.”…””}”(hj<  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KBhj¡  ubh¸)”}”(hX3  On most systems the memory returned will be uncached, because the
semantics of dma-coherent memory require either bypassing CPU caches
or using cache hardware with bus-snooping support.  While x86 hardware
has such bus-snooping, many other systems use software to flush cache
lines to prevent DMA conflicts.”h]”hX3  On most systems the memory returned will be uncached, because the
semantics of dma-coherent memory require either bypassing CPU caches
or using cache hardware with bus-snooping support.  While x86 hardware
has such bus-snooping, many other systems use software to flush cache
lines to prevent DMA conflicts.”…””}”(hjJ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KEhj¡  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hùhjž  hžhhŸh¶h Nubhú)”}”(hXž  Devices on some EHCI controllers could handle DMA to/from high memory.

Unfortunately, the current Linux DMA infrastructure doesn't have a sane
way to expose these capabilities ... and in any case, HIGHMEM is mostly a
design wart specific to x86_32.  So your best bet is to ensure you never
pass a highmem buffer into a USB driver.  That's easy; it's the default
behavior.  Just don't override it; e.g. with ``NETIF_F_HIGHDMA``.

This may force your callers to do some bounce buffering, copying from
high memory to "normal" DMA memory.  If you can come up with a good way
to fix this issue (for x86_32 machines with over 1 GByte of memory),
feel free to submit patches.
”h]”(h¸)”}”(hŒFDevices on some EHCI controllers could handle DMA to/from high memory.”h]”hŒFDevices on some EHCI controllers could handle DMA to/from high memory.”…””}”(hjb  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KKhj^  ubh¸)”}”(hXd  Unfortunately, the current Linux DMA infrastructure doesn't have a sane
way to expose these capabilities ... and in any case, HIGHMEM is mostly a
design wart specific to x86_32.  So your best bet is to ensure you never
pass a highmem buffer into a USB driver.  That's easy; it's the default
behavior.  Just don't override it; e.g. with ``NETIF_F_HIGHDMA``.”h]”(hXX  Unfortunately, the current Linux DMA infrastructure doesnâ€™t have a sane
way to expose these capabilities ... and in any case, HIGHMEM is mostly a
design wart specific to x86_32.  So your best bet is to ensure you never
pass a highmem buffer into a USB driver.  Thatâ€™s easy; itâ€™s the default
behavior.  Just donâ€™t override it; e.g. with ”…””}”(hjp  hžhhŸNh Nubj8  )”}”(hŒ``NETIF_F_HIGHDMA``”h]”hŒNETIF_F_HIGHDMA”…””}”(hjx  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j7  hjp  ubhŒ.”…””}”(hjp  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KMhj^  ubh¸)”}”(hŒïThis may force your callers to do some bounce buffering, copying from
high memory to "normal" DMA memory.  If you can come up with a good way
to fix this issue (for x86_32 machines with over 1 GByte of memory),
feel free to submit patches.”h]”hŒóThis may force your callers to do some bounce buffering, copying from
high memory to â€œnormalâ€ DMA memory.  If you can come up with a good way
to fix this issue (for x86_32 machines with over 1 GByte of memory),
feel free to submit patches.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KShj^  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hùhjž  hžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”ju  jv  uh1hôhŸh¶h K'hj  hžhubeh}”(h]”Œeliminating-copies”ah ]”h"]”Œeliminating copies”ah$]”h&]”uh1h¡hh£hžhhŸh¶h K"ubh¢)”}”(hhh]”(h§)”}”(hŒWorking with existing buffers”h]”hŒWorking with existing buffers”…””}”(hjµ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj²  hžhhŸh¶h KYubh¸)”}”(hX*  Existing buffers aren't usable for DMA without first being mapped into the
DMA address space of the device.  However, most buffers passed to your
driver can safely be used with such DMA mapping.  (See the first section
of Documentation/core-api/dma-api-howto.rst, titled "What memory is DMA-able?")”h]”hX0  Existing buffers arenâ€™t usable for DMA without first being mapped into the
DMA address space of the device.  However, most buffers passed to your
driver can safely be used with such DMA mapping.  (See the first section
of Documentation/core-api/dma-api-howto.rst, titled â€œWhat memory is DMA-able?â€)”…””}”(hjÃ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K[hj²  hžhubhõ)”}”(hhh]”hú)”}”(hX«  When you have the scatterlists which have been mapped for the USB controller,
you could use the new ``usb_sg_*()`` calls, which would turn scatterlist
into URBs::

      int usb_sg_init(struct usb_sg_request *io, struct usb_device *dev,
              unsigned pipe, unsigned period, struct scatterlist *sg,
              int nents, size_t length, gfp_t mem_flags);

      void usb_sg_wait(struct usb_sg_request *io);

      void usb_sg_cancel(struct usb_sg_request *io);

When the USB controller doesn't support DMA, the ``usb_sg_init()`` would try
to submit URBs in PIO way as long as the page in scatterlists is not in the
Highmem, which could be very rare in modern architectures.”h]”(h¸)”}”(hŒ¢When you have the scatterlists which have been mapped for the USB controller,
you could use the new ``usb_sg_*()`` calls, which would turn scatterlist
into URBs::”h]”(hŒdWhen you have the scatterlists which have been mapped for the USB controller,
you could use the new ”…””}”(hjØ  hžhhŸNh Nubj8  )”}”(hŒ``usb_sg_*()``”h]”hŒ
usb_sg_*()”…””}”(hjà  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j7  hjØ  ubhŒ/ calls, which would turn scatterlist
into URBs:”…””}”(hjØ  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K`hjÔ  ubjÔ  )”}”(hX  int usb_sg_init(struct usb_sg_request *io, struct usb_device *dev,
        unsigned pipe, unsigned period, struct scatterlist *sg,
        int nents, size_t length, gfp_t mem_flags);

void usb_sg_wait(struct usb_sg_request *io);

void usb_sg_cancel(struct usb_sg_request *io);”h]”hX  int usb_sg_init(struct usb_sg_request *io, struct usb_device *dev,
        unsigned pipe, unsigned period, struct scatterlist *sg,
        int nents, size_t length, gfp_t mem_flags);

void usb_sg_wait(struct usb_sg_request *io);

void usb_sg_cancel(struct usb_sg_request *io);”…””}”hjø  sbah}”(h]”h ]”h"]”h$]”h&]”jã  jä  uh1jÓ  hŸh¶h KdhjÔ  ubh¸)”}”(hŒÓWhen the USB controller doesn't support DMA, the ``usb_sg_init()`` would try
to submit URBs in PIO way as long as the page in scatterlists is not in the
Highmem, which could be very rare in modern architectures.”h]”(hŒ3When the USB controller doesnâ€™t support DMA, the ”…””}”(hj  hžhhŸNh Nubj8  )”}”(hŒ``usb_sg_init()``”h]”hŒusb_sg_init()”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j7  hj  ubhŒ‘ would try
to submit URBs in PIO way as long as the page in scatterlists is not in the
Highmem, which could be very rare in modern architectures.”…””}”(hj  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KlhjÔ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hùhjÑ  hžhhŸh¶h Nubah}”(h]”h ]”h"]”h$]”h&]”ju  jv  uh1hôhŸh¶h K`hj²  hžhubeh}”(h]”Œworking-with-existing-buffers”ah ]”h"]”Œworking with existing buffers”ah$]”h&]”uh1h¡hh£hžhhŸh¶h KYubeh}”(h]”Œusb-dma”ah ]”h"]”Œusb dma”ah$]”h&]”uh1h¡hhhžhhŸh¶h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h¶uh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¦NŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”Œentry”Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”je  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h¶Œ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(j?  j<  j|  jy  j¯  j¬  j7  j4  uŒ	nametypes”}”(j?  ‰j|  ‰j¯  ‰j7  ‰uh}”(j<  h£jy  hÇj¬  j  j4  j²  uŒfootnote_refs”}”Œcitation_refs”}”Œautofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”Œ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nhžhub.