[RESEND RFT PATCH 0/2] mfd: max14577: Allow the driver to be built as a module
This series is similar to  and allows the max14577 PMIC MFD driver to
be built as a module. Currently the Kconfig symbol for the driver is a
boolean but there isn't really a reason for this restriction.
Chanwoo Choi tried to test the original post but found a build issue .
The fix for that issue landed in v4.6 so I'm resending this series now
that there are no in-flight dependencies anymore.
The patches have been just built tested because I don't have any of the
boards using this driver, so testing will be highly appreciated.
[RESEND RFT PATCH 1/2] mfd: max14577: Use module_init() instead of subsys_initcall()
The driver's init function is called at subsys init call level but the
dependencies provided by the driver are looked up by drivers that have
probe deferral support, so manual ordering of init calls isn't needed.
I checked an the only users in mainline for this driver are the Exynos3250
Monk and Rinato boards. In both, only two regulators are used (safeout_reg
and motor_reg) and these are looked up by the drivers phy-samsung-usb2 and
regulator-haptic respectively, and both support probe deferral.
[RESEND RFT PATCH 2/2] mfd: max14577: Allow driver to be built as a module
In reply to this post by Javier Martinez Canillas-4
The driver's Kconfig symbol is a boolean but nothing prevents the driver
to be built as a module instead of built-in. It is true that most system
integrators will choose the latter but the config should not restrict it.