From: Marco Morandini <marco.morandini@polimi.it>
To: Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
linux-input@vger.kernel.org
Subject: [PATCH RFC 0/1] HID: allow specifying quirks params for hid-core
Date: Thu, 15 Jun 2023 23:00:07 +0200 [thread overview]
Message-ID: <f702b1fb-a31d-0cd0-9f42-dd8d1a0573b5@polimi.it> (raw)
Right now, only usbhid accepts parameters
specifying quirks.
Following Benjamin's explanations,
this patch allows specifying them for hid
in the form hid.quirks=BUS:vendorID:productID:quirks
I don't know if this is a good idea or not, thus the RFC.
If it was for me, I'd get rid of the usbhid parameters
and of the duplicated hid_quirks_init,
forcing everyone to specify the bus,
but I fear this could be a regression for user space.
Marco Morandini (1)
HID: allow specifying quirks params for hid-core
drivers/hid/hid-core.c | 13 +++++++++++++
drivers/hid/hid-quirks.c | 33 +++++++++++++++++++++++++++++++++
include/linux/hid.h | 1 +
3 files changed, 47 insertions(+)
--
2.41.0
reply other threads:[~2023-06-15 21:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=f702b1fb-a31d-0cd0-9f42-dd8d1a0573b5@polimi.it \
--to=marco.morandini@polimi.it \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--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).