linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Tue, 15 Oct 2024 11:47:25 -0700	[thread overview]
Message-ID: <Zw64vVlkV6wyOUd-@google.com> (raw)
In-Reply-To: <Zw2X50VzyzF4AyBT@google.com>

On Mon, Oct 14, 2024 at 10:15:03PM +0000, Aseda Aboagye wrote:
> On Wed, Oct 02, 2024 at 08:00:59AM -0700, Dmitry Torokhov wrote:
> > 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.
> 
> Do you reckon that we're stuck with this behaviour now since migrating them
> out, will likely break users who don't have the appropriate sub-drivers
> selected in their kernel config?

We typically do not commit to keeping forward or backward compatibility
for the kernel config options, it is distribution's task to configure
the kernel properly, so I think it can be changed if desired.

Thanks.

-- 
Dmitry

      reply	other threads:[~2024-10-15 18:47 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
2024-10-14 22:15   ` Aseda Aboagye
2024-10-15 18:47     ` Dmitry Torokhov [this message]

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=Zw64vVlkV6wyOUd-@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).