Searched full:pipelines (Results 1 – 22 of 22) sorted by relevance
| /Documentation/devicetree/bindings/display/ |
| D | allwinner,sun4i-a10-display-engine.yaml | 69 allwinner,pipelines:
81 - allwinner,pipelines
102 allwinner,pipelines:
107 allwinner,pipelines:
114 allwinner,pipelines = <&fe0>, <&fe1>;
|
| D | arm,komeda.yaml | 53 The stream IDs for each of the used pipelines, each four IDs for the
|
| /Documentation/gpu/ |
| D | komeda-kms.rst | 79 Benefitting from the modularized architecture, D71 pipelines can be easily
80 adjusted to fit different usages. And D71 has two pipelines, which support two
84 Two pipelines work independently and separately to drive two display outputs.
87 Two pipelines work together to drive only one display output.
212 Sub-pipelines for input and output
215 A complete display pipeline can be easily divided into three sub-pipelines
295 In the following section we'll see these three sub-pipelines will be handled
326 pipelines. Since komeda is not for D71 only but also intended for later products,
375 Komeda has multiple Layer input pipelines, see:
|
| D | automated_testing.rst | 107 created (eg. https://gitlab.freedesktop.org/janedoe/linux/-/pipelines)
158 If a hardware farm is down and thus causing pipelines to fail that would
|
| D | introduction.rst | 6 complex graphics devices, usually containing programmable pipelines well
|
| D | i915.rst | 287 GPGPU pipelines, but not the 3D pipeline.
|
| /Documentation/userspace-api/media/dvb/ |
| D | legacy_dvb_decoder_api.rst | 27 Pipelines should be set up using the :ref:`Media Controller API<media_controller>`.
|
| /Documentation/admin-guide/media/ |
| D | imx.rst | 80 - Many different pipelines can be configured via media controller API,
81 that correspond to the hardware video capture pipelines supported in
86 - Concurrent independent streams, by configuring pipelines to multiple
96 motion compensation modes: low, medium, and high motion. Pipelines are
347 Capture Pipelines
350 The following describe the various use-cases supported by the pipelines.
354 (parallel or mipi csi-2). So these pipelines begin with:
433 pipelines for both sensors. The OV5642 is routed to ipu1_csi0, and
|
| D | qcom_camss.rst | 129 sub-devices allows to create linear media controller pipelines when using two
130 cameras simultaneously. This avoids branches in the pipelines which otherwise
|
| D | ipu3.rst | 233 The IPU3 ImgU pipelines can be configured using the Media Controller, defined at
446 set of parameters as input. The major stages of pipelines are shown here:
|
| /Documentation/devicetree/bindings/arm/mediatek/ |
| D | mediatek,mmsys.yaml | 45 - description: vdosys0 and vdosys1 are 2 display HW pipelines,
|
| /Documentation/devicetree/bindings/media/ |
| D | nxp,imx8-isi.yaml | 13 The Image Sensing Interface (ISI) combines image processing pipelines with
|
| D | video-interfaces.yaml | 14 Video data pipelines usually consist of external devices, e.g. camera sensors,
|
| /Documentation/devicetree/bindings/display/ti/ |
| D | ti,omap-dss.txt | 88 shifter). The video pipelines for the connectors are formed as follows:
|
| /Documentation/devicetree/bindings/display/xlnx/ |
| D | xlnx,zynqmp-dpsub.yaml | 11 implements the display and audio pipelines based on the DisplayPort v1.2
|
| /Documentation/userspace-api/media/mediactl/ |
| D | request-api.rst | 10 modern devices (stateless codecs, complex camera pipelines, ...) and APIs
|
| /Documentation/userspace-api/media/v4l/ |
| D | open.rst | 44 sub-devices and to configure the pipelines via the
|
| D | dev-subdev.rst | 113 Image Format Negotiation on Pipelines
|
| /Documentation/gpu/amdgpu/display/ |
| D | mpo-overview.rst | 12 the graphics/compute pipelines can be put into low-power states. In summary,
|
| /Documentation/driver-api/media/ |
| D | mc-core.rst | 190 Pipelines and media streams
|
| /Documentation/admin-guide/ |
| D | workload-tracing.rst | 123 operating system, pipelines, schedulers, and virtual machines. Please refer
261 memory, network, operating system, pipelines, schedulers, and virtual
|
| /Documentation/arch/sparc/oradax/ |
| D | dax-hv-api.txt | 222 is invalid. However, Pipelines can be extended beyond two CCBs: the sequence would start with a CCB
|