Re: [PATCH 2/2] mfd: intel_soc_pmic_chtwc: Fix module autoload

2017-08-09 Thread Javier Martinez Canillas
Hello Hans, On 08/09/2017 02:02 PM, Hans de Goede wrote: > Hi, > > On 09-08-17 10:44, Javier Martinez Canillas wrote: >> The driver has a tristate Kconfig symbol so it can be built as a module, >> but it doesn't export the device aliases in the module. So if the driver >> is built as module,

Re: [PATCH 2/2] mfd: intel_soc_pmic_chtwc: Fix module autoload

2017-08-09 Thread Javier Martinez Canillas
Hello Hans, On 08/09/2017 02:02 PM, Hans de Goede wrote: > Hi, > > On 09-08-17 10:44, Javier Martinez Canillas wrote: >> The driver has a tristate Kconfig symbol so it can be built as a module, >> but it doesn't export the device aliases in the module. So if the driver >> is built as module,

Re: [PATCH 2/2] mfd: intel_soc_pmic_chtwc: Fix module autoload

2017-08-09 Thread Hans de Goede
Hi, On 09-08-17 10:44, Javier Martinez Canillas wrote: The driver has a tristate Kconfig symbol so it can be built as a module, but it doesn't export the device aliases in the module. So if the driver is built as module, autoload won't work since udev/kmod won't be able to match the registered

Re: [PATCH 2/2] mfd: intel_soc_pmic_chtwc: Fix module autoload

2017-08-09 Thread Hans de Goede
Hi, On 09-08-17 10:44, Javier Martinez Canillas wrote: The driver has a tristate Kconfig symbol so it can be built as a module, but it doesn't export the device aliases in the module. So if the driver is built as module, autoload won't work since udev/kmod won't be able to match the registered