From: Michael Walle <mwalle@kernel.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>, Lee Jones <lee@kernel.org>
Cc: jcormier@criticallink.com, Job Sava <jsava@criticallink.com>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
Michael Walle <mwalle@kernel.org>
Subject: [PATCH v2 0/3] mfd: tps6594: add power button and power-off
Date: Tue, 26 Aug 2025 15:46:28 +0200 [thread overview]
Message-ID: <20250826134631.1499936-1-mwalle@kernel.org> (raw)
I took over the series from [1] since the original developer was an
intern and is no longer with their former company.
Changelog is in the individual patches. But the most prominent
change is that the pin mux config is now read from the chip itself
instead of having a DT property.
[1] https://lore.kernel.org/all/20250520-linux-stable-tps6594-pwrbutton-v1-0-0cc5c6e0415c@criticallink.com/
Job Sava (1):
input: tps6594-pwrbutton: Add power button functionality
Michael Walle (2):
mfd: tps6594: add power button functionality
mfd: tps6594: Add board power-off support
drivers/input/misc/Kconfig | 10 ++
drivers/input/misc/Makefile | 1 +
drivers/input/misc/tps6594-pwrbutton.c | 126 +++++++++++++++++++++++++
drivers/mfd/tps6594-core.c | 58 +++++++++++-
4 files changed, 193 insertions(+), 2 deletions(-)
create mode 100644 drivers/input/misc/tps6594-pwrbutton.c
--
2.39.5
next reply other threads:[~2025-08-26 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 13:46 Michael Walle [this message]
2025-08-26 13:46 ` [PATCH v2 1/3] input: tps6594-pwrbutton: Add power button functionality Michael Walle
2025-08-26 13:46 ` [PATCH v2 2/3] mfd: tps6594: add " Michael Walle
2025-08-26 13:46 ` [PATCH v2 3/3] mfd: tps6594: Add board power-off support Michael Walle
2025-09-03 10:45 ` [PATCH v2 0/3] mfd: tps6594: add power button and power-off Lee Jones
2025-09-03 10:46 ` Lee Jones
2025-09-03 11:32 ` [GIT PULL] Immutable branch between MFD and Input due for the v6.18 merge window Lee Jones
2025-09-11 15:14 ` [GIT PULL v2] " Lee Jones
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=20250826134631.1499936-1-mwalle@kernel.org \
--to=mwalle@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jcormier@criticallink.com \
--cc=jsava@criticallink.com \
--cc=lee@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®