On Wed, Mar 15, 2017 at 1:39 PM, Javier Martinez Canillas <javier@xxxxxxxxxxxxxxx> wrote: > Hello Andy, > > On 03/15/2017 08:21 AM, Andy Shevchenko wrote: >> On Wed, Mar 15, 2017 at 12:58 PM, Javier Martinez Canillas >> <javier@xxxxxxxxxxxxxxx> wrote: >>> On 03/15/2017 04:58 AM, Wolfram Sang wrote: >> >>> Unfortunately some maintainers do and don't accept patches adding I2C tables >>> only to have module autoloading working so I still think it should be fixed. >> >> Wait, how does it work for now?! > It only works if you have an I2C device ID table, but that may not be the case > for DT-only drivers that could only have an OF device ID table. In the latter > case module autoload won't work. OK. >> Sounds for me you are trying to solve non-existing issue. > It's an existing issue. You _must_ have an I2C device ID table if you want to > autload a device driver which is superfluous for DT-only drivers. Okay, can you scope only affected drivers then? Looking to spread patches from you over all drivers I dunno they are all affected right now. P.S. Personally I agree with maintainers who do *not* apply this. Sorry. -- With Best Regards, Andy Shevchenko -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
