From: Aaron Lu <aaron.lu@intel.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>,
Yinghai Lu <yinghai@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>, Tejun Heo <tj@kernel.org>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH 2/3] ACPI / PM: Make messages in acpi_device_set_power() print device names
Date: Wed, 31 Jul 2013 14:52:53 +0800 [thread overview]
Message-ID: <51F8B445.1070000@intel.com> (raw)
In-Reply-To: <4285597.UpTJrMA8Fu@vostro.rjw.lan>
On 07/29/2013 08:20 PM, Rafael J. Wysocki wrote:
> On Monday, July 29, 2013 10:29:36 AM Aaron Lu wrote:
>> On 07/27/2013 09:11 PM, Rafael J. Wysocki wrote:
>>> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>>>
>>> Modify acpi_device_set_power() so that diagnostic messages printed by
>>> it to the kernel log always contain the name of the device concerned
>>> to make it possible to identify the device that triggered the message
>>> if need be.
>>>
>>> Also replace printk(KERN_WARNING ) with dev_warn() everywhere in that
>>> function.
>>>
>>> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>>> ---
>>> drivers/acpi/device_pm.c | 22 ++++++++++------------
>>> 1 file changed, 10 insertions(+), 12 deletions(-)
>>>
>>> Index: linux-pm/drivers/acpi/device_pm.c
>>> ===================================================================
>>> --- linux-pm.orig/drivers/acpi/device_pm.c
>>> +++ linux-pm/drivers/acpi/device_pm.c
>>> @@ -166,20 +166,20 @@ int acpi_device_set_power(struct acpi_de
>>> /* Make sure this is a valid target state */
>>>
>>> if (state == device->power.state) {
>>> - ACPI_DEBUG_PRINT((ACPI_DB_INFO, "Device is already at %s\n",
>>> + ACPI_DEBUG_PRINT((ACPI_DB_INFO, "Device [%s] already in %s\n",
>>> + device->pnp.bus_id,
>>> acpi_power_state_string(state)));
>>> return 0;
>>> }
>>>
>>> if (!device->power.states[state].flags.valid) {
>>> - printk(KERN_WARNING PREFIX "Device does not support %s\n",
>>> - acpi_power_state_string(state));
>>> + dev_warn(&device->dev, "Power state %s not supported\n",
>>> + acpi_power_state_string(state));
>>> return -ENODEV;
>>> }
>>> if (device->parent && (state < device->parent->power.state)) {
>>> - printk(KERN_WARNING PREFIX
>>> - "Cannot set device to a higher-powered"
>>> - " state than parent\n");
>>> + dev_warn(&device->dev, "Cannot transition to a higher-powered "
>>> + "state than parent\n");
>>
>> I think the state information would also be useful here:
>>
>> dev_warn(&device->dev, "Cannot transition to a higher-powereed "
>> "state %d than paeren's state %d\n", state,
>> device->parent->power.state);
>
> This is not the scope of this patch, please send another one on top of it.
>
Patch to add state information in error message, apply on top of this
one.
From: Aaron Lu <aaron.lu@intel.com>
Subject: [PATCH] ACPI / PM: Add state information in error message for
acpi_device_set_power
The state information can be useful to know what the problem is when it
appeared in an error message about a device can not being set to a higher
power state than its parent, so this patch adds such state information
for both the target state of the device failed to be set and the current
parent's state.
Signed-off-by: Aaron Lu <aaron.lu@intel.com>
---
drivers/acpi/device_pm.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/acpi/device_pm.c b/drivers/acpi/device_pm.c
index beb9625..707258b 100644
--- a/drivers/acpi/device_pm.c
+++ b/drivers/acpi/device_pm.c
@@ -179,7 +179,8 @@ int acpi_device_set_power(struct acpi_device *device, int state)
}
if (device->parent && (state < device->parent->power.state)) {
dev_warn(&device->dev,
- "Cannot transition to a higher-powered state than parent\n");
+ "Cannot transition to a higher-powered state %d than parent's state %d\n",
+ state, device->parent->power.state);
return -ENODEV;
}
--
1.8.3.2.10.g43d11f4
next prev parent reply other threads:[~2013-07-31 6:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-27 13:09 [PATCH 0/3] ACPI / PM: Device PM cleanups Rafael J. Wysocki
2013-07-27 13:10 ` [PATCH 1/3] ACPI / PM: Only set power states of devices that are power manageable Rafael J. Wysocki
2013-07-29 14:09 ` Aaron Lu
2013-07-29 22:21 ` Rafael J. Wysocki
2013-07-29 23:43 ` Aaron Lu
2013-07-30 14:04 ` Rafael J. Wysocki
2013-07-31 6:48 ` Aaron Lu
2013-07-31 10:29 ` Rafael J. Wysocki
2013-07-27 13:11 ` [PATCH 2/3] ACPI / PM: Make messages in acpi_device_set_power() print device names Rafael J. Wysocki
2013-07-29 2:29 ` Aaron Lu
2013-07-29 12:20 ` Rafael J. Wysocki
2013-07-31 6:52 ` Aaron Lu [this message]
2013-07-31 10:27 ` Rafael J. Wysocki
2013-08-01 0:49 ` [PATCH updated] ACPI / PM: Add state information in error message for acpi_device_set_power Aaron Lu
2013-07-29 3:06 ` [PATCH 2/3] ACPI / PM: Make messages in acpi_device_set_power() print device names Lan Tianyu
2013-07-29 3:11 ` Joe Perches
2013-07-29 12:17 ` Rafael J. Wysocki
2013-07-29 12:16 ` Sergei Shtylyov
2013-07-29 13:36 ` Rafael J. Wysocki
2013-07-29 14:15 ` Aaron Lu
2013-07-29 12:11 ` Rafael J. Wysocki
2013-07-27 13:14 ` [PATCH 3/3] ACPI / PM: Use ACPI_STATE_D3_COLD instead of ACPI_STATE_D3 everywhere Rafael J. Wysocki
2013-07-29 14:28 ` Aaron Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51F8B445.1070000@intel.com \
--to=aaron.lu@intel.com \
--cc=bhelgaas@google.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=tj@kernel.org \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).