diff options
| author | Kane Chen <kane.chen@intel.com> | 2022-11-10 23:39:24 +0800 |
|---|---|---|
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2022-11-10 20:43:30 +0100 |
| commit | dc776bd3eb907f0e1dcb4e4b5307ace2a4962b20 (patch) | |
| tree | 94f4679650d956334a7abea2628417e66338b493 /drivers/acpi/power.c | |
| parent | f0c4d9fc9cc9462659728d168387191387e903cc (diff) | |
ACPI: PM: Print full name path while adding power resource
While debugging a boot-time issue, it's hard to know what ACPI power
resource the kernel is initializing.
It's very helpful to print the full name path of the power resource
being added so that it is not necessary to guess which one it is,
especially on a system with 2 ore more power resources where the
last name path segment is the same.
Before:
ACPI: PM: Power Resource [RTD3]
ACPI: PM: Power Resource [RTD3]
ACPI: PM: Power Resource [PR00]
ACPI: PM: Power Resource [PR01]
After:
ACPI: \_SB_.PCI0.RP01.RTD3: New power resource
ACPI: \_SB_.PCI0.RP08.RTD3: New power resource
ACPI: \_SB_.PCI0.I2C3.H016.PR00: New power resource
ACPI: \_SB_.PCI0.SPI1.CRFP.PR01: New power resource
Signed-off-by: Kane Chen <kane.chen@intel.com>
[ rjw: Subject and changelog edits ]
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/acpi/power.c')
| -rw-r--r-- | drivers/acpi/power.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/acpi/power.c b/drivers/acpi/power.c index f2588aba8421..23507d29f000 100644 --- a/drivers/acpi/power.c +++ b/drivers/acpi/power.c @@ -967,7 +967,7 @@ struct acpi_device *acpi_add_power_resource(acpi_handle handle) if (acpi_power_get_state(resource, &state_dummy)) __acpi_power_on(resource); - pr_info("%s [%s]\n", acpi_device_name(device), acpi_device_bid(device)); + acpi_handle_info(handle, "New power resource\n"); result = acpi_tie_acpi_dev(device); if (result) |