Re: [PATCH 1/3] Input: silead - Add OF device ID table

2017-02-22 Thread Javier Martinez Canillas
Hello Hans, On 02/22/2017 11:23 AM, Hans de Goede wrote: > HI, > > On 22-02-17 13:45, Javier Martinez Canillas wrote: >> Hello Hans, >> >> Thanks for your feedback. >> >> On 02/22/2017 05:29 AM, Hans de Goede wrote: >>> Hi, >>> >>> On 21-02-17 19:12, Javier Martinez Canillas wrote: The

Re: [PATCH 1/3] Input: silead - Add OF device ID table

2017-02-22 Thread Javier Martinez Canillas
Hello Hans, On 02/22/2017 11:23 AM, Hans de Goede wrote: > HI, > > On 22-02-17 13:45, Javier Martinez Canillas wrote: >> Hello Hans, >> >> Thanks for your feedback. >> >> On 02/22/2017 05:29 AM, Hans de Goede wrote: >>> Hi, >>> >>> On 21-02-17 19:12, Javier Martinez Canillas wrote: The

Re: [PATCH 1/3] Input: silead - Add OF device ID table

2017-02-22 Thread Hans de Goede
HI, On 22-02-17 13:45, Javier Martinez Canillas wrote: Hello Hans, Thanks for your feedback. On 02/22/2017 05:29 AM, Hans de Goede wrote: Hi, On 21-02-17 19:12, Javier Martinez Canillas wrote: The driver doesn't have a struct of_device_id table but supported devices are registered via

Re: [PATCH 1/3] Input: silead - Add OF device ID table

2017-02-22 Thread Hans de Goede
HI, On 22-02-17 13:45, Javier Martinez Canillas wrote: Hello Hans, Thanks for your feedback. On 02/22/2017 05:29 AM, Hans de Goede wrote: Hi, On 21-02-17 19:12, Javier Martinez Canillas wrote: The driver doesn't have a struct of_device_id table but supported devices are registered via

Re: [PATCH 1/3] Input: silead - Add OF device ID table

2017-02-22 Thread Javier Martinez Canillas
Hello Hans, Thanks for your feedback. On 02/22/2017 05:29 AM, Hans de Goede wrote: > Hi, > > On 21-02-17 19:12, 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

Re: [PATCH 1/3] Input: silead - Add OF device ID table

2017-02-22 Thread Javier Martinez Canillas
Hello Hans, Thanks for your feedback. On 02/22/2017 05:29 AM, Hans de Goede wrote: > Hi, > > On 21-02-17 19:12, 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

Re: [PATCH 1/3] Input: silead - Add OF device ID table

2017-02-22 Thread Hans de Goede
Hi, On 21-02-17 19:12, 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 that the MODALIAS

Re: [PATCH 1/3] Input: silead - Add OF device ID table

2017-02-22 Thread Hans de Goede
Hi, On 21-02-17 19:12, 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 that the MODALIAS

[PATCH 1/3] Input: silead - Add OF device ID table

2017-02-21 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

[PATCH 1/3] Input: silead - Add OF device ID table

2017-02-21 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