| /Linux-v5.4/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.4/Documentation/x86/ |
| D | mds.rst | 32 Hyper-Threads so cross thread leakage is possible.
40 thread leakage is possible.
|
| /Linux-v5.4/drivers/gpu/drm/radeon/ |
| D | si_dpm.c | 1773 u16 v, s32 t, u32 ileakage, u32 *leakage) in si_calculate_leakage_for_v_and_t_formula() argument
1796 *leakage = drm_fixp2int(leakage_w * 1000); in si_calculate_leakage_for_v_and_t_formula()
1804 u32 *leakage) in si_calculate_leakage_for_v_and_t() argument
1806 si_calculate_leakage_for_v_and_t_formula(coeff, v, t, i_leakage, leakage); in si_calculate_leakage_for_v_and_t()
1811 u32 ileakage, u32 *leakage) in si_calculate_leakage_for_v_formula() argument
1824 *leakage = drm_fixp2int(leakage_w * 1000); in si_calculate_leakage_for_v_formula()
1832 u32 *leakage) in si_calculate_leakage_for_v() argument
1834 si_calculate_leakage_for_v_formula(coeff, fixed_kt, v, i_leakage, leakage); in si_calculate_leakage_for_v()
2585 u32 leakage; in si_init_dte_leakage_table() local
2605 &leakage); in si_init_dte_leakage_table()
[all …]
|
| D | ni_dpm.c | 745 u32 *leakage) in ni_calculate_leakage_for_v_and_t_formula() argument
760 *leakage = drm_fixp2int(leakage_w * 1000); in ni_calculate_leakage_for_v_and_t_formula()
768 u32 *leakage) in ni_calculate_leakage_for_v_and_t() argument
770 ni_calculate_leakage_for_v_and_t_formula(coeff, v, t, i_leakage, leakage); in ni_calculate_leakage_for_v_and_t()
3051 u32 leakage = 0; in ni_init_driver_calculated_leakage_table() local
3076 &leakage); in ni_init_driver_calculated_leakage_table()
3078 smc_leakage = ni_scale_power_for_smc(leakage, scaling_factor) / 1000; in ni_init_driver_calculated_leakage_table()
3121 smc_leakage = leakage_table->entries[j].leakage; in ni_init_simplified_leakage_table()
|
| D | ci_dpm.c | 298 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()
2352 rdev->pm.dpm.dyn_state.cac_leakage_table.entries[idx].leakage * VOLTAGE_SCALE; in ci_get_std_voltage_value_sidd()
2369 rdev->pm.dpm.dyn_state.cac_leakage_table.entries[idx].leakage * VOLTAGE_SCALE; in ci_get_std_voltage_value_sidd()
3509 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()
|
| D | radeon.h | 1398 u32 leakage; member
|
| /Linux-v5.4/drivers/gpu/drm/amd/amdgpu/ |
| D | si_dpm.c | 1864 u16 v, s32 t, u32 ileakage, u32 *leakage) in si_calculate_leakage_for_v_and_t_formula() argument
1887 *leakage = drm_fixp2int(leakage_w * 1000); in si_calculate_leakage_for_v_and_t_formula()
1895 u32 *leakage) in si_calculate_leakage_for_v_and_t() argument
1897 si_calculate_leakage_for_v_and_t_formula(coeff, v, t, i_leakage, leakage); in si_calculate_leakage_for_v_and_t()
1902 u32 ileakage, u32 *leakage) in si_calculate_leakage_for_v_formula() argument
1915 *leakage = drm_fixp2int(leakage_w * 1000); in si_calculate_leakage_for_v_formula()
1923 u32 *leakage) in si_calculate_leakage_for_v() argument
1925 si_calculate_leakage_for_v_formula(coeff, fixed_kt, v, i_leakage, leakage); in si_calculate_leakage_for_v()
2682 u32 leakage; in si_init_dte_leakage_table() local
2702 &leakage); in si_init_dte_leakage_table()
[all …]
|
| D | amdgpu_dpm.h | 136 u32 leakage; member
|
| D | amdgpu_dpm.c | 463 adev->pm.dpm.dyn_state.cac_leakage_table.entries[i].leakage = in amdgpu_parse_extended_power_table()
|
| /Linux-v5.4/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 | rk3328.dtsi | 532 cpu_leakage: cpu-leakage@17 {
535 logic_leakage: logic-leakage@19 {
|
| D | rk3399-gru.dtsi | 781 * prevent leakage.
|
| D | rk3368.dtsi | 783 cpu_leakage: cpu-leakage@17 {
|
| /Linux-v5.4/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.4/drivers/nvmem/ |
| D | Kconfig | 117 from eFuse, such as cpu-leakage.
|
| /Linux-v5.4/Documentation/core-api/ |
| D | kernel-api.rst | 346 called a *retention mode*. This mode still incurs leakage currents,
|
| /Linux-v5.4/Documentation/locking/ |
| D | lockdep-design.rst | 343 normally results from lock-class leakage or failure to properly
347 will result in lock-class leakage. The issue here is that each
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | perf-security.rst | 11 monitored processes. The data leakage is possible both in scenarios of
|
| /Linux-v5.4/Documentation/admin-guide/hw-vuln/ |
| D | mds.rst | 209 This only covers the host to guest transition, i.e. prevents leakage from
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-class-power | 660 is turned off in order to reduce the leakage from the BAT pin to less
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | fscrypt.rst | 371 being encrypted. In addition, to reduce leakage of filename lengths
|
