From: Waqar Hameed <waqar.hameed@axis.com>
To: Sebastian Reichel <sre@kernel.org>
Cc: <kernel@axis.com>, <linux-pm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH 0/4] power: supply: Add support for liquid detection
Date: Wed, 28 Oct 2026 22:56:13 +0100 [thread overview]
Message-ID: <cover.1793223841.git.waqar.hameed@axis.com> (raw)
During discussions of the development of a new driver [1], it was
concluded that a new `sysfs` ABI for reporting and controlling liquid
detection is wanted. This patchset introduces this.
Since there are currently not many devices with support for this. ABI
for setting/getting detection threshold values has been left out (as
discussed in [1]). Hopefully when more devices are supported, a good
common way to specify this will be designed.
[1] https://lore.kernel.org/lkml/cover.1772201049.git.waqar.hameed@axis.com/
Waqar Hameed (4):
power: supply: Add sysfs entry for liquid detection control
power: supply: Add liquid detection to health property enum
power: supply: bq25630: Add macro define for IRQ cycle time
power: supply: bq25630: Add support for liquid detection
Documentation/ABI/testing/sysfs-class-power | 22 ++-
drivers/power/supply/bq25630_charger.c | 163 +++++++++++++++++++-
drivers/power/supply/power_supply_sysfs.c | 9 ++
include/linux/power_supply.h | 9 ++
4 files changed, 199 insertions(+), 4 deletions(-)
base-commit: 151a134a4e6ec66f69db8750c66006f5207f7a9d
--
2.43.0
next reply other threads:[~2026-10-28 21:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 21:56 Waqar Hameed [this message]
2026-10-28 21:56 ` [PATCH 2/4] power: supply: Add liquid detection to health property enum Waqar Hameed
2026-10-28 21:56 ` [PATCH 1/4] power: supply: Add sysfs entry for liquid detection control Waqar Hameed
2026-10-28 21:56 ` [PATCH 3/4] power: supply: bq25630: Add macro define for IRQ cycle time Waqar Hameed
2026-10-28 21:56 ` [PATCH 4/4] power: supply: bq25630: Add support for liquid detection Waqar Hameed
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=cover.1793223841.git.waqar.hameed@axis.com \
--to=waqar.hameed@axis.com \
--cc=kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@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
all inboxes | Powered by JetHome®