| /Linux-v5.15/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-v5.15/arch/arm/boot/dts/ |
| D | berlin2cd-valve-steamlink.dts | 42 * less depending on leakage value in OTP), and buck2 likely used for
|
| D | sun8i-a83t-bananapi-m3.dts | 316 * avoid any leakage or mismatch.
|
| D | omap3-pandora-common.dtsi | 216 * disabling this regulator causes current leakage, and LCD flicker
|
| /Linux-v5.15/Documentation/ABI/testing/ |
| D | sysfs-class-power-ltc4162l | 72 by reducing the leakage to about 2.8 microamps. The chip will
|
| D | sysfs-class-power | 701 is turned off in order to reduce the leakage from the BAT pin to less
|
| /Linux-v5.15/Documentation/devicetree/bindings/reserved-memory/ |
| D | reserved-memory.txt | 63 leakage or corruption. The feature on its own provides a basic level
65 unexpected times. However, to protect against general data leakage and
|
| /Linux-v5.15/Documentation/devicetree/bindings/power/ |
| D | power_domain.txt | 4 used for power gating of selected IP blocks for power saving by reduced leakage
|
| /Linux-v5.15/drivers/nvmem/ |
| D | Kconfig | 147 from eFuse, such as cpu-leakage.
158 from otp, such as cpu-leakage.
|
| /Linux-v5.15/Documentation/x86/ |
| D | mds.rst | 32 Hyper-Threads so cross thread leakage is possible.
40 thread leakage is possible.
|
| /Linux-v5.15/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()
3052 u32 leakage = 0; in ni_init_driver_calculated_leakage_table() local
3077 &leakage); in ni_init_driver_calculated_leakage_table()
3079 smc_leakage = ni_scale_power_for_smc(leakage, scaling_factor) / 1000; in ni_init_driver_calculated_leakage_table()
3122 smc_leakage = leakage_table->entries[j].leakage; in ni_init_simplified_leakage_table()
|
| D | ci_dpm.c | 274 hi_vid[i] = ci_convert_to_vid((u16)rdev->pm.dpm.dyn_state.cac_leakage_table.entries[i].leakage); in ci_populate_bapm_vddc_vid_sidd()
2316 rdev->pm.dpm.dyn_state.cac_leakage_table.entries[idx].leakage * VOLTAGE_SCALE; in ci_get_std_voltage_value_sidd()
2333 rdev->pm.dpm.dyn_state.cac_leakage_table.entries[idx].leakage * VOLTAGE_SCALE; in ci_get_std_voltage_value_sidd()
3473 std_voltage_table->entries[i].leakage; in ci_setup_default_dpm_tables()
|
| D | r600_dpm.c | 1056 rdev->pm.dpm.dyn_state.cac_leakage_table.entries[i].leakage = in r600_parse_extended_power_table()
|
| /Linux-v5.15/drivers/gpu/drm/amd/pm/powerplay/ |
| D | si_dpm.c | 1844 u16 v, s32 t, u32 ileakage, u32 *leakage) in si_calculate_leakage_for_v_and_t_formula() argument
1867 *leakage = drm_fixp2int(leakage_w * 1000); in si_calculate_leakage_for_v_and_t_formula()
1875 u32 *leakage) in si_calculate_leakage_for_v_and_t() argument
1877 si_calculate_leakage_for_v_and_t_formula(coeff, v, t, i_leakage, leakage); in si_calculate_leakage_for_v_and_t()
1882 u32 ileakage, u32 *leakage) in si_calculate_leakage_for_v_formula() argument
1895 *leakage = drm_fixp2int(leakage_w * 1000); in si_calculate_leakage_for_v_formula()
1903 u32 *leakage) in si_calculate_leakage_for_v() argument
1905 si_calculate_leakage_for_v_formula(coeff, fixed_kt, v, i_leakage, leakage); in si_calculate_leakage_for_v()
2662 u32 leakage; in si_init_dte_leakage_table() local
2682 &leakage); in si_init_dte_leakage_table()
[all …]
|
| /Linux-v5.15/arch/arm64/boot/dts/rockchip/ |
| D | rk3399-gru-chromebook.dtsi | 280 * Note strange pullup enable. Apparently this avoids leakage but
|
| D | rk3399.dtsi | 1317 cpub_leakage: cpu-leakage@17 {
1320 gpu_leakage: gpu-leakage@18 {
1323 center_leakage: center-leakage@19 {
1326 cpul_leakage: cpu-leakage@1a {
1329 logic_leakage: logic-leakage@1b {
|
| D | rk3399-gru.dtsi | 784 * prevent leakage.
|
| D | rk3328.dtsi | 576 cpu_leakage: cpu-leakage@17 {
579 logic_leakage: logic-leakage@19 {
|
| D | rk3368.dtsi | 775 cpu_leakage: cpu-leakage@17 {
|
| /Linux-v5.15/drivers/gpu/drm/amd/pm/inc/ |
| D | amdgpu_dpm.h | 136 u32 leakage; member
|
| /Linux-v5.15/Documentation/core-api/ |
| D | kernel-api.rst | 346 called a *retention mode*. This mode still incurs leakage currents,
|
| /Linux-v5.15/Documentation/admin-guide/hw-vuln/ |
| D | mds.rst | 209 This only covers the host to guest transition, i.e. prevents leakage from
|
| /Linux-v5.15/Documentation/admin-guide/ |
| D | perf-security.rst | 11 monitored processes. The data leakage is possible both in scenarios of
|
| /Linux-v5.15/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
|
