Home
last modified time | relevance | path

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

12

/linux/drivers/gpu/drm/arm/display/komeda/
H A Dkomeda_dev.c35 komeda_pipeline_dump_register(mdev->pipelines[i], sf); in komeda_register_show()
69 struct komeda_pipeline *pipe = mdev->pipelines[0]; in config_id_show()
160 mdev->pipelines[pipe_id]->of_node = of_node_get(child); in komeda_parse_dt()
165 pipe = mdev->pipelines[pipe_id]; in komeda_parse_dt()
244 DRM_ERROR("assemble display pipelines failed.\n"); in komeda_dev_create()
289 komeda_pipeline_destroy(mdev, mdev->pipelines[i]); in komeda_dev_destroy()
290 mdev->pipelines[i] = NULL; in komeda_dev_destroy()
H A Dkomeda_pipeline.c24 DRM_ERROR("Exceed max support %d pipelines.\n", in komeda_pipeline_add()
42 mdev->pipelines[mdev->n_pipelines] = pipe; in komeda_pipeline_add()
89 temp = mdev->pipelines[id - KOMEDA_COMPONENT_COMPIZ0]; in komeda_pipeline_get_component_pos()
108 temp = mdev->pipelines[id - KOMEDA_COMPONENT_IPS0]; in komeda_pipeline_get_component_pos()
352 pipe = mdev->pipelines[i]; in komeda_assemble_pipelines()
H A Dkomeda_dev.h144 * And D71 supports assign two pipelines to one single display on mode
182 /** @n_pipelines: the number of pipe in @pipelines */
184 /** @pipelines: the komeda pipelines */
185 struct komeda_pipeline *pipelines[KOMEDA_MAX_PIPELINES]; member
H A Dkomeda_plane.c325 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()
/linux/sound/soc/sof/
H A Dipc4-pcm.c89 dev_dbg(sdev->dev, "Set pipelines %s to state %d%s", in sof_ipc4_set_multi_pipeline_state()
100 /* trigger multiple pipelines with a single IPC */ in sof_ipc4_set_multi_pipeline_state()
103 /* ipc_size includes the count and the pipeline IDs for the number of pipelines */ in sof_ipc4_set_multi_pipeline_state()
294 * model on SOF driver has two notional pipelines, one at host DAI,
356 struct snd_sof_pipeline *spipe = pipeline_list->pipelines[i]; in sof_ipc4_chain_dma_trigger()
362 "All pipelines in chained DMA path should have use_chain_dma attribute set."); in sof_ipc4_chain_dma_trigger()
426 if (!pipeline_list->pipelines || !pipeline_list->count) in sof_ipc4_trigger_pipelines()
429 spipe = pipeline_list->pipelines[0]; in sof_ipc4_trigger_pipelines()
480 * IPC4 requires pipelines to be triggered in order starting at the sink and in sof_ipc4_trigger_pipelines()
483 * Skip the pipelines tha in sof_ipc4_trigger_pipelines()
[all...]
H A Dsof-audio.c107 * skip for static pipelines in sof_widget_free_unlocked()
158 * widget in the pipeline is freed. Skip setting up scheduler widget for static pipelines. in sof_widget_setup_unlocked()
347 * This is not sufficient to handle loopback cases between pipelines configured with in sof_setup_pipeline_connections()
565 if (!pipeline_list->pipelines) in sof_set_up_widgets_in_path()
569 * Add the widget's pipe_widget to the list of pipelines to be triggered if not in sof_set_up_widgets_in_path()
570 * already in the list. This will result in the pipelines getting added in the in sof_set_up_widgets_in_path()
574 spipe = pipeline_list->pipelines[i]; in sof_set_up_widgets_in_path()
581 pipeline_list->pipelines[i] = swidget->spipe; in sof_set_up_widgets_in_path()
715 /* complete pipelines */ in sof_widget_list_setup()
H A Dsof-audio.h213 * @set_up_all_pipelines: Function pointer for setting up all topology pipelines
214 * @tear_down_all_pipelines: Function pointer for tearing down all topology pipelines
316 * struct snd_sof_pcm_stream_pipeline_list - List of pipelines associated with a PCM stream
317 * @pipelines: array of pipelines
321 struct snd_sof_pipeline **pipelines; member
338 * flag to indicate that the DSP pipelines should be kept
440 * unique for each module type across all pipelines. This will not be used in SOF_IPC.
/linux/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:
H A Dautomated_testing.rst113 created (eg. https://gitlab.freedesktop.org/janedoe/linux/-/pipelines)
168 If a hardware farm is down and thus causing pipelines to fail that would
H A Dintroduction.rst6 complex graphics devices, usually containing programmable pipelines well
/linux/drivers/staging/media/atomisp/
H A Dnotes.txt28 this means that unlike in fixed pipelines the soft pipelines
/linux/drivers/staging/vc04_services/bcm2835-camera/
H A DTODO4 pipelines, we need to export our buffers through dma-buf so that the
/linux/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
H A Dipu3.rst233 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:
/linux/arch/arm/boot/dts/allwinner/
H A Dsun5i-a13.dtsi84 allwinner,pipelines = <&fe0>;
H A Dsun5i-gr8.dtsi54 allwinner,pipelines = <&fe0>;
H A Dsun5i-a10s.dtsi72 allwinner,pipelines = <&fe0>;
H A Dsun8i-v3s.dtsi84 allwinner,pipelines = <&mixer0>;
/linux/Documentation/devicetree/bindings/display/ti/
H A Dti,omap-dss.txt88 shifter). The video pipelines for the connectors are formed as follows:
/linux/Documentation/admin-guide/
H A Dworkload-tracing.rst123 operating system, pipelines, schedulers, and virtual machines. Please refer
261 memory, network, operating system, pipelines, schedulers, and virtual
/linux/Documentation/userspace-api/media/v4l/
H A Dopen.rst44 sub-devices and to configure the pipelines via the
/linux/Documentation/userspace-api/media/mediactl/
H A Drequest-api.rst10 modern devices (stateless codecs, complex camera pipelines, ...) and APIs
/linux/arch/riscv/boot/dts/allwinner/
H A Dsunxi-d1s-t113.dtsi26 allwinner,pipelines = <&mixer0>, <&mixer1>;

12