[<prev] [next>] [day] [month] [year] [list]
Message-ID: <YTcBOskPYjbv4q61@google.com>
Date: Mon, 6 Sep 2021 23:05:46 -0700
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: "Tobita, Tatsunosuke" <tatsunosuke.tobita@...om.com>
Cc: Alistair Francis <alistair@...stair23.me>,
"Cheng, Ping" <Ping.Cheng@...om.com>,
"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
"linux-imx@....com" <linux-imx@....com>,
"kernel@...gutronix.de" <kernel@...gutronix.de>,
"pinglinux@...il.com" <pinglinux@...il.com>,
"junkpainting@...il.com" <junkpainting@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"alistair23@...il.com" <alistair23@...il.com>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH v10 05/12] Input: wacom_i2c - Read the descriptor values
Hi Tatsunosuke,
On Thu, Sep 02, 2021 at 07:33:49AM +0000, Tobita, Tatsunosuke wrote:
> Hi Dmitry,
>
> Yes, our firmware supports HID over I2C. However, some of our
> customers often do not want to use HID to handle our hardware; even
> they don't install the generic HID driver neither. In such case, we
> need to distinguish what generation of our device customer's has. And
> to do so, we check I2C HID descriptor even though the driver is not
> working with HID driver components, but this one. That is why I2C HID
> descriptor is used there. It is called, but the situation with this
> driver is not supposed to work as a HID device.
I would like to understand better why the customers do not want to use
HID. There needs to be a _very_ strong reason to essentially duplicate
HID layer in a vendor driver and I inclined to say that such customers
would need to patch their kernels themselves.
Thanks.
--
Dmitry
Powered by blists - more mailing lists