| /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 | 102 dev_dbg(sdev->dev, "Set pipelines %s to state %d%s", in sof_ipc4_set_multi_pipeline_state()
113 /* trigger multiple pipelines with a single IPC */ in sof_ipc4_set_multi_pipeline_state()
116 /* ipc_size includes the count and the pipeline IDs for the number of pipelines */ in sof_ipc4_set_multi_pipeline_state()
307 * model on SOF driver has two notional pipelines, one at host DAI,
369 struct snd_sof_pipeline *spipe = pipeline_list->pipelines[i]; in sof_ipc4_chain_dma_trigger()
375 "All pipelines in chained DMA path should have use_chain_dma attribute set."); in sof_ipc4_chain_dma_trigger()
439 if (!pipeline_list->pipelines || !pipeline_list->count) in sof_ipc4_trigger_pipelines()
442 spipe = pipeline_list->pipelines[0]; in sof_ipc4_trigger_pipelines()
493 * IPC4 requires pipelines to be triggered in order starting at the sink and in sof_ipc4_trigger_pipelines()
496 * Skip the pipelines that have their skip_during_fe_trigger flag set. If there is a fork in sof_ipc4_trigger_pipelines()
[all …]
|
| H A D | sof-audio.h | 214 * @set_up_all_pipelines: Function pointer for setting up all topology pipelines
215 * @tear_down_all_pipelines: Function pointer for tearing down all topology pipelines
319 * struct snd_sof_pcm_stream_pipeline_list - List of pipelines associated with a PCM stream
320 * @pipelines: array of pipelines
324 struct snd_sof_pipeline **pipelines;
341 * flag to indicate that the DSP pipelines should be kept
445 * unique for each module type across all pipelines. This will not be used in SOF_IPC.
321 struct snd_sof_pipeline **pipelines; global() member
|
| H A D | pm.c | 126 /* restore pipelines */ in sof_resume()
246 /* we need to tear down pipelines only if the DSP hardware is in sof_suspend()
|
| H A D | ipc4-topology.h | 171 * @count: Number of pipelines to be triggered
172 * @pipeline_instance_ids: Flexible array of IDs of the pipelines to be triggered
|
| H A D | ipc4-priv.h | 72 * @max_num_pipelines: max number of pipelines
|
| H A D | ipc4-fw-reg.h | 122 * @pipeline_regs: State of pipelines attached to host output gateways
|
| /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>;
|
| /linux/Documentation/gpu/rfc/ |
| H A D | color_pipeline.rst | 99 HW color management pipelines can significantly differ between HW
110 To support the definition of color pipelines we define the DRM core
114 pipelines have the same operation they won't share the same drm_colorop
188 Color Pipelines are created by a driver and advertised via a new
193 one, or more possible color pipelines. A DRM client will select a color
329 suggestions on how to think about creating your color pipelines:
331 - Try to expose pipelines that use already defined colorops, even if
358 As this is uAPI drivers can't regress color pipelines that have been
360 abandon color pipelines advertised for previous generations.
362 pipelines forward as those will likely already have support in DRM
|
| /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/drivers/media/platform/xilinx/ |
| H A D | Kconfig | 14 Driver for Xilinx Video IP Pipelines
|
| /linux/Documentation/admin-guide/media/ |
| 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/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/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/drivers/gpu/drm/ |
| H A D | drm_plane.c | 1829 * @pipelines: list of pipelines
1830 * @num_pipelines: number of pipelines
1832 * Create the COLOR_PIPELINE plane property to specific color pipelines on
1839 const struct drm_prop_enum_list *pipelines, in drm_plane_create_color_pipeline_property() argument
1859 /* Add all other color pipelines */ in drm_plane_create_color_pipeline_property()
1861 all_pipelines[len].type = pipelines[i].type; in drm_plane_create_color_pipeline_property()
1862 all_pipelines[len].name = pipelines[i].name; in drm_plane_create_color_pipeline_property()
|
| /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>;
|
| /linux/tools/perf/pmu-events/arch/x86/sandybridge/ |
| H A D | snb-metrics.json | 143 …tric represents fraction of cycles the CPU was stalled due to switches from DSB to MITE pipelines",
148 …pipelines. The DSB (decoded i-cache) is a Uop Cache where the front-end directly delivers Uops (mi…
511 …livery by the DSB (decoded i-cache) or MITE (legacy instruction decode) pipelines. Certain operati…
|
| /linux/tools/perf/pmu-events/arch/x86/jaketown/ |
| H A D | jkt-metrics.json | 143 …tric represents fraction of cycles the CPU was stalled due to switches from DSB to MITE pipelines",
148 …pipelines. The DSB (decoded i-cache) is a Uop Cache where the front-end directly delivers Uops (mi…
532 …livery by the DSB (decoded i-cache) or MITE (legacy instruction decode) pipelines. Certain operati…
|