From: Hans de Goede <hdegoede@redhat.com>
To: Julian Sax <jsbc@gmx.de>, linux-input@vger.kernel.org
Cc: Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] HID: i2c-hid: add Vero K147 to descriptor override
Date: Fri, 27 Nov 2020 10:16:16 +0100 [thread overview]
Message-ID: <fa55d191-aa27-cb12-a0d7-3b3342fb3366@redhat.com> (raw)
In-Reply-To: <20201126175158.1183879-1-jsbc@gmx.de>
Hi,
On 11/26/20 6:51 PM, Julian Sax wrote:
> This device uses the SIPODEV SP1064 touchpad, which does not
> supply descriptors, so it has to be added to the override list.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Julian Sax <jsbc@gmx.de>
Thanks, patch looks good to me:
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
Regards,
Hans
> ---
> drivers/hid/i2c-hid/i2c-hid-dmi-quirks.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/hid/i2c-hid/i2c-hid-dmi-quirks.c b/drivers/hid/i2c-hid/i2c-hid-dmi-quirks.c
> index 35f3bfc3e6f5..8e0f67455c09 100644
> --- a/drivers/hid/i2c-hid/i2c-hid-dmi-quirks.c
> +++ b/drivers/hid/i2c-hid/i2c-hid-dmi-quirks.c
> @@ -405,6 +405,14 @@ static const struct dmi_system_id i2c_hid_dmi_desc_override_table[] = {
> },
> .driver_data = (void *)&sipodev_desc
> },
> + {
> + .ident = "Vero K147",
> + .matches = {
> + DMI_EXACT_MATCH(DMI_SYS_VENDOR, "VERO"),
> + DMI_EXACT_MATCH(DMI_PRODUCT_NAME, "K147"),
> + },
> + .driver_data = (void *)&sipodev_desc
> + },
> { } /* Terminate list */
> };
>
> --
> 2.29.2
>
next prev parent reply other threads:[~2020-11-27 9:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 17:51 [PATCH] HID: i2c-hid: add Vero K147 to descriptor override Julian Sax
2020-11-27 9:16 ` Hans de Goede [this message]
2020-11-27 15:18 ` Jiri Kosina
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=fa55d191-aa27-cb12-a0d7-3b3342fb3366@redhat.com \
--to=hdegoede@redhat.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=jsbc@gmx.de \
--cc=linux-input@vger.kernel.org \
--cc=stable@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).