29 Apr, 2016
1 commit
-
The enable time for buck regulators was not configured but actually is
essential: consumers, like usb3503, doing hard reset (regulator off/on)
should wait for the regulator to settle.Configure the enable time according to datasheet.
Signed-off-by: Krzysztof Kozlowski
Signed-off-by: Mark Brown
07 Apr, 2016
1 commit
-
The driver's init and exit function don't do anything besides registering
and unregistering the platform driver, so the module_platform_driver()
macro could just be used instead of having separate functions.Currently the macro is not being used because the driver is initialized at
subsys init call level but this isn't necessary since consumer devices are
defined in the DT as dependencies so there's no need for init calls order.Signed-off-by: Javier Martinez Canillas
Signed-off-by: Mark Brown
12 Feb, 2016
1 commit
-
The max77686 and max77802 regulator drivers are for sub-devices of a MFD
driver for some PMIC blocks. But the same object file name (max77686.o)
was used for both the common MFD driver and the max77686 regulator one.This confuses kbuild if both drivers are built as module causing the MFD
driver to not be copied when installing the modules.Also, max77{686,802} are a quite generic name for MFD subdevices drivers
so it is better to rename them to max77{686,802}-regulator like it's the
case for most regulator drivers.Signed-off-by: Javier Martinez Canillas
Signed-off-by: Mark Brown