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] [day] [month] [year] [list]
Message-Id: <174579421680.295785.5362050281749814568.b4-ty@collabora.com>
Date: Mon, 28 Apr 2025 00:50:16 +0200
From: Sebastian Reichel <sebastian.reichel@...labora.com>
To: Pali Rohár <pali@...nel.org>, 
 Sebastian Reichel <sre@...nel.org>, Jerry Lv <Jerry.Lv@...s.com>
Cc: kernel@...s.com, linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4] power: supply: bq27xxx: Retrieve again when busy


On Tue, 15 Apr 2025 11:40:47 +0800, Jerry Lv wrote:
> Multiple applications may access the battery gauge at the same time, so
> the gauge may be busy and EBUSY will be returned. The driver will set a
> flag to record the EBUSY state, and this flag will be kept until the next
> periodic update. When this flag is set, bq27xxx_battery_get_property()
> will just return ENODEV until the flag is updated.
> 
> Even if the gauge was busy during the last accessing attempt, returning
> ENODEV is not ideal, and can cause confusion in the applications layer.
> 
> [...]

Applied, thanks!

[1/1] power: supply: bq27xxx: Retrieve again when busy
      commit: f16d9fb6cf03fdbdefa41a8b32ba1e57afb7ae3d

Best regards,
-- 
Sebastian Reichel <sebastian.reichel@...labora.com>


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ