Searched refs:mem2mem (Results 1 – 24 of 24) sorted by relevance
| /Linux-v6.1/Documentation/driver-api/media/ |
| D | v4l2-mem2mem.rst | 6 .. kernel-doc:: include/media/v4l2-mem2mem.h
|
| D | v4l2-core.rst | 22 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-v6.1/drivers/media/platform/st/sti/bdisp/ |
| D | Kconfig | 10 This v4l2 mem2mem driver is a 2D blitter for STMicroelectronics SoC.
|
| /Linux-v6.1/Documentation/userspace-api/media/v4l/ |
| D | devices.rst | 17 dev-mem2mem
|
| D | vidioc-encoder-cmd.rst | 58 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
|
| D | vidioc-decoder-cmd.rst | 51 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
|
| D | vidioc-qbuf.rst | 119 For :ref:`memory-to-memory devices <mem2mem>` you can specify the
184 ``VIDIOC_DQBUF`` returns this on an empty capture queue for mem2mem
|
| D | pixfmt-v4l2.rst | 37 inside the stream, when fed to a stateful mem2mem decoder, the fields
41 For compressed formats on the CAPTURE side of a stateful mem2mem
|
| D | pixfmt-compressed.rst | 206 HEVC pipeline (using the :ref:`mem2mem` and :ref:`media-request-api`).
|
| D | buffer.rst | 601 - Last buffer produced by the hardware. mem2mem codec drivers set
645 OUTPUT buffer. This flag applies only to mem2mem devices.
|
| /Linux-v6.1/drivers/media/v4l2-core/ |
| D | Makefile | 32 obj-$(CONFIG_V4L2_MEM2MEM_DEV) += v4l2-mem2mem.o
|
| D | Kconfig | 51 # Used by drivers that need v4l2-mem2mem.ko
|
| /Linux-v6.1/drivers/media/platform/nxp/ |
| D | Kconfig | 18 # mem2mem drivers
|
| /Linux-v6.1/Documentation/admin-guide/media/ |
| D | platform-cardlist.rst | 60 sh_veu SuperH VEU mem2mem video processing
|
| D | imx.rst | 99 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-v6.1/arch/arm/boot/dts/ |
| D | stm32mp131.dtsi | 201 st,mem2mem;
219 st,mem2mem;
|
| D | stm32h743.dtsi | 268 st,mem2mem;
286 st,mem2mem;
|
| D | stm32f746.dtsi | 562 st,mem2mem;
|
| D | stm32f429.dtsi | 696 st,mem2mem;
|
| D | stm32mp151.dtsi | 1046 st,mem2mem;
1064 st,mem2mem;
|
| /Linux-v6.1/Documentation/userspace-api/media/mediactl/ |
| D | request-api.rst | 71 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-v6.1/drivers/dma/ |
| D | stm32-dma.c | 232 bool mem2mem; member
1599 dmadev->mem2mem = of_property_read_bool(pdev->dev.of_node, in stm32_dma_probe()
1644 if (dmadev->mem2mem) { in stm32_dma_probe()
|
| /Linux-v6.1/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)
230 - While in the mem2mem case we were having two distinct types to
|
