| /Linux-v6.6/Documentation/driver-api/thermal/ |
| D | cpu-idle-cooling.rst | 18 increase even after the dynamic leakage is reduced to its minimum by
20 to the static leakage. The only solution is to power down the
21 component, thus dropping the dynamic and static leakage that will
35 If we can remove the static and the dynamic leakage for a specific
50 dynamic leakage for this period (modulo the energy needed to enter
65 state with a minimum power consumption and reduce the static leakage
184 * The static leakage is not defined here, we can introduce it in the
|
| /Linux-v6.6/Documentation/ABI/testing/ |
| D | sysfs-class-power-rt9467 | 9 is turned off to reduce the leakage from the BAT pin. See
|
| D | sysfs-class-power-rt9471 | 8 off to reduce the leakage from the BAT pin. See device datasheet for details.
|
| D | sysfs-class-power-ltc4162l | 72 by reducing the leakage to about 2.8 microamps. The chip will
|
| /Linux-v6.6/arch/arm/boot/dts/synaptics/ |
| D | berlin2cd-valve-steamlink.dts | 42 * less depending on leakage value in OTP), and buck2 likely used for
|
| /Linux-v6.6/Documentation/devicetree/bindings/power/ |
| D | power_domain.txt | 4 used for power gating of selected IP blocks for power saving by reduced leakage
|
| /Linux-v6.6/Documentation/arch/x86/ |
| D | mds.rst | 32 Hyper-Threads so cross thread leakage is possible.
40 thread leakage is possible.
|
| /Linux-v6.6/Documentation/power/ |
| D | energy-model.rst | 95 (leakage) is important.
156 physics of a real device, e.g. when static power (leakage) is important.
|
| /Linux-v6.6/drivers/gpu/drm/radeon/ |
| D | si_dpm.c | 1751 u16 v, s32 t, u32 ileakage, u32 *leakage) in si_calculate_leakage_for_v_and_t_formula() argument
1774 *leakage = drm_fixp2int(leakage_w * 1000); in si_calculate_leakage_for_v_and_t_formula()
1782 u32 *leakage) in si_calculate_leakage_for_v_and_t() argument
1784 si_calculate_leakage_for_v_and_t_formula(coeff, v, t, i_leakage, leakage); in si_calculate_leakage_for_v_and_t()
1789 u32 ileakage, u32 *leakage) in si_calculate_leakage_for_v_formula() argument
1802 *leakage = drm_fixp2int(leakage_w * 1000); in si_calculate_leakage_for_v_formula()
1810 u32 *leakage) in si_calculate_leakage_for_v() argument
1812 si_calculate_leakage_for_v_formula(coeff, fixed_kt, v, i_leakage, leakage); in si_calculate_leakage_for_v()
2563 u32 leakage; in si_init_dte_leakage_table() local
2583 &leakage); in si_init_dte_leakage_table()
[all …]
|
| D | ni_dpm.c | 743 u32 *leakage) in ni_calculate_leakage_for_v_and_t_formula() argument
758 *leakage = drm_fixp2int(leakage_w * 1000); in ni_calculate_leakage_for_v_and_t_formula()
766 u32 *leakage) in ni_calculate_leakage_for_v_and_t() argument
768 ni_calculate_leakage_for_v_and_t_formula(coeff, v, t, i_leakage, leakage); in ni_calculate_leakage_for_v_and_t()
3054 u32 leakage = 0; in ni_init_driver_calculated_leakage_table() local
3079 &leakage); in ni_init_driver_calculated_leakage_table()
3081 smc_leakage = ni_scale_power_for_smc(leakage, scaling_factor) / 1000; in ni_init_driver_calculated_leakage_table()
3124 smc_leakage = leakage_table->entries[j].leakage; in ni_init_simplified_leakage_table()
|
| /Linux-v6.6/arch/arm64/boot/dts/rockchip/ |
| D | rk3588s.dtsi | 2155 cpub0_leakage: cpu-leakage@17 {
2159 cpub1_leakage: cpu-leakage@18 {
2163 cpul_leakage: cpu-leakage@19 {
2167 log_leakage: log-leakage@1a {
2171 gpu_leakage: gpu-leakage@1b {
2180 npu_leakage: npu-leakage@28 {
2184 codec_leakage: codec-leakage@29 {
|
| D | rk3399-gru-chromebook.dtsi | 470 * Note strange pullup enable. Apparently this avoids leakage but
|
| D | rk3399.dtsi | 1440 cpub_leakage: cpu-leakage@17 {
1443 gpu_leakage: gpu-leakage@18 {
1446 center_leakage: center-leakage@19 {
1449 cpul_leakage: cpu-leakage@1a {
1452 logic_leakage: logic-leakage@1b {
|
| D | rk3328.dtsi | 582 cpu_leakage: cpu-leakage@17 {
585 logic_leakage: logic-leakage@19 {
|
| D | rk3399-gru.dtsi | 819 * prevent leakage.
|
| /Linux-v6.6/drivers/gpu/drm/amd/pm/legacy-dpm/ |
| D | si_dpm.c | 1859 u16 v, s32 t, u32 ileakage, u32 *leakage) in si_calculate_leakage_for_v_and_t_formula() argument
1882 *leakage = drm_fixp2int(leakage_w * 1000); in si_calculate_leakage_for_v_and_t_formula()
1890 u32 *leakage) in si_calculate_leakage_for_v_and_t() argument
1892 si_calculate_leakage_for_v_and_t_formula(coeff, v, t, i_leakage, leakage); in si_calculate_leakage_for_v_and_t()
1897 u32 ileakage, u32 *leakage) in si_calculate_leakage_for_v_formula() argument
1910 *leakage = drm_fixp2int(leakage_w * 1000); in si_calculate_leakage_for_v_formula()
1918 u32 *leakage) in si_calculate_leakage_for_v() argument
1920 si_calculate_leakage_for_v_formula(coeff, fixed_kt, v, i_leakage, leakage); in si_calculate_leakage_for_v()
2677 u32 leakage; in si_init_dte_leakage_table() local
2697 &leakage); in si_init_dte_leakage_table()
[all …]
|
| D | legacy_dpm.c | 402 adev->pm.dpm.dyn_state.cac_leakage_table.entries[i].leakage = in amdgpu_parse_extended_power_table()
|
| /Linux-v6.6/drivers/gpu/drm/amd/pm/inc/ |
| D | amdgpu_dpm.h | 125 u32 leakage; member
|
| /Linux-v6.6/drivers/nvmem/ |
| D | Kconfig | 264 from eFuse, such as cpu-leakage.
275 from OTP, such as cpu-leakage.
|
| /Linux-v6.6/Documentation/core-api/ |
| D | kernel-api.rst | 376 called a *retention mode*. This mode still incurs leakage currents,
|
| /Linux-v6.6/arch/arm/boot/dts/allwinner/ |
| D | sun8i-a83t-bananapi-m3.dts | 331 * avoid any leakage or mismatch.
|
| /Linux-v6.6/Documentation/admin-guide/hw-vuln/ |
| D | mds.rst | 209 This only covers the host to guest transition, i.e. prevents leakage from
|
| /Linux-v6.6/arch/arm/boot/dts/ti/omap/ |
| D | omap3-pandora-common.dtsi | 216 * disabling this regulator causes current leakage, and LCD flicker
|
| /Linux-v6.6/Documentation/admin-guide/ |
| D | perf-security.rst | 11 monitored processes. The data leakage is possible both in scenarios of
|
| /Linux-v6.6/Documentation/locking/ |
| D | lockdep-design.rst | 346 normally results from lock-class leakage or failure to properly
350 will result in lock-class leakage. The issue here is that each
|
