Home
last modified time | relevance | path

Searched refs:mem2mem (Results 1 – 23 of 23) sorted by relevance

/linux/Documentation/driver-api/media/
H A Dv4l2-mem2mem.rst6 .. kernel-doc:: include/media/v4l2-mem2mem.h
H A Dv4l2-core.rst21 v4l2-mem2mem
H A Dv4l2-dev.rst49 …default), set to ``VFL_DIR_TX`` for output devices and ``VFL_DIR_M2M`` for mem2mem (codec) devices.
/linux/drivers/media/platform/st/sti/bdisp/
H A DKconfig10 This v4l2 mem2mem driver is a 2D blitter for STMicroelectronics SoC.
/linux/Documentation/userspace-api/media/v4l/
H A Ddevices.rst17 dev-mem2mem
H A Dvidioc-encoder-cmd.rst58 started yet. Applies to both queues of mem2mem encoders.
63 mem2mem encoders.
66 introduced in Linux 2.6.21. They are, however, mandatory for stateful mem2mem
H A Dvidioc-decoder-cmd.rst51 started yet. Applies to both queues of mem2mem decoders.
56 queues of mem2mem decoders.
59 introduced in Linux 3.3. They are, however, mandatory for stateful mem2mem decoders
H A Dvidioc-qbuf.rst119 For :ref:`memory-to-memory devices <mem2mem>` you can specify the
184 ``VIDIOC_DQBUF`` returns this on an empty capture queue for mem2mem
H A Dpixfmt-v4l2.rst37 inside the stream, when fed to a stateful mem2mem decoder, the fields
41 For compressed formats on the CAPTURE side of a stateful mem2mem
H A Dpixfmt-compressed.rst211 HEVC pipeline (using the :ref:`mem2mem` and :ref:`media-request-api`).
H A Dbuffer.rst596 - Last buffer produced by the hardware. mem2mem codec drivers set
640 OUTPUT buffer. This flag applies only to mem2mem devices.
/linux/drivers/media/v4l2-core/
H A DMakefile33 obj-$(CONFIG_V4L2_MEM2MEM_DEV) += v4l2-mem2mem.o
H A DKconfig51 # Used by drivers that need v4l2-mem2mem.ko
/linux/drivers/media/platform/nxp/
H A DKconfig44 # mem2mem drivers
/linux/Documentation/admin-guide/media/
H A Dplatform-cardlist.rst59 sh_veu SuperH VEU mem2mem video processing
H A Dimx.rst99 VDIC from memory buffers via a output/mem2mem devices.
286 or mem2mem device node. With this pipeline, the VDIC can also operate
288 frames from memory buffers. Note that an output or mem2mem device
/linux/Documentation/userspace-api/media/mediactl/
H A Drequest-api.rst71 For :ref:`memory-to-memory devices <mem2mem>` you can use requests only for
132 For use-cases such as :ref:`codecs <mem2mem>`, the request API can be used
/linux/arch/arm/boot/dts/st/
H A Dstm32h743.dtsi268 st,mem2mem;
286 st,mem2mem;
H A Dstm32f746.dtsi663 st,mem2mem;
H A Dstm32mp131.dtsi715 st,mem2mem;
733 st,mem2mem;
H A Dstm32f429.dtsi727 st,mem2mem;
/linux/drivers/dma/stm32/
H A Dstm32-dma.c231 bool mem2mem; member
1594 dmadev->mem2mem = of_property_read_bool(pdev->dev.of_node, in stm32_dma_probe()
1639 if (dmadev->mem2mem) { in stm32_dma_probe()
/linux/Documentation/driver-api/dmaengine/
H A Dprovider.rst79 These were just the general memory-to-memory (also called mem2mem) or
125 (i.e. excluding mem2mem transfers)
230 - While in the mem2mem case we were having two distinct types to