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,
stable@vger.kernel.org
Subject: Re: [PATCH] ACPI/Battery: Retry to get Battery information if failed during probing
Date: Fri, 13 Jun 2014 10:25:00 +0800 [thread overview]
Message-ID: <539A60FC.1050301@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1406121415150.8305@chino.kir.corp.google.com>
On 2014年06月13日 05:17, David Rientjes wrote:
> On Thu, 12 Jun 2014, Lan Tianyu wrote:
>
>> The retry time is set by randomly and not accurate because don't know
>> when EC will work normally. Set the retry time to 5 just in order to
>> make sure battery driver probing sucessfully every time,
>>
>
> Ok, I was hoping to avoid the excessive wait if it will never actually
> succeed
Ok. The battery driver has used async init and so this will not affect
the speed of boot up.
> but I assume there's some evidence that it can succeed after 40ms,
> 60ms, etc. Please consider the following instead:
>
> for (i = 0; i < 5; i++) {
> /* Comment on why we need a delay in between retries */
> if (i)
> msleep(20);
> result = acpi_battery_update(battery, false);
> if (!result)
> break;
> }
>
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;
+ }
+
--
Best regards
Tianyu Lan
next prev parent reply other threads:[~2014-06-13 2:25 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 [this message]
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
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=539A60FC.1050301@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 \
--cc=stable@vger.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