Re: [PATCH v2 4/4] watchdog: aspeed: Move init to arch_initcall

2017-10-22 Thread Guenter Roeck
On 10/17/2017 04:35 AM, Andrew Jeffery wrote: On Wed, 2017-09-20 at 15:43 +0930, Joel Stanley wrote: On Wed, Sep 20, 2017 at 3:00 PM, Andrew Jeffery wrote: Probing at device_initcall time lead to perverse cases where the watchdog was probed after, say, I2C devices, which then leaves a potential

Re: [PATCH v2 4/4] watchdog: aspeed: Move init to arch_initcall

2017-10-17 Thread Andrew Jeffery
On Wed, 2017-09-20 at 15:43 +0930, Joel Stanley wrote: > > On Wed, Sep 20, 2017 at 3:00 PM, Andrew Jeffery wrote: > > Probing at device_initcall time lead to perverse cases where the > > watchdog was probed after, say, I2C devices, which then leaves a > > potentially running watchdog at the mercy

Re: [PATCH v2 4/4] watchdog: aspeed: Move init to arch_initcall

2017-09-19 Thread Joel Stanley
On Wed, Sep 20, 2017 at 3:00 PM, Andrew Jeffery wrote: > Probing at device_initcall time lead to perverse cases where the > watchdog was probed after, say, I2C devices, which then leaves a > potentially running watchdog at the mercy of I2C device behaviour and > bus conditions. > > Load the watchd

[PATCH v2 4/4] watchdog: aspeed: Move init to arch_initcall

2017-09-19 Thread Andrew Jeffery
Probing at device_initcall time lead to perverse cases where the watchdog was probed after, say, I2C devices, which then leaves a potentially running watchdog at the mercy of I2C device behaviour and bus conditions. Load the watchdog driver early to ensure that the kernel is patting it well before