Re: [PATCH v8 1/5] Input: elan_i2c: Export the device id whitelist

2019-06-30 Thread Dmitry Torokhov
On Thu, Jun 27, 2019 at 04:29:29PM +0200, Benjamin Tissoires wrote: > On Thu, Jun 27, 2019 at 4:02 PM Jeffrey Hugo wrote: > > > > On Sun, Jun 23, 2019 at 12:20 AM Dmitry Torokhov > > wrote: > > > > > > On Fri, Jun 21, 2019 at 07:50:42AM -0700, Jeffrey Hugo wrote: > > > > Elan_i2c and hid-quirks w

Re: [PATCH v8 1/5] Input: elan_i2c: Export the device id whitelist

2019-06-27 Thread Benjamin Tissoires
On Thu, Jun 27, 2019 at 4:02 PM Jeffrey Hugo wrote: > > On Sun, Jun 23, 2019 at 12:20 AM Dmitry Torokhov > wrote: > > > > On Fri, Jun 21, 2019 at 07:50:42AM -0700, Jeffrey Hugo wrote: > > > Elan_i2c and hid-quirks work in conjunction to decide which devices each > > > driver will handle. Elan_i2

Re: [PATCH v8 1/5] Input: elan_i2c: Export the device id whitelist

2019-06-27 Thread Jeffrey Hugo
On Sun, Jun 23, 2019 at 12:20 AM Dmitry Torokhov wrote: > > On Fri, Jun 21, 2019 at 07:50:42AM -0700, Jeffrey Hugo wrote: > > Elan_i2c and hid-quirks work in conjunction to decide which devices each > > driver will handle. Elan_i2c has a whitelist of devices that should be > > consumed by hid-qui

Re: [PATCH v8 1/5] Input: elan_i2c: Export the device id whitelist

2019-06-22 Thread Dmitry Torokhov
On Fri, Jun 21, 2019 at 07:50:42AM -0700, Jeffrey Hugo wrote: > Elan_i2c and hid-quirks work in conjunction to decide which devices each > driver will handle. Elan_i2c has a whitelist of devices that should be > consumed by hid-quirks so that there is one master list of devices to > handoff betwee