| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/amdzen1/ |
| 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…
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/amdzen2/ |
| 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…
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/ |
| D | allwinner,sun4i-a10-display-engine.yaml | 68 allwinner,pipelines:
78 - allwinner,pipelines
98 allwinner,pipelines:
103 allwinner,pipelines:
110 allwinner,pipelines = <&fe0>, <&fe1>;
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/arm/display/komeda/ |
| D | komeda_dev.c | 37 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()
|
| D | komeda_dev.h | 144 * 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
|
| D | komeda_pipeline.c | 20 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()
|
| D | komeda_kms.h | 27 * 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-5.10/Documentation/gpu/ |
| 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:
|
| /kernel/linux/linux-4.19/Documentation/media/v4l-drivers/ |
| D | imx.rst | 78 - Many different pipelines can be configured via media controller API,
79 that correspond to the hardware video capture pipelines supported in
84 - Concurrent independent streams, by configuring pipelines to multiple
94 motion compensation modes: low, medium, and high motion. Pipelines are
394 Capture Pipelines
397 The following describe the various use-cases supported by the pipelines.
401 (parallel or mipi csi-2). So these pipelines begin with:
480 pipelines for both sensors. The OV5642 is routed to ipu1_csi0, and
|
| D | qcom_camss.rst | 127 sub-devices allows to create linear media controller pipelines when using two
128 cameras simultaneously. This avoids branches in the pipelines which otherwise
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/media/ |
| 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
|
| 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
|
| /kernel/linux/linux-4.19/drivers/media/platform/xilinx/ |
| D | Kconfig | 7 Driver for Xilinx Video IP Pipelines
|
| /kernel/linux/linux-5.10/drivers/media/platform/xilinx/ |
| D | Kconfig | 11 Driver for Xilinx Video IP Pipelines
|
| /kernel/linux/linux-5.10/drivers/staging/vc04_services/bcm2835-camera/ |
| D | TODO | 4 pipelines, we need to export our buffers through dma-buf so that the
|
| /kernel/linux/linux-4.19/drivers/staging/vc04_services/bcm2835-camera/ |
| D | TODO | 4 pipelines, we need to export our buffers through dma-buf so that the
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/media/ |
| D | video-interfaces.txt | 6 Video data pipelines usually consist of external devices, e.g. camera sensors,
154 The example snippet below describes two data pipelines. ov772x and imx074 are
161 pipelines can be active: ov772x -> ceu0 or imx074 -> csi2 -> ceu0.
|
| /kernel/linux/linux-4.19/drivers/gpu/drm/sun4i/ |
| D | sun4i_drv.c | 112 dev_err(drm->dev, "Couldn't bind all pipelines components\n"); in sun4i_drv_bind()
249 * in the pipeline. Fortunately, the pipelines are perfectly symmetric,
383 "allwinner,pipelines", in sun4i_drv_probe()
|
| /kernel/linux/linux-4.19/Documentation/media/uapi/dvb/ |
| D | legacy_dvb_apis.rst | 16 video should be using the V4L2 and ALSA APIs, and the pipelines should
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/dvb/ |
| D | legacy_dvb_apis.rst | 16 video should be using the V4L2 and ALSA APIs, and the pipelines should
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/sun4i/ |
| D | sun4i_drv.c | 90 dev_err(drm->dev, "Couldn't bind all pipelines components\n"); in sun4i_drv_bind()
224 * in the pipeline. Fortunately, the pipelines are perfectly symmetric,
379 "allwinner,pipelines", in sun4i_drv_probe()
|
| /kernel/linux/linux-4.19/include/media/ |
| D | vsp1.h | 28 * @interlaced: true for interlaced pipelines
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | sun5i-a13.dtsi | 84 allwinner,pipelines = <&fe0>;
|
| /kernel/linux/linux-5.10/include/media/ |
| D | vsp1.h | 27 * @interlaced: true for interlaced pipelines
|
| /kernel/linux/linux-4.19/arch/arm/boot/dts/ |
| D | sun5i-a13.dtsi | 88 allwinner,pipelines = <&fe0>;
|