From: Lan Tianyu <tianyu.lan@intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: David Rientjes <rientjes@google.com>,
lenb@kernel.org, naszar@ya.ru, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] ACPI/Battery: Retry to get Battery information if failed during probing
Date: Thu, 19 Jun 2014 14:48:09 +0800 [thread overview]
Message-ID: <53A287A9.7000203@intel.com> (raw)
In-Reply-To: <2223803.V8Foed99uq@vostro.rjw.lan>
On 2014年06月19日 07:00, Rafael J. Wysocki wrote:
> On Wednesday, June 18, 2014 03:15:47 PM David Rientjes wrote:
>> On Tue, 17 Jun 2014, Rafael J. Wysocki wrote:
>>
>>>> diff --git a/drivers/acpi/battery.c b/drivers/acpi/battery.c
>>>> index e48fc98..8ed93a3 100644
>>>> --- a/drivers/acpi/battery.c
>>>> +++ b/drivers/acpi/battery.c
>>>> @@ -34,6 +34,7 @@
>>>> #include <linux/dmi.h>
>>>> #include <linux/slab.h>
>>>> #include <linux/suspend.h>
>>>> +#include <linux/delay.h>
>>>> #include <asm/unaligned.h>
>>>>
>>>> #ifdef CONFIG_ACPI_PROCFS_POWER
>>>> @@ -1119,7 +1120,7 @@ static struct dmi_system_id bat_dmi_table[] = {
>>>>
>>>> static int acpi_battery_add(struct acpi_device *device)
>>>> {
>>>> - int result = 0;
>>>> + int result = 0, retry = 5;
>>>> struct acpi_battery *battery = NULL;
>>>>
>>>> if (!device)
>>>> @@ -1135,9 +1136,20 @@ static int acpi_battery_add(struct acpi_device *device)
>>>> mutex_init(&battery->sysfs_lock);
>>>> if (acpi_has_method(battery->device->handle, "_BIX"))
>>>> set_bit(ACPI_BATTERY_XINFO_PRESENT, &battery->flags);
>>>> - result = acpi_battery_update(battery, false);
>>>> +
>>>> + /*
>>>> + * Some machines'(E,G Lenovo Z480) ECs are not stable
>>>> + * during boot up and this causes battery driver fails to be
>>>> + * probed due to failure of getting battery information
>>>> + * from EC sometimes. After several retries, the operation
>>>> + * may work. So add retry code here and 20ms sleep between
>>>> + * every retries.
>>>> + */
>>>> + while ((result = acpi_battery_update(battery, false)) && retry--)
>>>> + msleep(20);
>>>> if (result)
>>>> goto fail;
>>>
>>> Why not to write this as
>>>
>>> for (;;) {
>>> result = acpi_battery_update(battery, false);
>>> if (!result)
>>> break;
>>> else if (!--retry)
>>> goto fail;
>>>
>>> msleep(20);
>>> }
>>>
>>
>> I suggested a similar for loop earlier, I think it's cleaner.
>
> Precisely. And it would be even more clean to introduce
>
> static bool acpi_battery_update_retry(struct acpi_battery *battery)
> {
> int retry, ret;
>
> for (retry = 5; retry; retry--) {
> ret = acpi_battery_update(battery, false);
> if (!ret)
> break;
>
> msleep(20);
> }
> return ret;
> }
>
> and use that instead of the open-coded loop.
Ok. I will update patch like this.
>
> Rafael
>
--
Best regards
Tianyu Lan
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Lan Tianyu <tianyu.lan@intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: David Rientjes <rientjes@google.com>,
lenb@kernel.org, naszar@ya.ru, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] ACPI/Battery: Retry to get Battery information if failed during probing
Date: Thu, 19 Jun 2014 14:48:09 +0800 [thread overview]
Message-ID: <53A287A9.7000203@intel.com> (raw)
In-Reply-To: <2223803.V8Foed99uq@vostro.rjw.lan>
On 2014年06月19日 07:00, Rafael J. Wysocki wrote:
> On Wednesday, June 18, 2014 03:15:47 PM David Rientjes wrote:
>> On Tue, 17 Jun 2014, Rafael J. Wysocki wrote:
>>
>>>> diff --git a/drivers/acpi/battery.c b/drivers/acpi/battery.c
>>>> index e48fc98..8ed93a3 100644
>>>> --- a/drivers/acpi/battery.c
>>>> +++ b/drivers/acpi/battery.c
>>>> @@ -34,6 +34,7 @@
>>>> #include <linux/dmi.h>
>>>> #include <linux/slab.h>
>>>> #include <linux/suspend.h>
>>>> +#include <linux/delay.h>
>>>> #include <asm/unaligned.h>
>>>>
>>>> #ifdef CONFIG_ACPI_PROCFS_POWER
>>>> @@ -1119,7 +1120,7 @@ static struct dmi_system_id bat_dmi_table[] = {
>>>>
>>>> static int acpi_battery_add(struct acpi_device *device)
>>>> {
>>>> - int result = 0;
>>>> + int result = 0, retry = 5;
>>>> struct acpi_battery *battery = NULL;
>>>>
>>>> if (!device)
>>>> @@ -1135,9 +1136,20 @@ static int acpi_battery_add(struct acpi_device *device)
>>>> mutex_init(&battery->sysfs_lock);
>>>> if (acpi_has_method(battery->device->handle, "_BIX"))
>>>> set_bit(ACPI_BATTERY_XINFO_PRESENT, &battery->flags);
>>>> - result = acpi_battery_update(battery, false);
>>>> +
>>>> + /*
>>>> + * Some machines'(E,G Lenovo Z480) ECs are not stable
>>>> + * during boot up and this causes battery driver fails to be
>>>> + * probed due to failure of getting battery information
>>>> + * from EC sometimes. After several retries, the operation
>>>> + * may work. So add retry code here and 20ms sleep between
>>>> + * every retries.
>>>> + */
>>>> + while ((result = acpi_battery_update(battery, false)) && retry--)
>>>> + msleep(20);
>>>> if (result)
>>>> goto fail;
>>>
>>> Why not to write this as
>>>
>>> for (;;) {
>>> result = acpi_battery_update(battery, false);
>>> if (!result)
>>> break;
>>> else if (!--retry)
>>> goto fail;
>>>
>>> msleep(20);
>>> }
>>>
>>
>> I suggested a similar for loop earlier, I think it's cleaner.
>
> Precisely. And it would be even more clean to introduce
>
> static bool acpi_battery_update_retry(struct acpi_battery *battery)
> {
> int retry, ret;
>
> for (retry = 5; retry; retry--) {
> ret = acpi_battery_update(battery, false);
> if (!ret)
> break;
>
> msleep(20);
> }
> return ret;
> }
>
> and use that instead of the open-coded loop.
Ok. I will update patch like this.
>
> Rafael
>
--
Best regards
Tianyu Lan
next prev parent reply other threads:[~2014-06-19 6:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 7:09 [PATCH V2] ACPI/Battery: Retry to get Battery information if failed during probing Lan Tianyu
2014-06-17 7:09 ` Lan Tianyu
2014-06-17 11:35 ` Rafael J. Wysocki
2014-06-18 22:15 ` David Rientjes
2014-06-18 23:00 ` Rafael J. Wysocki
2014-06-19 6:48 ` Lan Tianyu [this message]
2014-06-19 6:48 ` Lan Tianyu
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=53A287A9.7000203@intel.com \
--to=tianyu.lan@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naszar@ya.ru \
--cc=rientjes@google.com \
--cc=rjw@rjwysocki.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.