| /linux-6.1.9/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
|
| /linux-6.1.9/drivers/gpu/drm/arm/display/komeda/ |
| D | komeda_dev.c | 37 komeda_pipeline_dump_register(mdev->pipelines[i], sf); in komeda_register_show()
73 struct komeda_pipeline *pipe = mdev->pipelines[0]; in config_id_show()
164 mdev->pipelines[pipe_id]->of_node = of_node_get(child); in komeda_parse_dt()
169 pipe = mdev->pipelines[pipe_id]; in komeda_parse_dt()
297 komeda_pipeline_destroy(mdev, mdev->pipelines[i]); in komeda_dev_destroy()
298 mdev->pipelines[i] = NULL; in komeda_dev_destroy()
|
| D | komeda_pipeline.c | 40 mdev->pipelines[mdev->n_pipelines] = pipe; in komeda_pipeline_add()
87 temp = mdev->pipelines[id - KOMEDA_COMPONENT_COMPIZ0]; in komeda_pipeline_get_component_pos()
106 temp = mdev->pipelines[id - KOMEDA_COMPONENT_IPS0]; in komeda_pipeline_get_component_pos()
350 pipe = mdev->pipelines[i]; in komeda_assemble_pipelines()
|
| D | komeda_dev.h | 185 struct komeda_pipeline *pipelines[KOMEDA_MAX_PIPELINES]; member
|
| D | komeda_plane.c | 325 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 | 574 master = mdev->pipelines[i]; in komeda_kms_setup_crtcs()
|
| /linux-6.1.9/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-6.1.9/drivers/staging/media/atomisp/ |
| D | notes.txt | 28 this means that unlike in fixed pipelines the soft pipelines
|
| D | TODO | 185 20. Remove the logic which sets up pipelines inside it, moving it to
|
| /linux-6.1.9/drivers/staging/vc04_services/bcm2835-camera/ |
| D | TODO | 4 pipelines, we need to export our buffers through dma-buf so that the
|
| /linux-6.1.9/drivers/media/platform/samsung/exynos4-is/ |
| D | media-dev.h | 146 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()
1444 INIT_LIST_HEAD(&fmd->pipelines); in fimc_md_probe()
|
| /linux-6.1.9/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
|
| /linux-6.1.9/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>;
|
| /linux-6.1.9/Documentation/devicetree/bindings/display/xlnx/ |
| D | xlnx,zynqmp-dpsub.yaml | 11 implements the display and audio pipelines based on the DisplayPort v1.2
|
| /linux-6.1.9/Documentation/devicetree/bindings/display/ti/ |
| D | ti,omap-dss.txt | 88 shifter). The video pipelines for the connectors are formed as follows:
|
| /linux-6.1.9/Documentation/devicetree/bindings/media/ |
| D | video-interfaces.yaml | 14 Video data pipelines usually consist of external devices, e.g. camera sensors,
|
| /linux-6.1.9/Documentation/userspace-api/media/mediactl/ |
| D | request-api.rst | 10 modern devices (stateless codecs, complex camera pipelines, ...) and APIs
|
| /linux-6.1.9/Documentation/userspace-api/media/v4l/ |
| D | open.rst | 44 sub-devices and to configure the pipelines via the
|