mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux ACPI <linux-acpi@vger.kernel.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Armin Wolf <w_armin@gmx.de>
Subject: [PATCH v1 0/3] ACPI: EC: Avoid evaluating _REG for non-functional operation regions
Date: Mon, 12 Aug 2024 15:06:25 +0200	[thread overview]
Message-ID: <22385894.EfDdHjke4D@rjwysocki.net> (raw)

Hi Everyone,

The purpose of this series is to address issues reported here:

https://lore.kernel.org/linux-acpi/1f76b7e2-1928-4598-8037-28a1785c2d13@redhat.com/

and related to evaluating _REG for EC operation regions that are not
expected to be used (for example, because they reside in the scopes of
ACPI device objects whose _STA returns 0).

The first patch reverts commit 0e6b6dedf168 ("Revert "ACPI: EC: Evaluate orphan
_REG under EC device") that will not be necessary after making the changes in
the last patch.  The second patch modifies acpi_execute_reg_methods() to take
an additional "depth" argument that will be needed doing forward.

The last patch moves the _REG evaluation for EC operation regions beyond the
EC device scope to acpi_bus_attach() so it is only evaluated if the device
object holding the EC operation region is present.

Thanks!




             reply	other threads:[~2024-08-12 13:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-12 13:06 Rafael J. Wysocki [this message]
2024-08-12 13:08 ` [PATCH v1 1/3] Revert "ACPI: EC: Evaluate orphan _REG under EC device" Rafael J. Wysocki
2024-08-12 13:11 ` [PATCH v1 2/3] ACPICA: Add a depth argument to acpi_execute_reg_methods() Rafael J. Wysocki
2024-08-12 13:16 ` [PATCH v1 3/3] ACPI: EC: Evaluate _REG outside the EC scope more carefully 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=22385894.EfDdHjke4D@rjwysocki.net \
    --to=rjw@rjwysocki.net \
    --cc=hdegoede@redhat.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=w_armin@gmx.de \
    /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®