Home
last modified time | relevance | path

Searched refs:pipelines (Results 1 – 25 of 53) sorted by relevance

123

/OK3568_Linux_fs/kernel/drivers/gpu/drm/arm/display/komeda/
H A Dkomeda_dev.c37 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()
H A Dkomeda_pipeline.c38 mdev->pipelines[mdev->n_pipelines] = pipe; in komeda_pipeline_add()
85 temp = mdev->pipelines[id - KOMEDA_COMPONENT_COMPIZ0]; in komeda_pipeline_get_component_pos()
104 temp = mdev->pipelines[id - KOMEDA_COMPONENT_IPS0]; in komeda_pipeline_get_component_pos()
347 pipe = mdev->pipelines[i]; in komeda_assemble_pipelines()
H A Dkomeda_dev.h187 struct komeda_pipeline *pipelines[KOMEDA_MAX_PIPELINES]; member
H A Dkomeda_plane.c333 pipe = mdev->pipelines[i]; in komeda_kms_add_planes()
H A Dkomeda_private_obj.c373 pipe = mdev->pipelines[i]; in komeda_kms_add_private_objs()
/OK3568_Linux_fs/kernel/Documentation/gpu/
H A Dkomeda-kms.rst79 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:
/OK3568_Linux_fs/buildroot/package/gstreamer1/gst1-interpipe/
H A DConfig.in8 between two independent pipelines.
/OK3568_Linux_fs/yocto/meta-openembedded/meta-multimedia/recipes-support/gst-instruments/
H A Dgst-instruments_git.bb1 SUMMARY = "Profiling utilities for GStreamer 1.0 pipelines"
/OK3568_Linux_fs/yocto/poky/meta/recipes-extended/libpipeline/
H A Dlibpipeline_1.5.5.bb2 DESCRIPTION = "This is a C library for setting up and running pipelines of processes, \
/OK3568_Linux_fs/yocto/poky/meta/recipes-extended/bash/bash/
H A Dexecute_cmd.patch15 enabled, execute the last element of non-async pipelines in the
/OK3568_Linux_fs/kernel/Documentation/userspace-api/media/dvb/
H A Dlegacy_dvb_apis.rst16 video should be using the V4L2 and ALSA APIs, and the pipelines should
/OK3568_Linux_fs/kernel/drivers/staging/vc04_services/bcm2835-camera/
H A DTODO4 pipelines, we need to export our buffers through dma-buf so that the
/OK3568_Linux_fs/buildroot/package/pipewire/
H A DConfig.in10 multimedia pipelines.
/OK3568_Linux_fs/kernel/drivers/media/platform/exynos4-is/
H A Dmedia-dev.h141 struct list_head pipelines; member
H A Dmedia-dev.c381 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()
1442 INIT_LIST_HEAD(&fmd->pipelines); in fimc_md_probe()
/OK3568_Linux_fs/buildroot/package/qpdf/
H A D0002-Fix-some-pipelines-to-be-safe-if-downstream-write-fails.patch4 Subject: [PATCH] Fix some pipelines to be safe if downstream write fails (fuzz
/OK3568_Linux_fs/kernel/Documentation/admin-guide/media/
H A Dqcom_camss.rst129 sub-devices allows to create linear media controller pipelines when using two
130 cameras simultaneously. This avoids branches in the pipelines which otherwise
H A Dimx.rst80 - 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
/OK3568_Linux_fs/buildroot/package/libcamera/
H A DConfig.in72 Pipeline for simple pipelines.
/OK3568_Linux_fs/kernel/arch/arm/boot/dts/
H A Dsun5i-a13.dtsi84 allwinner,pipelines = <&fe0>;
H A Dsun5i-gr8.dtsi54 allwinner,pipelines = <&fe0>;
H A Dsun5i-a10s.dtsi72 allwinner,pipelines = <&fe0>;
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/media/
H A Dvideo-interfaces.txt6 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.
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/display/ti/
H A Dti,omap-dss.txt88 shifter). The video pipelines for the connectors are formed as follows:
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/
H A Dgraph.txt21 To see how this binding applies to video pipelines, for example, see

123