Searched refs:pipelines (Results 1 – 25 of 35) sorted by relevance
12
| /Linux-v5.10/drivers/gpu/drm/arm/display/komeda/ |
| D | komeda_dev.c | 37 komeda_pipeline_dump_register(mdev->pipelines[i], sf); in komeda_register_show()
84 struct komeda_pipeline *pipe = mdev->pipelines[0]; in config_id_show()
176 mdev->pipelines[pipe_id]->of_node = of_node_get(child); in komeda_parse_dt()
181 pipe = mdev->pipelines[pipe_id]; in komeda_parse_dt()
310 komeda_pipeline_destroy(mdev, mdev->pipelines[i]); in komeda_dev_destroy()
311 mdev->pipelines[i] = NULL; in komeda_dev_destroy()
|
| D | komeda_pipeline.c | 38 mdev->pipelines[mdev->n_pipelines] = pipe; in komeda_pipeline_add()
84 temp = mdev->pipelines[id - KOMEDA_COMPONENT_COMPIZ0]; in komeda_pipeline_get_component_pos()
103 temp = mdev->pipelines[id - KOMEDA_COMPONENT_IPS0]; in komeda_pipeline_get_component_pos()
343 pipe = mdev->pipelines[i]; in komeda_assemble_pipelines()
|
| D | komeda_dev.h | 187 struct komeda_pipeline *pipelines[KOMEDA_MAX_PIPELINES]; member
|
| D | komeda_plane.c | 327 pipe = mdev->pipelines[i]; in komeda_kms_add_planes()
|
| D | komeda_private_obj.c | 373 pipe = mdev->pipelines[i]; in komeda_kms_add_private_objs()
|
| D | komeda_crtc.c | 566 master = mdev->pipelines[i]; in komeda_kms_setup_crtcs()
|
| /Linux-v5.10/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 | introduction.rst | 6 complex graphics devices, usually containing programmable pipelines well
|
| /Linux-v5.10/Documentation/userspace-api/media/dvb/ |
| D | legacy_dvb_apis.rst | 16 video should be using the V4L2 and ALSA APIs, and the pipelines should
|
| /Linux-v5.10/drivers/staging/vc04_services/bcm2835-camera/ |
| D | TODO | 4 pipelines, we need to export our buffers through dma-buf so that the
|
| /Linux-v5.10/drivers/media/platform/exynos4-is/ |
| D | media-dev.h | 141 struct list_head pipelines; member
|
| D | media-dev.c | 381 list_add_tail(&p->list, &fmd->pipelines); in fimc_md_pipeline_create()
389 while (!list_empty(&fmd->pipelines)) { in fimc_md_pipelines_free()
392 p = list_entry(fmd->pipelines.next, typeof(*p), list); in fimc_md_pipelines_free()
1446 INIT_LIST_HEAD(&fmd->pipelines); in fimc_md_probe()
|
| /Linux-v5.10/Documentation/admin-guide/media/ |
| 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 | 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
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 | ipu3.rst | 231 The IPU3 ImgU pipelines can be configured using the Media Controller, defined at
443 set of parameters as input. The major stages of pipelines are shown here:
|
| /Linux-v5.10/arch/arm/boot/dts/ |
| D | sun5i-a13.dtsi | 84 allwinner,pipelines = <&fe0>;
|
| D | sun5i-gr8.dtsi | 54 allwinner,pipelines = <&fe0>;
|
| D | sun5i-a10s.dtsi | 72 allwinner,pipelines = <&fe0>;
|
| D | sun8i-v3s.dtsi | 82 allwinner,pipelines = <&mixer0>;
|
| D | sun8i-a23-a33.dtsi | 73 allwinner,pipelines = <&fe0>;
|
| /Linux-v5.10/Documentation/devicetree/bindings/ |
| D | graph.txt | 21 To see how this binding applies to video pipelines, for example, see
|
| /Linux-v5.10/Documentation/devicetree/bindings/display/ti/ |
| D | ti,omap-dss.txt | 88 shifter). The video pipelines for the connectors are formed as follows:
|
| /Linux-v5.10/Documentation/devicetree/bindings/media/ |
| D | video-interfaces.txt | 6 Video data pipelines usually consist of external devices, e.g. camera sensors,
520 The example snippet below describes two data pipelines. ov772x and imx074 are
527 pipelines can be active: ov772x -> ceu0 or imx074 -> csi2 -> ceu0.
|
| /Linux-v5.10/Documentation/userspace-api/media/v4l/ |
| D | open.rst | 44 sub-devices and to configure the pipelines via the
|
| /Linux-v5.10/Documentation/userspace-api/media/mediactl/ |
| D | request-api.rst | 10 modern devices (stateless codecs, complex camera pipelines, ...) and APIs
|
12
