Re: [PATCH 1/2] watchdog: bcm7038_wdt: fix module autoload

2016-11-11 Thread Javier Martinez Canillas
Hello Guenter, On 11/11/2016 04:47 PM, Guenter Roeck wrote: > Hi Javier, > > On Fri, Nov 11, 2016 at 04:43:37PM -0300, Javier Martinez Canillas wrote: >> Hello Guenter, >> >> On 10/14/2016 01:55 PM, Guenter Roeck wrote: >>> On Fri, Oct 14, 2016 at 12:23:50PM -0300, Javier Martinez Canillas wrote:

Re: [PATCH 1/2] watchdog: bcm7038_wdt: fix module autoload

2016-11-11 Thread Guenter Roeck
Hi Javier, On Fri, Nov 11, 2016 at 04:43:37PM -0300, Javier Martinez Canillas wrote: > Hello Guenter, > > On 10/14/2016 01:55 PM, Guenter Roeck wrote: > > On Fri, Oct 14, 2016 at 12:23:50PM -0300, Javier Martinez Canillas wrote: > >> If the driver is built as a module, autoload won't work because

Re: [PATCH 1/2] watchdog: bcm7038_wdt: fix module autoload

2016-11-11 Thread Javier Martinez Canillas
Hello Guenter, On 10/14/2016 01:55 PM, Guenter Roeck wrote: > On Fri, Oct 14, 2016 at 12:23:50PM -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 >> devi

Re: [PATCH 1/2] watchdog: bcm7038_wdt: fix module autoload

2016-10-14 Thread Guenter Roeck
On Fri, Oct 14, 2016 at 12:23:50PM -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 inf

[PATCH 1/2] watchdog: bcm7038_wdt: fix module autoload

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 drive