From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux ACPI <linux-acpi@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Michal Wilczynski <michal.wilczynski@intel.com>
Subject: [RFT][PATCH v1 0/4] ACPI: Install notify or event handlers in ACPI button drivers
Date: Sun, 04 Jun 2023 17:17:22 +0200 [thread overview]
Message-ID: <1847933.atdPhlSkOF@kreacher> (raw)
Hi Folks,
This series reworks the two ACPI button drivers to install notify or fixed
event handlers (depending on the device type) by themselves, so the core
code need not take the "fixed event handler for a button driver" case in
the general driver notify handler installer.
As a bonus, it separates the notify handler in the "generic" button driver
into a lid notify handler and a proper button notify handler.
It modifies also the core to drop the "fixed event handler for a button driver"
case from there (last patch).
It works for me, but I would appreciate as much testing of this as possible
especially on old hardware.
Obviously, it replaces
https://lore.kernel.org/linux-acpi/4500594.LvFx2qVVIh@kreacher/T/#m064d4130b57cbcb0ece1bb415fae1465ebc20f42
and its followers to some extent, but I think that it's better to deal with the
special case first and then take care of the rest.
Thanks!
next reply other threads:[~2023-06-04 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 15:17 Rafael J. Wysocki [this message]
2023-06-04 15:19 ` [RFT][PATCH v1 1/4] ACPI: button: Eliminate the driver notify callback Rafael J. Wysocki
2023-06-09 17:44 ` Wilczynski, Michal
2023-06-04 15:20 ` [RFT][PATCH v1 2/4] ACPI: button: Use different notify handlers for lid and buttons Rafael J. Wysocki
2023-06-04 15:22 ` [RFT][PATCH v1 3/4] ACPI: tiny-power-button: Eliminate the driver notify callback Rafael J. Wysocki
2023-06-04 15:23 ` [RFT][PATCH v1 4/4] ACPI: bus: Simplify installation and removal of " Rafael J. Wysocki
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=1847933.atdPhlSkOF@kreacher \
--to=rjw@rjwysocki.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.wilczynski@intel.com \
/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