linux-kernel - Re: [PATCH] ACPI/Battery: Accelerate battery resume callback

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <536C873D.8030405@intel.com>
Date:	Fri, 09 May 2014 15:43:57 +0800
From:	Lan Tianyu <tianyu.lan@...el.com>
To:	Pavel Machek <pavel@....cz>
CC:	rjw@...ysocki.net, lenb@...nel.org, linux-acpi@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ACPI/Battery: Accelerate battery resume callback

On 2014年05月09日 15:38, Pavel Machek wrote:
> Hi!
> 
>> Most time of battery resume callback is spent on executing AML code
>> _BTP, _BIF and _BIF to get battery info, status and set alarm. These
>> AML methods may access EC operation regions several times and consumes
>> time.
>>
>> These operations are not necessary during devices resume and can run
>> during POST_SUSPEND/HIBERNATION event when all processes are thawed.
> 
> Does it mean that userspace will see pre-hibernation battery level for a while 
> after resume?

Hi Pavel:
	Thanks for your review. No, when user access the battery sysfs
interface, driver will read battery info and return new data.

> 
> 									Pavel
> 


-- 
Best regards
Tianyu Lan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/