From: Lan Tianyu <tianyu.lan@intel.com>
To: David Rientjes <rientjes@google.com>
Cc: rjw@rjwysocki.net, lenb@kernel.org, naszar@ya.ru,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI/Battery: Retry to get Battery information if failed during probing
Date: Tue, 17 Jun 2014 09:27:54 +0800 [thread overview]
Message-ID: <539F999A.8070902@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1406161827320.21018@chino.kir.corp.google.com>
On 2014年06月17日 09:27, David Rientjes wrote:
> On Mon, 16 Jun 2014, Lan Tianyu wrote:
>
>>>> How about this?
>>>>
>>>> - result = acpi_battery_update(battery, false);
>>>> - if (result)
>>>> +
>>>> + /*
>>>> + * 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 (acpi_battery_update(battery, false) && retry--)
>>>> + msleep(20);
>>>> + if (!retry) {
>>>> + result = -ENODEV;
>>>> goto fail;
>>>> + }
>>>> +
>>>
>>> I think you want --retry and not retry--.
>>
>> My original purpose is to retry 5 times after the first try fails.
>> If use "--retry" here, it just retries 4 times.
>>
>>> Otherwise it's possible for the
>>> final call to acpi_battery_update() to succeed and now it's returning
>>> -ENODEV.
>>>
>>
>> Yes, it maybe and I will change code like the following.
>>
>> while ((result = acpi_battery_update(battery, false)) && retry--)
>> msleep(20);
>> if (result)
>> goto fail;
>>
>
> Looks good.
>
Great. Thanks for review. :)
--
Best regards
Tianyu Lan
prev parent reply other threads:[~2014-06-17 1:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 6:02 [PATCH] ACPI/Battery: Retry to get Battery information if failed during probing Lan Tianyu
2014-06-12 6:55 ` David Rientjes
2014-06-12 7:19 ` Lan Tianyu
2014-06-12 7:26 ` David Rientjes
2014-06-12 8:14 ` Lan Tianyu
2014-06-12 21:17 ` David Rientjes
2014-06-13 2:25 ` Lan Tianyu
2014-06-13 21:46 ` David Rientjes
2014-06-16 2:12 ` Lan Tianyu
2014-06-16 2:35 ` Zheng, Lv
2014-06-16 2:43 ` Lan Tianyu
2014-06-17 1:27 ` David Rientjes
2014-06-17 1:27 ` Lan Tianyu [this message]
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=539F999A.8070902@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox