From: Hans de Goede <hdegoede@redhat.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-input@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: [PATCH 0/1] Input: soc_button_array - Work around DSDTs which modify the irqflags
Date: Sun, 6 Sep 2020 14:20:15 +0200 [thread overview]
Message-ID: <20200906122016.4628-1-hdegoede@redhat.com> (raw)
Hi Dmitry,
This patch is a bit of a kludge, but the problem it fixes has been
encountered on 2 different models now, so it seems that we really
need a workaround for this.
This patch applies on top of these 2 patches:
"Input: soc_button_array - Add active_low setting to soc_button_info"
"Input: soc_button_array - Add support for INT33D3 tablet-mode switch devices"
Which I have posted multiple times upstream already (they are from May!),
but these have not been getting any attention.
The soc_button_array code really is x86 specific glue code to translate
various incarnations of gpio-keys in ACPI tables to gpio_keys_platform_data.
As such I wonder if it would not be better to move this driver to
drivers/platform/x86?
I seem to be doing most if not all of the recent work on soc_button_array,
and soon I will be a co-maintainer of drivers/platform/x86. So having it
there and adding me in MAINTAINERS as maintaining it seems to be best?
If you want I can do a patch moving soc_button_array to drivers/platform/x86
and then add the other 3 patches on top and then we can merge all of this
through drivers/platform/x86?
Regards,
Hans
next reply other threads:[~2020-09-06 12:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-06 12:20 Hans de Goede [this message]
2020-09-06 12:20 ` [PATCH] Input: soc_button_array - Work around DSDTs which modify the irqflags Hans de Goede
2020-09-14 6:09 ` Dmitry Torokhov
2020-09-14 6:12 ` [PATCH 0/1] " Dmitry Torokhov
2020-09-14 7:45 ` Hans de Goede
2020-09-14 8:00 ` Andy Shevchenko
2020-09-14 13:52 ` Hans de Goede
2020-09-14 14:08 ` Hans de Goede
2020-09-14 18:05 ` Dmitry Torokhov
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=20200906122016.4628-1-hdegoede@redhat.com \
--to=hdegoede@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=mika.westerberg@linux.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 NNTP newsgroup(s).