This series implements DPTF power participant driver. Intel ® Dynamic
Platform and Thermal Framework (Intel ® DPTF) platform Power Participant
is responsible for exposing platform telemetry such as
-Platform Power
-Battery Information such as State of Charge, estimated maximum
sustainable power (PMax), SMART battery spec information
Intel ® DPTF Power Participant loads as an ACPI Device (INT3407). This
device utilizes and exposes the platform power and Fuel Gauge information
and capabilities to the framework and for the policies to take control
action.
Implementation wise this is power supply battery driver with additional
attributes for platform power objects.
So the first patch splits the battery driver into two parts, a common part
and a ACPI battery enumeration part.
Next two patches add support for dptf power driver which uses common
battery driver and adds additional attributes for platform power.
v2:
When both CONFIG_ACPI_BATTERY and CONFIG_DPTF_POWER are defined and
platform has support for INT3407, then dptf power registration is
delayed for 100ms. In 100 ms, if there is no ACPI battery is registered
then dptf power will be registered. Since both can be modules and
battery driver loads in async thread, there can be race even if we
specify loading order for initialization.
Srinivas Pandruvada (3):
acpi: battery: Split battery driver for reuse by DPTF power
participant
acpi: dptf_power: Add DPTF power participant
acpi: battery_common: battery present status for INT3407
drivers/acpi/Kconfig | 22 +
drivers/acpi/Makefile | 2 +
drivers/acpi/battery.c | 1199 +------------------------------------
drivers/acpi/battery.h | 31 +
drivers/acpi/battery_common.c | 1299 +++++++++++++++++++++++++++++++++++++++++
drivers/acpi/dptf_power.c | 184 ++++++
6 files changed, 1543 insertions(+), 1194 deletions(-)
create mode 100644 drivers/acpi/battery_common.c
create mode 100644 drivers/acpi/dptf_power.c
--
2.5.0
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
