Searched refs:pipelines (Results 1 – 23 of 23) sorted by relevance
| /Linux-v4.19/Documentation/media/uapi/dvb/ |
| D | legacy_dvb_apis.rst | 16 video should be using the V4L2 and ALSA APIs, and the pipelines should
|
| /Linux-v4.19/drivers/staging/vc04_services/bcm2835-camera/ |
| D | TODO | 4 pipelines, we need to export our buffers through dma-buf so that the
|
| /Linux-v4.19/drivers/media/platform/exynos4-is/ |
| D | media-dev.h | 156 struct list_head pipelines; member
|
| D | media-dev.c | 369 list_add_tail(&p->list, &fmd->pipelines); in fimc_md_pipeline_create()
377 while (!list_empty(&fmd->pipelines)) { in fimc_md_pipelines_free()
380 p = list_entry(fmd->pipelines.next, typeof(*p), list); in fimc_md_pipelines_free()
1426 INIT_LIST_HEAD(&fmd->pipelines); in fimc_md_probe()
|
| /Linux-v4.19/Documentation/devicetree/bindings/media/ |
| D | video-interfaces.txt | 6 Video data pipelines usually consist of external devices, e.g. camera sensors,
154 The example snippet below describes two data pipelines. ov772x and imx074 are
161 pipelines can be active: ov772x -> ceu0 or imx074 -> csi2 -> ceu0.
|
| /Linux-v4.19/Documentation/media/v4l-drivers/ |
| D | qcom_camss.rst | 127 sub-devices allows to create linear media controller pipelines when using two
128 cameras simultaneously. This avoids branches in the pipelines which otherwise
|
| D | imx.rst | 78 - Many different pipelines can be configured via media controller API,
79 that correspond to the hardware video capture pipelines supported in
84 - Concurrent independent streams, by configuring pipelines to multiple
397 The following describe the various use-cases supported by the pipelines.
401 (parallel or mipi csi-2). So these pipelines begin with:
480 pipelines for both sensors. The OV5642 is routed to ipu1_csi0, and
|
| /Linux-v4.19/arch/arm/boot/dts/ |
| D | sun5i-a13.dtsi | 88 allwinner,pipelines = <&fe0>;
|
| D | sun5i-gr8.dtsi | 54 allwinner,pipelines = <&fe0>;
|
| D | sun5i-a10s.dtsi | 76 allwinner,pipelines = <&fe0>;
|
| D | sun8i-v3s.dtsi | 66 allwinner,pipelines = <&mixer0>;
|
| D | sun8i-a33.dtsi | 164 allwinner,pipelines = <&fe0>;
|
| D | sun8i-r40.dtsi | 106 allwinner,pipelines = <&mixer0>, <&mixer1>;
|
| D | sunxi-h3-h5.dtsi | 110 allwinner,pipelines = <&mixer0>;
|
| D | sun8i-a83t.dtsi | 186 allwinner,pipelines = <&mixer0>, <&mixer1>;
|
| D | sun4i-a10.dtsi | 183 allwinner,pipelines = <&fe0>, <&fe1>;
|
| D | sun9i-a80.dtsi | 253 allwinner,pipelines = <&fe0>, <&fe1>;
|
| D | sun7i-a20.dtsi | 245 allwinner,pipelines = <&fe0>, <&fe1>;
|
| D | sun6i-a31.dtsi | 263 allwinner,pipelines = <&fe0>, <&fe1>;
|
| /Linux-v4.19/Documentation/devicetree/bindings/display/ti/ |
| D | ti,omap-dss.txt | 88 shifter). The video pipelines for the connectors are formed as follows:
|
| /Linux-v4.19/Documentation/devicetree/bindings/ |
| D | graph.txt | 21 To see how this binding applies to video pipelines, for example, see
|
| /Linux-v4.19/Documentation/gpu/ |
| D | introduction.rst | 6 complex graphics devices, usually containing programmable pipelines well
|
| /Linux-v4.19/Documentation/devicetree/bindings/display/sunxi/ |
| D | sun4i-drm.txt | 407 - allwinner,pipelines: list of phandle to the display engine
607 allwinner,pipelines = <&fe0>;
|
