From: Armin Wolf <W_Armin@gmx.de>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Len Brown <lenb@kernel.org>,
Robert Moore <robert.moore@intel.com>
Cc: linux-acpi@vger.kernel.org, acpica-devel@lists.linux.dev
Subject: Re: Missing default handler for the EmbeddedControl OpRegion
Date: Sun, 5 May 2024 19:03:22 +0200 [thread overview]
Message-ID: <a2be7595-53c1-42fb-8633-2299ab20de64@gmx.de> (raw)
In-Reply-To: <Zi+0whTvDbAdveHq@kuha.fi.intel.com>
Am 29.04.24 um 16:54 schrieb Heikki Krogerus:
> Hi,
>
> There's a bug that is caused by an EmbeddedControl OpRegion which is
> declared inside the scope of a specific USB Type-C device (PNP0CA0):
> https://bugzilla.kernel.org/show_bug.cgi?id=218789
>
> It looks like that's not the only case where that OpRegion ID is used
> outside of the EC device scope. There is at least one driver in Linux
> Kernel (drivers/platform/x86/wmi.c) that already has a custom handler
> for the EmbeddedControl OpRegion, and based on a quick search, the
> problem "Region EmbeddedControl (ID=3) has no handler" has happened
> with some other devices too.
>
>
> Br,
>
Hi,
i support your proposal, but i think we first have to figure out how Windows
handles such cases. Those devices are build for and tested with Windows only,
so Windows seems to specify some behavior which allows for this.
I will try to contact Microsoft and ask them how the Windows Kernel handles
this OpRegions.
Thanks,
Armin Wolf
next prev parent reply other threads:[~2024-05-05 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 14:54 Missing default handler for the EmbeddedControl OpRegion Heikki Krogerus
2024-05-05 17:03 ` Armin Wolf [this message]
2024-05-06 17:45 ` Rafael J. Wysocki
2024-05-08 12:20 ` Heikki Krogerus
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=a2be7595-53c1-42fb-8633-2299ab20de64@gmx.de \
--to=w_armin@gmx.de \
--cc=acpica-devel@lists.linux.dev \
--cc=heikki.krogerus@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=robert.moore@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).