Re: [PATCH] mfd: mt6397: Add platform device ID table

2016-02-10 Thread Lee Jones
On Tue, 09 Feb 2016, Javier Martinez Canillas wrote: > The platform bus_type .match callback attempts to match the platform device > name with an entry on the .id_table if provided and fallbacks to match with > the driver's name if a table is not provided. > > Using a platform device ID to match

Re: [PATCH] mfd: mt6397: Add platform device ID table

2016-02-10 Thread Lee Jones
On Tue, 09 Feb 2016, Javier Martinez Canillas wrote: > The platform bus_type .match callback attempts to match the platform device > name with an entry on the .id_table if provided and fallbacks to match with > the driver's name if a table is not provided. > > Using a platform device ID to match

[PATCH] mfd: mt6397: Add platform device ID table

2016-02-09 Thread Javier Martinez Canillas
The platform bus_type .match callback attempts to match the platform device name with an entry on the .id_table if provided and fallbacks to match with the driver's name if a table is not provided. Using a platform device ID to match is more explicit, allows the driver to support more than one

[PATCH] mfd: mt6397: Add platform device ID table

2016-02-09 Thread Javier Martinez Canillas
The platform bus_type .match callback attempts to match the platform device name with an entry on the .id_table if provided and fallbacks to match with the driver's name if a table is not provided. Using a platform device ID to match is more explicit, allows the driver to support more than one