| /linux/Documentation/driver-api/thermal/ |
| H A 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/Documentation/ABI/testing/ |
| H A D | sysfs-class-power-rt9467 | 9 is turned off to reduce the leakage from the BAT pin. See
|
| H A D | sysfs-class-power-rt9471 | 8 off to reduce the leakage from the BAT pin. See device datasheet for details.
|
| H A D | sysfs-class-power-ltc4162l | 72 by reducing the leakage to about 2.8 microamps. The chip will
|
| /linux/arch/arm/boot/dts/synaptics/ |
| H A D | berlin2cd-valve-steamlink.dts | 42 * less depending on leakage value in OTP), and buck2 likely used for
|
| /linux/Documentation/devicetree/bindings/power/ |
| H A D | power_domain.txt | 4 used for power gating of selected IP blocks for power saving by reduced leakage
|
| /linux/drivers/gpu/drm/radeon/ |
| H A D | si_dpm.c | 1707 u16 v, s32 t, u32 ileakage, u32 *leakage) in si_calculate_leakage_for_v_and_t_formula() argument
1730 *leakage = drm_fixp2int(leakage_w * 1000); in si_calculate_leakage_for_v_and_t_formula()
1738 u32 *leakage) in si_calculate_leakage_for_v_and_t() argument
1740 si_calculate_leakage_for_v_and_t_formula(coeff, v, t, i_leakage, leakage); in si_calculate_leakage_for_v_and_t()
1745 u32 ileakage, u32 *leakage) in si_calculate_leakage_for_v_formula() argument
1758 *leakage = drm_fixp2int(leakage_w * 1000); in si_calculate_leakage_for_v_formula()
1766 u32 *leakage) in si_calculate_leakage_for_v() argument
1768 si_calculate_leakage_for_v_formula(coeff, fixed_kt, v, i_leakage, leakage); in si_calculate_leakage_for_v()
2519 u32 leakage; in si_init_dte_leakage_table() local
2539 &leakage); in si_init_dte_leakage_table()
[all …]
|
| H A D | r600_dpm.c | 1054 rdev->pm.dpm.dyn_state.cac_leakage_table.entries[i].leakage = in r600_parse_extended_power_table()
|
| /linux/Documentation/arch/x86/ |
| H A D | mds.rst | 32 Hyper-Threads so cross thread leakage is possible.
40 thread leakage is possible.
|
| /linux/Documentation/power/ |
| H A D | energy-model.rst | 74 To better reflect power variation due to static power (leakage) the EM
120 (leakage) is important.
181 physics of a real device, e.g. when static power (leakage) is important.
|
| /linux/drivers/gpu/drm/amd/pm/legacy-dpm/ |
| H A D | si_dpm.c | 1875 u16 v, s32 t, u32 ileakage, u32 *leakage) in si_calculate_leakage_for_v_and_t_formula() argument
1898 *leakage = drm_fixp2int(leakage_w * 1000); in si_calculate_leakage_for_v_and_t_formula()
1906 u32 *leakage) in si_calculate_leakage_for_v_and_t() argument
1908 si_calculate_leakage_for_v_and_t_formula(coeff, v, t, i_leakage, leakage); in si_calculate_leakage_for_v_and_t()
1913 u32 ileakage, u32 *leakage) in si_calculate_leakage_for_v_formula() argument
1926 *leakage = drm_fixp2int(leakage_w * 1000); in si_calculate_leakage_for_v_formula()
1934 u32 *leakage) in si_calculate_leakage_for_v() argument
1936 si_calculate_leakage_for_v_formula(coeff, fixed_kt, v, i_leakage, leakage); in si_calculate_leakage_for_v()
2687 u32 leakage; in si_init_dte_leakage_table()
2707 &leakage); in si_init_dte_leakage_table()
2691 u32 leakage; si_init_dte_leakage_table() local
2730 u32 leakage; si_init_simplified_leakage_table() local
[all...] |
| /linux/drivers/nvmem/ |
| H A D | Kconfig | 331 from eFuse, such as cpu-leakage.
342 from OTP, such as cpu-leakage.
|
| /linux/arch/arm64/boot/dts/rockchip/ |
| H A D | rk3588-base.dtsi | 3074 cpub0_leakage: cpu-leakage@17 {
3078 cpub1_leakage: cpu-leakage@18 {
3082 cpul_leakage: cpu-leakage@19 {
3086 log_leakage: log-leakage@1a {
3090 gpu_leakage: gpu-leakage@1b {
3099 npu_leakage: npu-leakage@28 {
3103 codec_leakage: codec-leakage@29 {
|
| H A D | rk3399-gru-chromebook.dtsi | 463 * Note strange pullup enable. Apparently this avoids leakage but
|
| H A D | rk3399-base.dtsi | 1511 cpub_leakage: cpu-leakage@17 {
1514 gpu_leakage: gpu-leakage@18 {
1517 center_leakage: center-leakage@19 {
1520 cpul_leakage: cpu-leakage@1a {
1523 logic_leakage: logic-leakage@1b {
|
| H A D | rk3576.dtsi | 1947 cpub_leakage: cpub-leakage@1e {
1950 cpul_leakage: cpul-leakage@1f {
1953 npu_leakage: npu-leakage@20 {
1956 gpu_leakage: gpu-leakage@21 {
1959 log_leakage: log-leakage@22 {
|
| H A D | rk3308.dtsi | 579 cpu_leakage: cpu-leakage@17 {
583 logic_leakage: logic-leakage@18 {
|
| H A D | rk3328.dtsi | 619 cpu_leakage: cpu-leakage@17 {
622 logic_leakage: logic-leakage@19 {
|
| H A D | rk3399-gru.dtsi | 819 * prevent leakage.
|
| H A D | rk3368.dtsi | 1031 cpu_leakage: cpu-leakage@17 {
|
| /linux/arch/arm/boot/dts/allwinner/ |
| H A D | sun8i-a83t-bananapi-m3.dts | 331 * avoid any leakage or mismatch.
|
| /linux/arch/arm/boot/dts/aspeed/ |
| H A D | aspeed-bmc-facebook-harma.dts | 662 "leakage-detect-alert","","","",
|
| /linux/arch/arm/boot/dts/ti/omap/ |
| H A D | omap3-pandora-common.dtsi | 216 * disabling this regulator causes current leakage, and LCD flicker
|
| /linux/Documentation/admin-guide/ |
| H A D | perf-security.rst | 11 monitored processes. The data leakage is possible both in scenarios of
|
| /linux/Documentation/locking/ |
| H A 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
|