Re: [PATCH v2] clk: samsung: clk-exynos-audss: Fix module autoload

2016-10-17 Thread Stephen Boyd
On 10/16, Javier Martinez Canillas wrote: > If the driver is built as a module, autoload won't work because the module > alias information is not filled. So user-space can't match the registered > device with the corresponding module. > > Export the module alias information using the

Re: [PATCH v2] clk: samsung: clk-exynos-audss: Fix module autoload

2016-10-17 Thread Stephen Boyd
On 10/16, Javier Martinez Canillas wrote: > If the driver is built as a module, autoload won't work because the module > alias information is not filled. So user-space can't match the registered > device with the corresponding module. > > Export the module alias information using the

[PATCH v2] clk: samsung: clk-exynos-audss: Fix module autoload

2016-10-16 Thread Javier Martinez Canillas
If the driver is built as a module, autoload won't work because the module alias information is not filled. So user-space can't match the registered device with the corresponding module. Export the module alias information using the MODULE_DEVICE_TABLE() macro. Before this patch: $ modinfo

[PATCH v2] clk: samsung: clk-exynos-audss: Fix module autoload

2016-10-16 Thread Javier Martinez Canillas
If the driver is built as a module, autoload won't work because the module alias information is not filled. So user-space can't match the registered device with the corresponding module. Export the module alias information using the MODULE_DEVICE_TABLE() macro. Before this patch: $ modinfo