From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jeffrey Hugo <jeffrey.l.hugo@gmail.com>
Cc: benjamin.tissoires@redhat.com, jikos@kernel.org,
bjorn.andersson@linaro.org, lee.jones@linaro.org,
robh+dt@kernel.org, mark.rutland@arm.com, agross@kernel.org,
david.brown@linaro.org, hdegoede@redhat.com,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/3] HID: quirks: Refactor ELAN 400 and 401 handling
Date: Tue, 11 Jun 2019 17:35:07 -0700 [thread overview]
Message-ID: <20190612003507.GG143729@dtor-ws> (raw)
In-Reply-To: <20190606161322.47192-1-jeffrey.l.hugo@gmail.com>
On Thu, Jun 06, 2019 at 09:13:22AM -0700, Jeffrey Hugo wrote:
> There needs to be coordination between hid-quirks and the elan_i2c driver
> about which devices are handled by what drivers. Currently, both use
> whitelists, which results in valid devices being unhandled by default,
> when they should not be rejected by hid-quirks. This is quickly becoming
> an issue.
>
> Since elan_i2c has a maintained whitelist of what devices it will handle,
> use that to implement a blacklist in hid-quirks so that only the devices
> that need to be handled by elan_i2c get rejected by hid-quirks, and
> everything else is handled by default. The downside is the whitelist and
> blacklist need to be kept in sync.
>
> Suggested-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
> Signed-off-by: Jeffrey Hugo <jeffrey.l.hugo@gmail.com>
> ---
> drivers/hid/hid-quirks.c | 78 ++++++++++++++++++++++++++++++++++------
> 1 file changed, 67 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/hid/hid-quirks.c b/drivers/hid/hid-quirks.c
> index e5ca6fe2ca57..edebd0700e3d 100644
> --- a/drivers/hid/hid-quirks.c
> +++ b/drivers/hid/hid-quirks.c
> @@ -912,8 +912,66 @@ static const struct hid_device_id hid_mouse_ignore_list[] = {
> { }
> };
>
> +/*
> + * List of device names that elan_i2c is handling and HID should ignore. Must
> + * be kept in sync with elan_i2c
> + */
> +static const char *hid_elan_i2c_ignore[] = {
If this is a copy of elan whitelist, then, if we do not want to bother
with sharing it in object form (as a elan-i2c-ids module), can we at
least move it into include/linux/input/elan-i2c-ids.h and consume from
hid-quirks.c?
Thanks.
--
Dmitry
next prev parent reply other threads:[~2019-06-12 0:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 16:10 [PATCH v5 0/3] Basic DT support for Lenovo Miix 630 Jeffrey Hugo
2019-06-06 16:10 ` Jeffrey Hugo
2019-06-06 16:13 ` [PATCH v5 1/3] Input: elan_i2c: Add comment about link between elan_i2c and hid-quirks Jeffrey Hugo
2019-06-06 16:13 ` [PATCH v5 2/3] HID: quirks: Refactor ELAN 400 and 401 handling Jeffrey Hugo
2019-06-12 0:35 ` Dmitry Torokhov [this message]
2019-06-12 14:29 ` Jeffrey Hugo
2019-06-12 14:37 ` Lee Jones
2019-06-12 14:48 ` Jeffrey Hugo
2019-06-12 14:45 ` Jiri Kosina
2019-06-12 15:13 ` Dmitry Torokhov
2019-06-12 15:21 ` Benjamin Tissoires
2019-06-12 15:38 ` Jeffrey Hugo
2019-06-06 16:13 ` [PATCH v5 3/3] arm64: dts: qcom: Add Lenovo Miix 630 Jeffrey Hugo
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=20190612003507.GG143729@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=agross@kernel.org \
--cc=benjamin.tissoires@redhat.com \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=hdegoede@redhat.com \
--cc=jeffrey.l.hugo@gmail.com \
--cc=jikos@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.