From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux ACPI <linux-acpi@vger.kernel.org>,
Jonathan Cameron <jonathan.cameron@huawei.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Russell King (Oracle)" <linux@armlinux.org.uk>
Subject: [PATCH v2 0/5] ACPI: scan: Check enabled _STA bit on Bus/Device Checks
Date: Mon, 26 Feb 2024 17:24:57 +0100 [thread overview]
Message-ID: <6021126.lOV4Wx5bFT@kreacher> (raw)
Hi,
This is an update of the patch series at
https://lore.kernel.org/linux-acpi/4562925.LvFx2qVVIh@kreacher/
which mostly only rearranges the code and makes one functional
change in acpi_scan_devie_check().
The original series description is mostly still applicable:
"This series adds _STA enabled bit checking for processors (in all cases)
and for all devices in the Bus Check and Device Check notification handling
paths. It does so without any side-effects on non-processor devices, unlike
https://lore.kernel.org/linux-acpi/E1rVDmP-0027YJ-EW@rmk-PC.armlinux.org.uk/
The first patch fixes an issue with failing Device Check notifications
without a valid reason.
The next two patches together make Bus Check and Device Check notification
handling take the enabled bit into account.
The last patch modifies the processor scan handler to check the enabled bit
it its add callback.
I would appreciate testing this on a system where the enabled bit really
matters."
Thanks!
next reply other threads:[~2024-02-26 16:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 16:24 Rafael J. Wysocki [this message]
2024-02-26 16:35 ` [PATCH v2 1/5] ACPI: scan: Fix device check notification handling Rafael J. Wysocki
2024-02-26 16:36 ` [PATCH v2 2/5] ACPI: scan: Relocate acpi_bus_trim_one() Rafael J. Wysocki
2024-02-26 16:49 ` Rafael J. Wysocki
2024-02-26 16:40 ` [PATCH v2 3/5] ACPI: scan: Make acpi_processor_add() check the device enabled bit Rafael J. Wysocki
2024-02-27 9:28 ` Jonathan Cameron
2024-02-27 11:13 ` Rafael J. Wysocki
2024-02-26 16:45 ` [PATCH v2 4/5] ACPI: scan: Rework Device Check and Bus Check notification handling Rafael J. Wysocki
2024-02-27 9:39 ` Jonathan Cameron
2024-02-26 16:46 ` [PATCH v2 5/5] ACPI: scan: Consolidate " Rafael J. Wysocki
2024-02-27 9:41 ` Jonathan Cameron
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=6021126.lOV4Wx5bFT@kreacher \
--to=rjw@rjwysocki.net \
--cc=jonathan.cameron@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael@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