Home
last modified time | relevance | path

Searched +full:opp +full:- +full:specific (Results 1 – 25 of 181) sorted by relevance

12345678

/kernel/linux/linux-6.6/Documentation/devicetree/bindings/opp/
Dopp-v2-base.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/opp/opp-v2-base.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Generic OPP (Operating Performance Points) Common Properties
10 - Viresh Kumar <viresh.kumar@linaro.org>
13 Devices work at voltage-current-frequency combinations and some implementations
25 pattern: '^opp-table(-[a-z0-9]+)?$'
27 opp-shared:
29 Indicates that device nodes using this OPP Table Node's phandle switch
[all …]
Dti,omap-opp-supply.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/opp/ti,omap-opp-supply.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Texas Instruments OMAP compatible OPP supply
11 registers, which contain OPP-specific voltage information tailored
12 for the specific device. This binding provides the information
14 the primary regulator during an OPP transition.
16 Also, some supplies may have an associated vbb-supply, an Adaptive
17 Body Bias regulator, which must transition in a specific sequence
[all …]
/kernel/linux/linux-5.10/drivers/opp/
Ddebugfs.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * Generic OPP debugfs interface
5 * Copyright (C) 2015-2016 Viresh Kumar <viresh.kumar@linaro.org>
17 #include "opp.h"
23 if (dev->parent) in opp_set_dev_name()
24 snprintf(name, NAME_MAX, "%s-%s", dev_name(dev->parent), in opp_set_dev_name()
30 void opp_debug_remove_one(struct dev_pm_opp *opp) in opp_debug_remove_one() argument
32 debugfs_remove_recursive(opp->dentry); in opp_debug_remove_one()
38 struct icc_path *path = fp->private_data; in bw_name_read()
53 static void opp_debug_create_bw(struct dev_pm_opp *opp, in opp_debug_create_bw() argument
[all …]
Dti-opp-supply.c1 // SPDX-License-Identifier: GPL-2.0
3 * Copyright (C) 2016-2017 Texas Instruments Incorporated - https://www.ti.com/
5 * Dave Gerlach <d-gerlach@ti.com>
7 * TI OPP supply driver that provides override into the regulator control
8 * for generic opp core to handle devices with ABB regulator and/or
25 * struct ti_opp_supply_optimum_voltage_table - optimized voltage table
35 * struct ti_opp_supply_data - OMAP specific opp supply data
49 * struct ti_opp_supply_of_data - device tree match data
50 * @flags: specific type of opp supply
52 * @efuse_voltage_uv: Are the efuse entries in micro-volts? if not, assume
[all …]
/kernel/linux/linux-6.6/drivers/opp/
Ddebugfs.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * Generic OPP debugfs interface
5 * Copyright (C) 2015-2016 Viresh Kumar <viresh.kumar@linaro.org>
18 #include "opp.h"
24 if (dev->parent) in opp_set_dev_name()
25 snprintf(name, NAME_MAX, "%s-%s", dev_name(dev->parent), in opp_set_dev_name()
31 void opp_debug_remove_one(struct dev_pm_opp *opp) in opp_debug_remove_one() argument
33 debugfs_remove_recursive(opp->dentry); in opp_debug_remove_one()
39 struct icc_path *path = fp->private_data; in bw_name_read()
54 static void opp_debug_create_bw(struct dev_pm_opp *opp, in opp_debug_create_bw() argument
[all …]
Dopp.h1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * Generic OPP Interface
5 * Copyright (C) 2009-2010 Texas Instruments Incorporated.
26 /* Lock to allow exclusive modification to the device and opp lists */
31 /* OPP Config flags */
40 * struct opp_config_data - data for set config operations
41 * @opp_table: OPP table
42 * @flags: OPP config flags
44 * This structure stores the OPP config information for each OPP table
53 * Internal data structure organization with the OPP layer library is as
[all …]
Dti-opp-supply.c1 // SPDX-License-Identifier: GPL-2.0
3 * Copyright (C) 2016-2017 Texas Instruments Incorporated - https://www.ti.com/
5 * Dave Gerlach <d-gerlach@ti.com>
7 * TI OPP supply driver that provides override into the regulator control
8 * for generic opp core to handle devices with ABB regulator and/or
25 * struct ti_opp_supply_optimum_voltage_table - optimized voltage table
35 * struct ti_opp_supply_data - OMAP specific opp supply data
39 * @old_supplies: Placeholder for supplies information for old OPP.
40 * @new_supplies: Placeholder for supplies information for new OPP.
53 * struct ti_opp_supply_of_data - device tree match data
[all …]
/kernel/linux/linux-5.10/Documentation/driver-api/thermal/
Dcpu-idle-cooling.rst1 .. SPDX-License-Identifier: GPL-2.0
8 ----------
24 Last but not least, the system can ask for a specific power budget but
25 because of the OPP density, we can only choose an OPP with a power
26 budget lower than the requested one and under-utilize the CPU, thus
27 losing performance. In other words, one OPP under-utilizes the CPU
28 with a power less than the requested power budget and the next OPP
29 exceeds the power budget. An intermediate OPP could have been used if
33 ----------
35 If we can remove the static and the dynamic leakage for a specific
[all …]
/kernel/linux/linux-6.6/Documentation/driver-api/thermal/
Dcpu-idle-cooling.rst1 .. SPDX-License-Identifier: GPL-2.0
8 ----------
24 Last but not least, the system can ask for a specific power budget but
25 because of the OPP density, we can only choose an OPP with a power
26 budget lower than the requested one and under-utilize the CPU, thus
27 losing performance. In other words, one OPP under-utilizes the CPU
28 with a power less than the requested power budget and the next OPP
29 exceeds the power budget. An intermediate OPP could have been used if
33 ----------
35 If we can remove the static and the dynamic leakage for a specific
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/msm/
Dgpu.txt4 - compatible: "qcom,adreno-XYZ.W", "qcom,adreno" or
5 "amd,imageon-XYZ.W", "amd,imageon"
6 for example: "qcom,adreno-306.0", "qcom,adreno"
7 Note that you need to list the less specific "qcom,adreno" (since this
8 is what the device is matched on), in addition to the more specific
9 with the chip-id.
11 - reg: Physical base address and length of the controller's registers.
12 - interrupts: The interrupt signal from the gpu.
13 - clocks: device clocks (if applicable)
14 See ../clocks/clock-bindings.txt for details.
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/opp/
Dopp.txt1 Generic OPP (Operating Performance Points) Bindings
2 ----------------------------------------------------
4 Devices work at voltage-current-frequency combinations and some implementations
10 This document contain multiple versions of OPP binding and only one of them
13 Binding 1: operating-points
16 This binding only supports voltage-frequency pairs.
19 - operating-points: An array of 2-tuples items, and each item consists
20 of frequency and voltage like <freq-kHz vol-uV>.
27 compatible = "arm,cortex-a9";
29 next-level-cache = <&L2>;
[all …]
Dti-omap5-opp-supply.txt1 Texas Instruments OMAP compatible OPP supply description
7 an OPP transitions.
9 Also, some supplies may have an associated vbb-supply which is an Adaptive Body
10 Bias regulator which much be transitioned in a specific sequence with regards
11 to the vdd-supply and clk when making an OPP transition. By supplying two
12 regulators to the device that will undergo OPP transitions we can make use
13 of the multi regulator binding that is part of the OPP core described here [1]
16 [1] Documentation/devicetree/bindings/opp/opp.txt
19 - vdd-supply: phandle to regulator controlling VDD supply
20 - vbb-supply: phandle to regulator controlling Body Bias supply
[all …]
/kernel/linux/linux-6.6/arch/arm/mach-omap2/
Domap_opp_data.h1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * OMAP SoC specific OPP Data helpers
5 * Copyright (C) 2009-2010 Texas Instruments Incorporated - https://www.ti.com/
20 * USE the following ONLY in opp data initialization common to an SoC.
25 * struct omap_opp_def - OMAP OPP Definition
27 * @freq: Frequency in hertz corresponding to this OPP
28 * @u_volt: Nominal voltage in microvolts corresponding to this OPP
29 * @default_available: True/false - is this OPP available by default
33 * Operating Points or OPP. The actual definitions of OMAP Operating Points
34 * varies over silicon within the same family of devices. For a specific
[all …]
/kernel/linux/linux-5.10/arch/arm/mach-omap2/
Domap_opp_data.h2 * OMAP SoC specific OPP Data helpers
4 * Copyright (C) 2009-2010 Texas Instruments Incorporated - https://www.ti.com/
28 * USE the following ONLY in opp data initialization common to an SoC.
33 * struct omap_opp_def - OMAP OPP Definition
35 * @freq: Frequency in hertz corresponding to this OPP
36 * @u_volt: Nominal voltage in microvolts corresponding to this OPP
37 * @default_available: True/false - is this OPP available by default
41 * Operating Points or OPP. The actual definitions of OMAP Operating Points
42 * varies over silicon within the same family of devices. For a specific
48 * of this - but this is handled by the appropriate driver.
[all …]
/kernel/linux/linux-6.6/arch/arm/boot/dts/samsung/
Dexynos5800.dtsi1 // SPDX-License-Identifier: GPL-2.0
10 * values for board specific bindings.
20 compatible = "samsung,exynos5800-clock", "syscon";
24 opp-2000000000 {
25 opp-hz = /bits/ 64 <2000000000>;
26 opp-microvolt = <1312500 1312500 1500000>;
27 clock-latency-ns = <140000>;
29 opp-1900000000 {
30 opp-hz = /bits/ 64 <1900000000>;
31 opp-microvolt = <1262500 1262500 1500000>;
[all …]
Dexynos4212.dtsi1 // SPDX-License-Identifier: GPL-2.0
9 * based board files can include this file and provide values for board specific
23 #address-cells = <1>;
24 #size-cells = <0>;
26 cpu-map {
39 compatible = "arm,cortex-a9";
42 clock-names = "cpu";
43 operating-points-v2 = <&cpu0_opp_table>;
44 #cooling-cells = <2>; /* min followed by max */
49 compatible = "arm,cortex-a9";
[all …]
Dexynos4412.dtsi1 // SPDX-License-Identifier: GPL-2.0
9 * based board files can include this file and provide values for board specific
23 #address-cells = <1>;
24 #size-cells = <0>;
26 cpu-map {
45 compatible = "arm,cortex-a9";
48 clock-names = "cpu";
49 operating-points-v2 = <&cpu0_opp_table>;
50 #cooling-cells = <2>; /* min followed by max */
55 compatible = "arm,cortex-a9";
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/interconnect/
Dmediatek,cci.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jia-Wei Chang <jia-wei.chang@mediatek.com>
11 - Johnson Wang <johnson.wang@mediatek.com>
21 - mediatek,mt8183-cci
22 - mediatek,mt8186-cci
26 - description:
28 - description:
33 clock-names:
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/cpufreq/
Dcpufreq-st.txt5 from the SoC, then supplies the OPP framework with 'prop' and 'supported
9 For more information about the expected DT format [See: ../opp/opp.txt].
12 ----------------------
14 No vendor specific driver required for this.
18 - operating-points : [See: ../power/opp.txt]
21 --------------
26 operating-points = <1500000 0
34 --------------------------------------------
40 - operating-points-v2 : [See ../power/opp.txt]
43 ----------------
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/cpufreq/
Dcpufreq-st.txt5 from the SoC, then supplies the OPP framework with 'prop' and 'supported
10 ----------------------
12 No vendor specific driver required for this.
16 - operating-points : [See: ../power/opp-v1.yaml]
19 --------------
24 operating-points = <1500000 0
32 --------------------------------------------
38 - operating-points-v2 : [See ../power/opp-v2.yaml]
41 ----------------
45 operating-points-v2 = <&cpu0_opp_table>;
[all …]
/kernel/linux/linux-5.10/Documentation/power/
Dopp.rst2 Operating Performance Points (OPP) Library
5 (C) 2009-2010 Nishanth Menon <nm@ti.com>, Texas Instruments Incorporated
10 2. Initial OPP List Registration
11 3. OPP Search Functions
12 4. OPP Availability Control Functions
13 5. OPP Data Retrieval Functions
19 1.1 What is an Operating Performance Point (OPP)?
20 -------------------------------------------------
22 Complex SoCs of today consists of a multiple sub-modules working in conjunction.
25 facilitate this, sub-modules in a SoC are grouped into domains, allowing some
[all …]
/kernel/linux/linux-6.6/Documentation/power/
Dopp.rst2 Operating Performance Points (OPP) Library
5 (C) 2009-2010 Nishanth Menon <nm@ti.com>, Texas Instruments Incorporated
10 2. Initial OPP List Registration
11 3. OPP Search Functions
12 4. OPP Availability Control Functions
13 5. OPP Data Retrieval Functions
19 1.1 What is an Operating Performance Point (OPP)?
20 -------------------------------------------------
22 Complex SoCs of today consists of a multiple sub-modules working in conjunction.
25 facilitate this, sub-modules in a SoC are grouped into domains, allowing some
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/mmc/
Dsdhci-msm.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mmc/sdhci-msm.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm SDHCI controller (sdhci-msm)
10 - Bhupesh Sharma <bhupesh.sharma@linaro.org>
19 - enum:
20 - qcom,sdhci-msm-v4
22 - items:
23 - enum:
[all …]
/kernel/linux/linux-6.6/Documentation/gpu/amdgpu/display/
Ddcn-overview.rst10 .. kernel-figure:: dc_pipeline_overview.svg
19 * **Display Pipe and Plane (DPP)**: This block provides pre-blend pixel
24 multiple planes, using global or per-pixel alpha.
26 * **Output Pixel Processing (OPP)**: Process and format pixels to be sent to
38 * **Multi-Media HUB (MMHUBBUB)**: Memory controller interface for DMCUB and DWB
43 the Display Micro-Controller Unit - version B (DMCUB), which is handled via
60 OPP. It is DC's responsibility to drive the best configuration for each
61 specific scenario. Orchestrate all of these components together requires a
79 that HUBP accesses a surface using a specific format read from memory, and our
84 ----------------------
[all …]
/kernel/linux/linux-6.6/include/linux/mfd/
Ddbx500-prcmu.h1 /* SPDX-License-Identifier: GPL-2.0-only */
14 #include <dt-bindings/mfd/dbx500-prcmu.h> /* For clock identifiers */
40 * - EPOD_ID_SVAMMDSP: power domain for SVA MMDSP
41 * - EPOD_ID_SVAPIPE: power domain for SVA pipe
42 * - EPOD_ID_SIAMMDSP: power domain for SIA MMDSP
43 * - EPOD_ID_SIAPIPE: power domain for SIA pipe
44 * - EPOD_ID_SGA: power domain for SGA
45 * - EPOD_ID_B2R2_MCDE: power domain for B2R2 and MCDE
46 * - EPOD_ID_ESRAM12: power domain for ESRAM 1 and 2
47 * - EPOD_ID_ESRAM34: power domain for ESRAM 3 and 4
[all …]

12345678