From: Armin Wolf <W_Armin@gmx.de>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>, hdegoede@redhat.com
Cc: sre@kernel.org, platform-driver-x86@vger.kernel.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/4] power: supply: core: Add additional health status values
Date: Mon, 12 May 2025 00:33:48 +0200 [thread overview]
Message-ID: <e11b6c57-675b-4c81-bfb6-5133c8c245e7@gmx.de> (raw)
In-Reply-To: <174700275600.13063.9398321342899509983.b4-ty@linux.intel.com>
Am 12.05.25 um 00:32 schrieb Ilpo Järvinen:
> On Tue, 29 Apr 2025 02:36:03 +0200, Armin Wolf wrote:
>
>> Some batteries can signal when an internal fuse was blown. In such a
>> case POWER_SUPPLY_HEALTH_DEAD is too vague for userspace applications
>> to perform meaningful diagnostics.
>>
>> Additionally some batteries can also signal when some of their
>> internal cells are imbalanced. In such a case returning
>> POWER_SUPPLY_HEALTH_UNSPEC_FAILURE is again too vague for userspace
>> applications to perform meaningful diagnostics.
>>
>> [...]
>
> Thank you for your contribution, it has been applied to my local
> review-ilpo-next branch. Note it will show up in the public
> platform-drivers-x86/review-ilpo-next branch only once I've pushed my
> local branch there, which might take a while.
Thank you :)
> The list of commits applied:
> [1/4] power: supply: core: Add additional health status values
> commit: e6b07a34038716e010d9fd1ac74c1d84a501f369
> [2/4] platform/x86: dell-ddv: Implement the battery matching algorithm
> commit: 52e59cf1332dc4da5aecaa64c20f4a9f902e3186
> [3/4] platform/x86: dell-ddv: Expose the battery manufacture date to userspace
> commit: 366a50722c7071120a494aaf91c9193922e3d8f6
> [4/4] platform/x86: dell-ddv: Expose the battery health to userspace
> commit: d5251eef71bab8bd0b9ea3fe0005ad3d2553c3bb
>
> --
> i.
>
prev parent reply other threads:[~2025-05-11 22:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 0:36 [PATCH v2 1/4] power: supply: core: Add additional health status values Armin Wolf
2025-04-29 0:36 ` [PATCH v2 2/4] platform/x86: dell-ddv: Implement the battery matching algorithm Armin Wolf
2025-04-29 0:36 ` [PATCH v2 3/4] platform/x86: dell-ddv: Expose the battery manufacture date to userspace Armin Wolf
2025-04-29 0:36 ` [PATCH v2 4/4] platform/x86: dell-ddv: Expose the battery health " Armin Wolf
2025-04-29 23:44 ` [PATCH v2 1/4] power: supply: core: Add additional health status values Sebastian Reichel
2025-05-05 12:22 ` Ilpo Järvinen
2025-05-09 10:09 ` Ilpo Järvinen
2025-05-11 22:22 ` Sebastian Reichel
2025-05-11 22:32 ` Ilpo Järvinen
2025-05-11 22:33 ` Armin Wolf [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=e11b6c57-675b-4c81-bfb6-5133c8c245e7@gmx.de \
--to=w_armin@gmx.de \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sre@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