2018-02-10 08:57:19 +00:00
|
|
|
What: /sys/bus/platform/devices/INT3407:00/dptf_power/charger_type
|
|
|
|
|
Date: Jul, 2016
|
|
|
|
|
KernelVersion: v4.10
|
|
|
|
|
Contact: linux-acpi@vger.kernel.org
|
|
|
|
|
Description:
|
|
|
|
|
(RO) The charger type - Traditional, Hybrid or NVDC.
|
|
|
|
|
|
|
|
|
|
What: /sys/bus/platform/devices/INT3407:00/dptf_power/adapter_rating_mw
|
|
|
|
|
Date: Jul, 2016
|
|
|
|
|
KernelVersion: v4.10
|
|
|
|
|
Contact: linux-acpi@vger.kernel.org
|
|
|
|
|
Description:
|
|
|
|
|
(RO) Adapter rating in milliwatts (the maximum Adapter power).
|
|
|
|
|
Must be 0 if no AC Adaptor is plugged in.
|
|
|
|
|
|
|
|
|
|
What: /sys/bus/platform/devices/INT3407:00/dptf_power/max_platform_power_mw
|
|
|
|
|
Date: Jul, 2016
|
|
|
|
|
KernelVersion: v4.10
|
|
|
|
|
Contact: linux-acpi@vger.kernel.org
|
|
|
|
|
Description:
|
|
|
|
|
(RO) Maximum platform power that can be supported by the battery
|
|
|
|
|
in milliwatts.
|
|
|
|
|
|
|
|
|
|
What: /sys/bus/platform/devices/INT3407:00/dptf_power/platform_power_source
|
|
|
|
|
Date: Jul, 2016
|
|
|
|
|
KernelVersion: v4.10
|
|
|
|
|
Contact: linux-acpi@vger.kernel.org
|
|
|
|
|
Description:
|
|
|
|
|
(RO) Display the platform power source
|
2020-10-30 07:40:47 +00:00
|
|
|
|
|
|
|
|
========= ============================
|
ACPI: DPTF: Additional sysfs attributes for power participant driver
Add two additional attributes to the existing power participant driver:
rest_of_platform_power_mw: (RO) Shows the rest of worst case platform
power in mW outside of S0C. This will help in power distribution to SoC
and rest of the system. For example on a test system, this value is 2.5W
with a 15W TDP SoC. Based on the adapter rating (adapter_rating_mw), user
space software can decide on proper power allocation to SoC to improve
short term performance via powercap/RAPL interface.
prochot_confirm: (WO) Confirm EC about a prochot notification.
Also userspace is notified via sysfs_notify(), whenever power source or
rest of the platform power is changed. So user space can use poll()
system call on those attributes.
The ACPI methods used in this patch are as follows:
PROP
This object evaluates to the rest of worst case platform power in mW.
Bits:
23:0 Worst case rest of platform power in mW.
PBOK
PBOK is a method designed to provide a mechanism for OSPM to change power
setting before EC can de-assert a PROCHOT from a device. The EC may
receive several PROCHOTs, so it has a sequence number attached to PSRC
(read via existing attribute "platform_power_source"). Once OSPM takes
action for a PSRC change notification, it can call PBOK method to confirm
with the sequence number.
Bits:
3:0 Power Delivery State Change Sequence number
30 Reserved
31 0 – Not OK to de-assert PROCHOT
1 – OK to de-assert PROCHOT
PSRC (Platform Power Source): Not new in this patch but for
documentation for new bits
This object evaluates to an integer that represents the system power
source as well as the power delivery state change sequence number.
Bits:
3:0 The current power source as an integer for AC, DC, USB, Wireless.
0 = DC, 1 = AC, 2 = USB, 3 = Wireless Charging
7:4 Power Delivery State Change Sequence Number. Default value is 0
Notifications:
0x81: (Power State Change) Used to notify when the power source has
changed.
0x84: (PROP change) Used to notify when the platform rest of power has
changed.
Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
[ rjw: Subject, minor ABI documentation edit ]
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2020-05-21 20:30:15 +00:00
|
|
|
bits[3:0] Current power source
|
2020-10-30 07:40:47 +00:00
|
|
|
- 0x00 = DC
|
|
|
|
|
- 0x01 = AC
|
|
|
|
|
- 0x02 = USB
|
|
|
|
|
- 0x03 = Wireless Charger
|
ACPI: DPTF: Additional sysfs attributes for power participant driver
Add two additional attributes to the existing power participant driver:
rest_of_platform_power_mw: (RO) Shows the rest of worst case platform
power in mW outside of S0C. This will help in power distribution to SoC
and rest of the system. For example on a test system, this value is 2.5W
with a 15W TDP SoC. Based on the adapter rating (adapter_rating_mw), user
space software can decide on proper power allocation to SoC to improve
short term performance via powercap/RAPL interface.
prochot_confirm: (WO) Confirm EC about a prochot notification.
Also userspace is notified via sysfs_notify(), whenever power source or
rest of the platform power is changed. So user space can use poll()
system call on those attributes.
The ACPI methods used in this patch are as follows:
PROP
This object evaluates to the rest of worst case platform power in mW.
Bits:
23:0 Worst case rest of platform power in mW.
PBOK
PBOK is a method designed to provide a mechanism for OSPM to change power
setting before EC can de-assert a PROCHOT from a device. The EC may
receive several PROCHOTs, so it has a sequence number attached to PSRC
(read via existing attribute "platform_power_source"). Once OSPM takes
action for a PSRC change notification, it can call PBOK method to confirm
with the sequence number.
Bits:
3:0 Power Delivery State Change Sequence number
30 Reserved
31 0 – Not OK to de-assert PROCHOT
1 – OK to de-assert PROCHOT
PSRC (Platform Power Source): Not new in this patch but for
documentation for new bits
This object evaluates to an integer that represents the system power
source as well as the power delivery state change sequence number.
Bits:
3:0 The current power source as an integer for AC, DC, USB, Wireless.
0 = DC, 1 = AC, 2 = USB, 3 = Wireless Charging
7:4 Power Delivery State Change Sequence Number. Default value is 0
Notifications:
0x81: (Power State Change) Used to notify when the power source has
changed.
0x84: (PROP change) Used to notify when the platform rest of power has
changed.
Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
[ rjw: Subject, minor ABI documentation edit ]
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2020-05-21 20:30:15 +00:00
|
|
|
bits[7:4] Power source sequence number
|
2020-10-30 07:40:47 +00:00
|
|
|
========= ============================
|
2018-02-10 08:57:19 +00:00
|
|
|
|
|
|
|
|
What: /sys/bus/platform/devices/INT3407:00/dptf_power/battery_steady_power
|
|
|
|
|
Date: Jul, 2016
|
|
|
|
|
KernelVersion: v4.10
|
|
|
|
|
Contact: linux-acpi@vger.kernel.org
|
|
|
|
|
Description:
|
|
|
|
|
(RO) The maximum sustained power for battery in milliwatts.
|
ACPI: DPTF: Additional sysfs attributes for power participant driver
Add two additional attributes to the existing power participant driver:
rest_of_platform_power_mw: (RO) Shows the rest of worst case platform
power in mW outside of S0C. This will help in power distribution to SoC
and rest of the system. For example on a test system, this value is 2.5W
with a 15W TDP SoC. Based on the adapter rating (adapter_rating_mw), user
space software can decide on proper power allocation to SoC to improve
short term performance via powercap/RAPL interface.
prochot_confirm: (WO) Confirm EC about a prochot notification.
Also userspace is notified via sysfs_notify(), whenever power source or
rest of the platform power is changed. So user space can use poll()
system call on those attributes.
The ACPI methods used in this patch are as follows:
PROP
This object evaluates to the rest of worst case platform power in mW.
Bits:
23:0 Worst case rest of platform power in mW.
PBOK
PBOK is a method designed to provide a mechanism for OSPM to change power
setting before EC can de-assert a PROCHOT from a device. The EC may
receive several PROCHOTs, so it has a sequence number attached to PSRC
(read via existing attribute "platform_power_source"). Once OSPM takes
action for a PSRC change notification, it can call PBOK method to confirm
with the sequence number.
Bits:
3:0 Power Delivery State Change Sequence number
30 Reserved
31 0 – Not OK to de-assert PROCHOT
1 – OK to de-assert PROCHOT
PSRC (Platform Power Source): Not new in this patch but for
documentation for new bits
This object evaluates to an integer that represents the system power
source as well as the power delivery state change sequence number.
Bits:
3:0 The current power source as an integer for AC, DC, USB, Wireless.
0 = DC, 1 = AC, 2 = USB, 3 = Wireless Charging
7:4 Power Delivery State Change Sequence Number. Default value is 0
Notifications:
0x81: (Power State Change) Used to notify when the power source has
changed.
0x84: (PROP change) Used to notify when the platform rest of power has
changed.
Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
[ rjw: Subject, minor ABI documentation edit ]
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2020-05-21 20:30:15 +00:00
|
|
|
|
|
|
|
|
What: /sys/bus/platform/devices/INT3407:00/dptf_power/rest_of_platform_power_mw
|
|
|
|
|
Date: June, 2020
|
|
|
|
|
KernelVersion: v5.8
|
|
|
|
|
Contact: linux-acpi@vger.kernel.org
|
|
|
|
|
Description:
|
|
|
|
|
(RO) Shows the rest (outside of SoC) of worst-case platform power.
|
|
|
|
|
|
|
|
|
|
What: /sys/bus/platform/devices/INT3407:00/dptf_power/prochot_confirm
|
|
|
|
|
Date: June, 2020
|
|
|
|
|
KernelVersion: v5.8
|
|
|
|
|
Contact: linux-acpi@vger.kernel.org
|
|
|
|
|
Description:
|
|
|
|
|
(WO) Confirm embedded controller about a prochot notification.
|
2020-05-22 21:45:09 +00:00
|
|
|
|
|
|
|
|
What: /sys/bus/platform/devices/INT3532:00/dptf_battery/max_platform_power_mw
|
|
|
|
|
Date: June, 2020
|
|
|
|
|
KernelVersion: v5.8
|
|
|
|
|
Contact: linux-acpi@vger.kernel.org
|
|
|
|
|
Description:
|
|
|
|
|
(RO) The maximum platform power that can be supported by the battery in milli watts.
|
|
|
|
|
|
|
|
|
|
What: /sys/bus/platform/devices/INT3532:00/dptf_battery/max_steady_state_power_mw
|
|
|
|
|
Date: June, 2020
|
|
|
|
|
KernelVersion: v5.8
|
|
|
|
|
Contact: linux-acpi@vger.kernel.org
|
|
|
|
|
Description:
|
|
|
|
|
(RO) The maximum sustained power for battery in milli watts.
|
|
|
|
|
|
|
|
|
|
What: /sys/bus/platform/devices/INT3532:00/dptf_battery/high_freq_impedance_mohm
|
|
|
|
|
Date: June, 2020
|
|
|
|
|
KernelVersion: v5.8
|
|
|
|
|
Contact: linux-acpi@vger.kernel.org
|
|
|
|
|
Description:
|
|
|
|
|
(RO) The high frequency impedance value that can be obtained from battery
|
|
|
|
|
fuel gauge in milli Ohms.
|
|
|
|
|
|
|
|
|
|
What: /sys/bus/platform/devices/INT3532:00/dptf_battery/no_load_voltage_mv
|
|
|
|
|
Date: June, 2020
|
|
|
|
|
KernelVersion: v5.8
|
|
|
|
|
Contact: linux-acpi@vger.kernel.org
|
|
|
|
|
Description:
|
|
|
|
|
(RO) The no-load voltage that can be obtained from battery fuel gauge in
|
|
|
|
|
milli volts.
|
|
|
|
|
|
|
|
|
|
What: /sys/bus/platform/devices/INT3532:00/dptf_battery/current_discharge_capbility_ma
|
|
|
|
|
Date: June, 2020
|
|
|
|
|
KernelVersion: v5.8
|
|
|
|
|
Contact: linux-acpi@vger.kernel.org
|
|
|
|
|
Description:
|
|
|
|
|
(RO) The battery discharge current capability obtained from battery fuel gauge in
|
|
|
|
|
milli Amps.
|
2020-09-15 23:18:14 +00:00
|
|
|
|
|
|
|
|
What: /sys/bus/platform/devices/INTC1045:00/pch_fivr_switch_frequency/freq_mhz_low_clock
|
|
|
|
|
Date: November, 2020
|
|
|
|
|
KernelVersion: v5.10
|
|
|
|
|
Contact: linux-acpi@vger.kernel.org
|
|
|
|
|
Description:
|
|
|
|
|
(RW) The PCH FIVR (Fully Integrated Voltage Regulator) switching frequency in MHz,
|
|
|
|
|
when FIVR clock is 19.2MHz or 24MHz.
|
|
|
|
|
|
|
|
|
|
What: /sys/bus/platform/devices/INTC1045:00/pch_fivr_switch_frequency/freq_mhz_high_clock
|
|
|
|
|
Date: November, 2020
|
|
|
|
|
KernelVersion: v5.10
|
|
|
|
|
Contact: linux-acpi@vger.kernel.org
|
|
|
|
|
Description:
|
|
|
|
|
(RW) The PCH FIVR (Fully Integrated Voltage Regulator) switching frequency in MHz,
|
|
|
|
|
when FIVR clock is 38.4MHz.
|
2021-07-27 16:22:40 +00:00
|
|
|
|
|
|
|
|
What: /sys/bus/platform/devices/INTC1045:00/pch_fivr_switch_frequency/fivr_switching_freq_mhz
|
|
|
|
|
Date: September, 2021
|
|
|
|
|
KernelVersion: v5.15
|
|
|
|
|
Contact: linux-acpi@vger.kernel.org
|
|
|
|
|
Description:
|
|
|
|
|
(RO) Get the FIVR switching control frequency in MHz.
|
|
|
|
|
|
|
|
|
|
What: /sys/bus/platform/devices/INTC1045:00/pch_fivr_switch_frequency/fivr_switching_fault_status
|
|
|
|
|
Date: September, 2021
|
|
|
|
|
KernelVersion: v5.15
|
|
|
|
|
Contact: linux-acpi@vger.kernel.org
|
|
|
|
|
Description:
|
|
|
|
|
(RO) Read the FIVR switching frequency control fault status.
|
|
|
|
|
|
|
|
|
|
What: /sys/bus/platform/devices/INTC1045:00/pch_fivr_switch_frequency/ssc_clock_info
|
|
|
|
|
Date: September, 2021
|
|
|
|
|
KernelVersion: v5.15
|
|
|
|
|
Contact: linux-acpi@vger.kernel.org
|
|
|
|
|
Description:
|
|
|
|
|
(RO) Presents SSC (spread spectrum clock) information for EMI
|
|
|
|
|
(Electro magnetic interference) control. This is a bit mask.
|
2021-09-27 11:10:52 +00:00
|
|
|
|
|
|
|
|
======= ==========================================
|
2021-07-27 16:22:40 +00:00
|
|
|
Bits Description
|
2021-09-27 11:10:52 +00:00
|
|
|
======= ==========================================
|
2021-07-27 16:22:40 +00:00
|
|
|
[7:0] Sets clock spectrum spread percentage:
|
|
|
|
|
0x00=0.2% , 0x3F=10%
|
|
|
|
|
1 LSB = 0.1% increase in spread (for
|
|
|
|
|
settings 0x01 thru 0x1C)
|
|
|
|
|
1 LSB = 0.2% increase in spread (for
|
|
|
|
|
settings 0x1E thru 0x3F)
|
|
|
|
|
[8] When set to 1, enables spread
|
|
|
|
|
spectrum clock
|
|
|
|
|
[9] 0: Triangle mode. FFC frequency
|
|
|
|
|
walks around the Fcenter in a linear
|
|
|
|
|
fashion
|
|
|
|
|
1: Random walk mode. FFC frequency
|
|
|
|
|
changes randomly within the SSC
|
|
|
|
|
(Spread spectrum clock) range
|
|
|
|
|
[10] 0: No white noise. 1: Add white noise
|
|
|
|
|
to spread waveform
|
|
|
|
|
[11] When 1, future writes are ignored.
|
2021-09-27 11:10:52 +00:00
|
|
|
======= ==========================================
|