From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Rahul Pon <theflyingrahul@gmail.com>
Cc: Linus Walleij <linusw@kernel.org>,
Andy Shevchenko <andy@kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Mika Westerberg <westeri@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
linux-acpi@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI: GED: Support GpioInt event resources
Date: Thu, 1 Oct 2026 21:15:18 +0300 [thread overview]
Message-ID: <ar6jNo7-Wgx2ZLty@ashevche-desk.local> (raw)
In-Reply-To: <20261001041856.1984-1-theflyingrahul@gmail.com>
On Thu, Oct 01, 2026 at 09:48:56AM +0530, Rahul Pon wrote:
> On Thu, Oct 1, 2026 at 1:52 AM Linus Walleij <linusw@kernel.org> wrote:
> > I don't understand the patch at all, but I understand that Andy or Mika must
> > review it otherwise it's not going anywhere, so looping them in.
>
> Thanks, Linus.
>
> Andy, Mika: some context that should have been in the commit message.
>
> ACPI 6.6 section 5.6.9.2 says a GED _CRS contains only Interrupt
> resource descriptors, so this firmware is outside the spec. It is still
> the only source of lid events here: LIGE's _CRS is a single GpioInt on
> the GPIO controller (pin 960), and the controller's _AEI lists one
> other, unrelated pin. ECGE is the same, with pin 768. On Windows, the
> in-box ACPI device driver (acpidev.inf) binds both GED devices, and the
> lid works there.
>
> For _EVT, section 5.6.9.3 passes the GSI number, which a GpioInt does
> not have. The patch passes the pin number from the GpioInt descriptor,
> as section 5.6.5.3 does for _EVT under _AEI. Both _EVT methods on this
> laptop ignore Arg0.
>
> If the approach is acceptable, v2 will state the spec deviation in the
> commit message.
Is vendor of the firmware / platform being informed? Do they accept their
mistake? Are they going to fix their crap?
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-10-01 18:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 11:15 Rahul Pon
2026-09-30 20:22 ` Linus Walleij
2026-10-01 4:04 ` Mika Westerberg
2026-10-01 4:27 ` Rahul Pon
2026-10-01 4:18 ` Rahul Pon
2026-10-01 18:15 ` Andy Shevchenko [this message]
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=ar6jNo7-Wgx2ZLty@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=brgl@kernel.org \
--cc=lenb@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael@kernel.org \
--cc=theflyingrahul@gmail.com \
--cc=westeri@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®