Re: [RESEND PATCH] mfd: max77686: Use module_i2c_driver() instead of subsys initcall

2016-04-11 Thread Lee Jones
On Mon, 04 Apr 2016, Javier Martinez Canillas wrote: > The driver's init and exit function don't do anything besides adding and > deleting the I2C driver so the module_i2c_driver() macro could be used. > > Currently is not being used because the driver is initialized at subsys > initcall level, c

Re: [RESEND PATCH] mfd: max77686: Use module_i2c_driver() instead of subsys initcall

2016-04-04 Thread Andi Shyti
Hi Javier, > The driver's init and exit function don't do anything besides adding and > deleting the I2C driver so the module_i2c_driver() macro could be used. > > Currently is not being used because the driver is initialized at subsys > initcall level, claiming that this is done to allow consume

Re: [RESEND PATCH] mfd: max77686: Use module_i2c_driver() instead of subsys initcall

2016-04-04 Thread Krzysztof Kozlowski
On 05.04.2016 07:46, Javier Martinez Canillas wrote: > The driver's init and exit function don't do anything besides adding and > deleting the I2C driver so the module_i2c_driver() macro could be used. > > Currently is not being used because the driver is initialized at subsys > initcall level, cl

[RESEND PATCH] mfd: max77686: Use module_i2c_driver() instead of subsys initcall

2016-04-04 Thread Javier Martinez Canillas
The driver's init and exit function don't do anything besides adding and deleting the I2C driver so the module_i2c_driver() macro could be used. Currently is not being used because the driver is initialized at subsys initcall level, claiming that this is done to allow consumers devices to use the