* hid-input.c && vendor defined usage pages
@ 2024-09-25 0:32 Aseda Aboagye
2024-10-02 15:00 ` Dmitry Torokhov
0 siblings, 1 reply; 4+ messages in thread
From: Aseda Aboagye @ 2024-09-25 0:32 UTC (permalink / raw)
To: linux-input
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?
Curiously,
--
Aseda Aboagye
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: hid-input.c && vendor defined usage pages
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
0 siblings, 1 reply; 4+ messages in thread
From: Dmitry Torokhov @ 2024-10-02 15:00 UTC (permalink / raw)
To: Aseda Aboagye; +Cc: linux-input
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: hid-input.c && vendor defined usage pages
2024-10-02 15:00 ` Dmitry Torokhov
@ 2024-10-14 22:15 ` Aseda Aboagye
2024-10-15 18:47 ` Dmitry Torokhov
0 siblings, 1 reply; 4+ messages in thread
From: Aseda Aboagye @ 2024-10-14 22:15 UTC (permalink / raw)
To: Dmitry Torokhov; +Cc: linux-input
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?
Thanks,
--
Aseda Aboagye
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: hid-input.c && vendor defined usage pages
2024-10-14 22:15 ` Aseda Aboagye
@ 2024-10-15 18:47 ` Dmitry Torokhov
0 siblings, 0 replies; 4+ messages in thread
From: Dmitry Torokhov @ 2024-10-15 18:47 UTC (permalink / raw)
To: Aseda Aboagye; +Cc: linux-input
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2024-10-15 18:47 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).