Re: [PATCH 1/2] Input: fsl-imx25-tcq - fix module autoload when registered via OF

2016-10-26 Thread Dmitry Torokhov
On Fri, Oct 14, 2016 at 01:00:18PM -0300, 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

Re: [PATCH 1/2] Input: fsl-imx25-tcq - fix module autoload when registered via OF

2016-10-26 Thread Dmitry Torokhov
On Fri, Oct 14, 2016 at 01:00:18PM -0300, 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

[PATCH 1/2] Input: fsl-imx25-tcq - fix module autoload when registered via OF

2016-10-14 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 1/2] Input: fsl-imx25-tcq - fix module autoload when registered via OF

2016-10-14 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