Re: [PATCH v2 3/3] Input: qt1070 - Add OF device ID table

2017-03-27 Thread Javier Martinez Canillas
Hello Dmitry, On 03/23/2017 06:45 PM, Dmitry Torokhov wrote: > On Thu, Mar 23, 2017 at 04:14:56PM -0300, Javier Martinez Canillas wrote: >> Hello Dmitry, >> >> On 02/22/2017 11:40 AM, Javier Martinez Canillas wrote: >>> The driver doesn't have a struct of_device_id table but supported devices >>>

Re: [PATCH v2 3/3] Input: qt1070 - Add OF device ID table

2017-03-23 Thread Dmitry Torokhov
On Thu, Mar 23, 2017 at 04:14:56PM -0300, Javier Martinez Canillas wrote: > Hello Dmitry, > > On 02/22/2017 11:40 AM, Javier Martinez Canillas wrote: > > The driver doesn't have a struct of_device_id table but supported devices > > are registered via Device Trees. This is working on the assumption

Re: [PATCH v2 3/3] Input: qt1070 - Add OF device ID table

2017-03-23 Thread Javier Martinez Canillas
Hello Dmitry, On 02/22/2017 11:40 AM, Javier Martinez Canillas wrote: > The driver doesn't have a struct of_device_id table but supported devices > are registered via Device Trees. This is working on the assumption that a > I2C device registered via OF will always match a legacy I2C device ID and

[PATCH v2 3/3] Input: qt1070 - Add OF device ID table

2017-02-22 Thread Javier Martinez Canillas
The driver doesn't have a struct of_device_id table but supported devices are registered via Device Trees. This is working on the assumption that a I2C device registered via OF will always match a legacy I2C device ID and that the MODALIAS reported will always be of the form i2c:. But this could c