| /linux/tools/perf/pmu-events/arch/x86/amdzen1/ |
| H A D | floating-point.json | 6 … 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…
|
| /linux/tools/perf/pmu-events/arch/x86/amdzen2/ |
| H A D | floating-point.json | 6 …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…
|
| /linux/tools/perf/pmu-events/arch/x86/amdzen3/ |
| H A D | floating-point.json | 6 …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…
|
| /linux/sound/soc/sof/ |
| H A D | ipc4-pcm.c | 76 /* trigger multiple pipelines with a single IPC */ in sof_ipc4_set_multi_pipeline_state()
79 /* ipc_size includes the count and the pipeline IDs for the number of pipelines */ in sof_ipc4_set_multi_pipeline_state()
269 * model on SOF driver has two notional pipelines, one at host DAI,
331 struct snd_sof_pipeline *spipe = pipeline_list->pipelines[i]; in sof_ipc4_chain_dma_trigger()
337 "All pipelines in chained DMA path should have use_chain_dma attribute set."); in sof_ipc4_chain_dma_trigger()
401 if (!pipeline_list->pipelines || !pipeline_list->count) in sof_ipc4_trigger_pipelines()
404 spipe = pipeline_list->pipelines[0]; in sof_ipc4_trigger_pipelines()
431 * IPC4 requires pipelines to be triggered in order starting at the sink and in sof_ipc4_trigger_pipelines()
434 * Skip the pipelines that have their skip_during_fe_trigger flag set. If there is a fork in sof_ipc4_trigger_pipelines()
441 spipe = pipeline_list->pipelines[i]; in sof_ipc4_trigger_pipelines()
[all …]
|
| H A D | pm.c | 162 /* restore pipelines */ in sof_resume()
213 /* we need to tear down pipelines only if the DSP hardware is in sof_suspend()
|
| H A D | ipc4-topology.h | 147 * @count: Number of pipelines to be triggered
148 * @pipeline_instance_ids: Flexible array of IDs of the pipelines to be triggered
|
| /linux/Documentation/devicetree/bindings/display/ |
| H A D | allwinner,sun4i-a10-display-engine.yaml | 69 allwinner,pipelines:
81 - allwinner,pipelines
102 allwinner,pipelines:
107 allwinner,pipelines:
114 allwinner,pipelines = <&fe0>, <&fe1>;
|
| H A D | arm,komeda.yaml | 53 The stream IDs for each of the used pipelines, each four IDs for the
|
| /linux/Documentation/gpu/ |
| H A 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:
|
| /linux/drivers/gpu/drm/arm/display/komeda/ |
| H A D | komeda_dev.h | 144 * 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 D | komeda_pipeline.c | 24 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 D | komeda_kms.h | 27 * represents available layer input pipelines for this plane.
104 * the affected pipelines in once display instance
109 * the active pipelines in once display instance
|
| /linux/drivers/staging/media/atomisp/ |
| H A D | notes.txt | 28 this means that unlike in fixed pipelines the soft pipelines
|
| /linux/Documentation/admin-guide/media/ |
| H A 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
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
|
| H A 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
|
| /linux/drivers/media/platform/xilinx/ |
| H A D | Kconfig | 14 Driver for Xilinx Video IP Pipelines
|
| /linux/drivers/gpu/drm/sun4i/ |
| H A D | sun4i_drv.c | 92 dev_err(drm->dev, "Couldn't bind all pipelines components\n"); in sun4i_drv_bind()
222 * in the pipeline. Fortunately, the pipelines are perfectly symmetric,
384 "allwinner,pipelines", in sun4i_drv_probe()
|
| /linux/drivers/staging/vc04_services/bcm2835-camera/ |
| H A D | TODO | 4 pipelines, we need to export our buffers through dma-buf so that the
|
| /linux/tools/perf/pmu-events/arch/arm64/fujitsu/a64fx/ |
| H A D | pipeline.json | 123 …"PublicDescription": "This event counts aborted requests in L1D pipelines that due to store-load i…
126 …"BriefDescription": "This event counts aborted requests in L1D pipelines that due to store-load in…
|
| /linux/sound/soc/intel/avs/ |
| H A D | path.h | 34 /* path pipelines management */
|
| H A D | topology.h | 196 /* Path pipelines management. */
|
| /linux/Documentation/userspace-api/media/dvb/ |
| H A D | legacy_dvb_decoder_api.rst | 27 Pipelines should be set up using the :ref:`Media Controller API<media_controller>`.
|
| /linux/include/media/ |
| H A D | vsp1.h | 27 * @interlaced: true for interlaced pipelines
|
| /linux/arch/arm/boot/dts/allwinner/ |
| H A D | sun5i-a13.dtsi | 84 allwinner,pipelines = <&fe0>;
|
| H A D | sun5i-gr8.dtsi | 54 allwinner,pipelines = <&fe0>;
|