Home
last modified time | relevance | path

Searched full:pipelines (Results 1 – 25 of 258) sorted by relevance

1234567891011

/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/amdzen1/
Dfloating-point.json6 … uOps dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
13 … uOps dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
20 … uOps dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
27 … uOps dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
34 … uOps dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
41 … uOps dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
48 …uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
55 …uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
62 …uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
69 …uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
/kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/amdzen1/
Dfloating-point.json6 … uOps dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
13 … uOps dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
20 … uOps dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
27 … uOps dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
34 … uOps dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
41 … uOps dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
48 …uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
55 …uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
62 …uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
69 …uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
/kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/amdzen2/
Dfloating-point.json6 …uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
13 …uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
20 …uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
27 …uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
34 …uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/amdzen2/
Dfloating-point.json6 …uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
13 …uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
20 …uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
27 …uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
34 …uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
/kernel/linux/linux-6.6/sound/soc/sof/
Dipc4-pcm.c35 /* trigger multiple pipelines with a single IPC */ in sof_ipc4_set_multi_pipeline_state()
38 /* ipc_size includes the count and the pipeline IDs for the number of pipelines */ in sof_ipc4_set_multi_pipeline_state()
201 * model on SOF driver has two notional pipelines, one at host DAI,
253 struct snd_sof_pipeline *spipe = pipeline_list->pipelines[i]; in sof_ipc4_chain_dma_trigger()
259 "All pipelines in chained DMA stream should have use_chain_dma attribute set."); in sof_ipc4_chain_dma_trigger()
303 if (!pipeline_list->pipelines || !pipeline_list->count) in sof_ipc4_trigger_pipelines()
306 spipe = pipeline_list->pipelines[0]; in sof_ipc4_trigger_pipelines()
326 * IPC4 requires pipelines to be triggered in order starting at the sink and in sof_ipc4_trigger_pipelines()
329 * Skip the pipelines that have their skip_during_fe_trigger flag set. If there is a fork in sof_ipc4_trigger_pipelines()
336 spipe = pipeline_list->pipelines[i]; in sof_ipc4_trigger_pipelines()
[all …]
Dsof-audio.h205 * @set_up_all_pipelines: Function pointer for setting up all topology pipelines
206 * @tear_down_all_pipelines: Function pointer for tearing down all topology pipelines
306 * struct snd_sof_pcm_stream_pipeline_list - List of pipelines associated with a PCM stream
308 * @pipelines: array of pipelines
312 struct snd_sof_pipeline **pipelines; member
326 * flag to indicate that the DSP pipelines should be kept
425 * unique for each module type across all pipelines. This will not be used in SOF_IPC.
Dsof-audio.c111 * skip for static pipelines in sof_widget_free_unlocked()
161 * widget in the pipeline is freed. Skip setting up scheduler widget for static pipelines. in sof_widget_setup_unlocked()
350 * This is not sufficient to handle loopback cases between pipelines configured with in sof_setup_pipeline_connections()
568 if (!pipeline_list->pipelines) in sof_set_up_widgets_in_path()
572 * Add the widget's pipe_widget to the list of pipelines to be triggered if not in sof_set_up_widgets_in_path()
573 * already in the list. This will result in the pipelines getting added in the in sof_set_up_widgets_in_path()
577 spipe = pipeline_list->pipelines[i]; in sof_set_up_widgets_in_path()
584 pipeline_list->pipelines[i] = swidget->spipe; in sof_set_up_widgets_in_path()
718 /* complete pipelines */ in sof_widget_list_setup()
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/amdzen3/
Dfloating-point.json6 …uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
13 …uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
20 …uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
27 …uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
34 …uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pi…
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/
Dallwinner,sun4i-a10-display-engine.yaml68 allwinner,pipelines:
78 - allwinner,pipelines
98 allwinner,pipelines:
103 allwinner,pipelines:
110 allwinner,pipelines = <&fe0>, <&fe1>;
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/display/
Dallwinner,sun4i-a10-display-engine.yaml69 allwinner,pipelines:
81 - allwinner,pipelines
102 allwinner,pipelines:
107 allwinner,pipelines:
114 allwinner,pipelines = <&fe0>, <&fe1>;
/kernel/linux/linux-6.6/drivers/gpu/drm/arm/display/komeda/
Dkomeda_dev.c37 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()
248 DRM_ERROR("assemble display pipelines failed.\n"); in komeda_dev_create()
297 komeda_pipeline_destroy(mdev, mdev->pipelines[i]); in komeda_dev_destroy()
298 mdev->pipelines[i] = NULL; in komeda_dev_destroy()
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
Dkomeda_pipeline.c22 DRM_ERROR("Exceed max support %d pipelines.\n", in komeda_pipeline_add()
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()
Dkomeda_kms.h27 * represents available layer input pipelines for this plane.
104 * the affected pipelines in once display instance
109 * the active pipelines in once display instance
/kernel/linux/linux-5.10/drivers/gpu/drm/arm/display/komeda/
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()
260 DRM_ERROR("assemble display pipelines failed.\n"); in komeda_dev_create()
310 komeda_pipeline_destroy(mdev, mdev->pipelines[i]); in komeda_dev_destroy()
311 mdev->pipelines[i] = NULL; in komeda_dev_destroy()
Dkomeda_dev.h144 * And D71 supports assign two pipelines to one single display on mode
184 /** @n_pipelines: the number of pipe in @pipelines */
186 /** @pipelines: the komeda pipelines */
187 struct komeda_pipeline *pipelines[KOMEDA_MAX_PIPELINES]; member
Dkomeda_pipeline.c20 DRM_ERROR("Exceed max support %d pipelines.\n", in komeda_pipeline_add()
38 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()
Dkomeda_kms.h27 * represents available layer input pipelines for this plane.
101 * the affected pipelines in once display instance
106 * the active pipelines in once display instance
/kernel/linux/linux-6.6/Documentation/gpu/
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:
/kernel/linux/linux-5.10/Documentation/gpu/
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:
/kernel/linux/linux-6.6/drivers/media/platform/samsung/exynos4-is/
Dmedia-dev.h115 * @pipelines: list of pipelines
145 struct list_head pipelines; member
/kernel/linux/linux-6.6/drivers/staging/media/atomisp/
Dnotes.txt28 this means that unlike in fixed pipelines the soft pipelines
/kernel/linux/linux-5.10/Documentation/admin-guide/media/
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
96 motion compensation modes: low, medium, and high motion. Pipelines are
347 Capture Pipelines
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
/kernel/linux/linux-6.6/Documentation/admin-guide/media/
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
96 motion compensation modes: low, medium, and high motion. Pipelines are
347 Capture Pipelines
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
/kernel/linux/linux-6.6/drivers/gpu/drm/ci/
Dgitlab-ci.yml150 # Rule to filter for only scheduled pipelines.
156 # Generic rule to not run the job during scheduled pipelines. Jobs that aren't
256 # pipelines. This should appear in "extends:" after any includes of

1234567891011