Searched refs:mem2mem (Results 1 – 24 of 24) sorted by relevance
| /Linux-v5.4/Documentation/devicetree/bindings/dma/ |
| D | stm32-dmamux.txt | 38 st,mem2mem;
58 st,mem2mem;
|
| D | stm32-dma.txt | 18 - st,mem2mem: boolean; if defined, it indicates that the controller supports
36 st,mem2mem;
|
| /Linux-v5.4/Documentation/media/kapi/ |
| D | v4l2-mem2mem.rst | 6 .. kernel-doc:: include/media/v4l2-mem2mem.h
|
| D | v4l2-core.rst | 23 v4l2-mem2mem
|
| D | v4l2-dev.rst | 49 …default), set to ``VFL_DIR_TX`` for output devices and ``VFL_DIR_M2M`` for mem2mem (codec) devices.
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | devices.rst | 24 dev-mem2mem
|
| D | pixfmt-compressed.rst | 67 (using the :ref:`mem2mem` and :ref:`media-request-api`).
117 MPEG-2 pipeline (using the :ref:`mem2mem` and :ref:`media-request-api`).
160 VP8 pipeline (using the :ref:`mem2mem` and :ref:`media-request-api`).
|
| D | vidioc-decoder-cmd.rst | 59 started yet. Applies to both queues of mem2mem decoders.
64 queues of mem2mem decoders.
67 introduced in Linux 3.3. They are, however, mandatory for stateful mem2mem decoders
|
| D | vidioc-qbuf.rst | 126 For :ref:`memory-to-memory devices <mem2mem>` you can specify the
192 ``VIDIOC_DQBUF`` returns this on an empty capture queue for mem2mem
|
| D | vidioc-encoder-cmd.rst | 117 encoder is already stopped, this command does nothing. mem2mem
|
| D | pixfmt-v4l2.rst | 44 inside the stream, when fed to a stateful mem2mem decoder, the fields
|
| D | buffer.rst | 614 - Last buffer produced by the hardware. mem2mem codec drivers set
658 OUTPUT buffer. This flag applies only to mem2mem devices.
|
| /Linux-v5.4/drivers/media/v4l2-core/ |
| D | Makefile | 23 obj-$(CONFIG_V4L2_MEM2MEM_DEV) += v4l2-mem2mem.o
|
| D | Kconfig | 48 # Used by drivers that need v4l2-mem2mem.ko
|
| /Linux-v5.4/arch/arm/boot/dts/ |
| D | stm32h743.dtsi | 247 st,mem2mem;
265 st,mem2mem;
|
| D | stm32f746.dtsi | 619 st,mem2mem;
|
| D | stm32mp157c.dtsi | 965 st,mem2mem;
982 st,mem2mem;
|
| D | stm32f429.dtsi | 738 st,mem2mem;
|
| /Linux-v5.4/drivers/dma/ |
| D | stm32-dma.c | 211 bool mem2mem; member
1309 dmadev->mem2mem = of_property_read_bool(pdev->dev.of_node, in stm32_dma_probe()
1343 if (dmadev->mem2mem) { in stm32_dma_probe()
|
| /Linux-v5.4/Documentation/media/uapi/mediactl/ |
| D | request-api.rst | 94 For :ref:`memory-to-memory devices <mem2mem>` you can use requests only for
155 For use-cases such as :ref:`codecs <mem2mem>`, the request API can be used
|
| /Linux-v5.4/Documentation/driver-api/dmaengine/ |
| D | provider.rst | 79 These were just the general memory-to-memory (also called mem2mem) or
125 (i.e. excluding mem2mem transfers)
211 - While in the mem2mem case we were having two distinct types to
|
| /Linux-v5.4/drivers/media/ |
| D | Kconfig | 165 # V4L platform/mem2mem drivers
|
| /Linux-v5.4/Documentation/media/v4l-drivers/ |
| D | imx.rst | 99 VDIC from memory buffers via a output/mem2mem devices.
341 or mem2mem device node. With this pipeline, the VDIC can also operate
343 frames from memory buffers. Note that an output or mem2mem device
|
| /Linux-v5.4/drivers/media/platform/ |
| D | Kconfig | 323 This v4l2 mem2mem driver is a 2D blitter for STMicroelectronics SoC.
389 tristate "SuperH VEU mem2mem video processing driver"
|
