From: Hans de Goede <hdegoede@redhat.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Bastien Nocera <hadess@hadess.net>, linux-input@vger.kernel.org
Subject: Re: [PATCH] Input: goodix - Workaround Cherry Trail devices with a bogus ACPI Interrupt() resource
Date: Tue, 1 Mar 2022 11:47:44 +0100 [thread overview]
Message-ID: <212c1e2c-81f2-f92e-a5ad-ec84218e3c3f@redhat.com> (raw)
In-Reply-To: <Yh3Fh5PLPu91CKqn@google.com>
Hi Dmitry,
On 3/1/22 08:04, Dmitry Torokhov wrote:
> On Mon, Feb 28, 2022 at 12:16:13PM +0100, Hans de Goede wrote:
>> ACPI/x86 devices with a Cherry Trail SoC should have a GpioInt + a regular
>> GPIO ACPI resource in their ACPI tables.
>>
>> Some CHT devices have a bug, where the also is bogus Interrupt resource
>> (likely copied from a previous Bay Trail based generation of the device).
>>
>> The i2c-core-acpi code will assign the bogus, non-working, Interrupt
>> resource to client->irq. Add a workaround to fix this up.
>>
>> BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=2043960
>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>
> Applied (for 5.17), thank you.
Thank you!
Unrelated question (now that I have your attention) may I have your
Acked-by for merging the (small) drivers/input/misc/soc_button_array.c
of this series:
https://lore.kernel.org/linux-input/20220224110241.9613-1-hdegoede@redhat.com/
see:
https://lore.kernel.org/linux-input/20220224110241.9613-2-hdegoede@redhat.com/
Through the drivers/platform/x86 tree ?
(so that we can keep the series together)
Regards,
Hans
prev parent reply other threads:[~2022-03-01 10:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 11:16 [PATCH] Input: goodix - Workaround Cherry Trail devices with a bogus ACPI Interrupt() resource Hans de Goede
2022-03-01 7:04 ` Dmitry Torokhov
2022-03-01 10:47 ` Hans de Goede [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=212c1e2c-81f2-f92e-a5ad-ec84218e3c3f@redhat.com \
--to=hdegoede@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hadess@hadess.net \
--cc=linux-input@vger.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;
as well as URLs for NNTP newsgroup(s).