From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Aseda Aboagye <aaboagye@chromium.org>
Cc: linux-input@vger.kernel.org
Subject: Re: hid-input.c && vendor defined usage pages
Date: Wed, 2 Oct 2024 08:00:59 -0700 [thread overview]
Message-ID: <Zv1gKyTELpTngKIq@google.com> (raw)
In-Reply-To: <ZvNaHt7ePvoUpgy8@google.com>
Hi Aseda,
On Tue, Sep 24, 2024 at 07:32:30PM -0500, Aseda Aboagye wrote:
> Perhaps this is a naive question, but why does `hidinput_configure_usage()` in
> `hid-input.c` configure vendor defined usage pages? In actuality, it seems like
> it's mainly handling some HP specific usage pages. Why aren't those in some
> `hid-hp.c` file that's selected by a kernel config?
It is simply a historic artefact. These usages were mapped way before we
had HID sub-drivers and accompanying infrastructure.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2024-10-02 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 0:32 hid-input.c && vendor defined usage pages Aseda Aboagye
2024-10-02 15:00 ` Dmitry Torokhov [this message]
2024-10-14 22:15 ` Aseda Aboagye
2024-10-15 18:47 ` 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=Zv1gKyTELpTngKIq@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=aaboagye@chromium.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).