[PATCH] OMAP2PLUS: WDT: Fix: Disable WDT after reset during init
santosh.shilimkar at ti.com
Fri Oct 1 03:26:14 EDT 2010
> -----Original Message-----
> From: Kevin Hilman [mailto:khilman at deeprootsystems.com]
> Sent: Thursday, September 30, 2010 10:42 PM
> To: Shilimkar, Santosh
> Cc: Varadarajan, Charulatha; Tony Lindgren; Cousson, Benoit; Menon,
> Nishanth; wim at iguana.be; linux-omap at vger.kernel.org; linux-
> watchdog at vger.kernel.org; linux-arm-kernel at lists.infradead.org;
> paul at pwsan.com; Nayak, Rajendra; Basak, Partha
> Subject: Re: [PATCH] OMAP2PLUS: WDT: Fix: Disable WDT after reset during
> "Shilimkar, Santosh" <santosh.shilimkar at ti.com> writes:
> >> -----Original Message-----
> >> From: linux-omap-owner at vger.kernel.org [mailto:linux-omap-
> >> owner at vger.kernel.org] On Behalf Of Varadarajan, Charulatha
> >> Sent: Thursday, September 30, 2010 9:25 PM
> >> To: Tony Lindgren; Cousson, Benoit
> >> Cc: Kevin Hilman; Menon, Nishanth; wim at iguana.be; linux-
> >> omap at vger.kernel.org; linux-watchdog at vger.kernel.org; linux-arm-
> >> kernel at lists.infradead.org; paul at pwsan.com; Nayak, Rajendra; Basak,
> >> Subject: RE: [PATCH] OMAP2PLUS: WDT: Fix: Disable WDT after reset
> >> init
> >> Tony/ Benoit,
> >> > >
> >> > > I think that disabling it should be done only if the
> >> > > is not set.
> >> >
> >> > How about disabling is done always unless CONFIG_WATCHDOG_NOWAYOUT
> >> > is set?
> >> As given in the patch description, this patch does a disable of
> >> timer, during init, to avoid the system rebooting that happens due to
> >> enabling of watchdog timer after a reset of the module (during hwmod
> >> According to the default WDT registers values, the system reboot would
> >> happen in ~10s if watchdog is enabled with default values. Hence, after
> >> a WDT module reset during init, the watchdog has to be disabled within
> >> otherwise the system will keep rebooting.
> >> Hence irrespective of CONFIG_WATCHDOG_NOWAYOUT/ CONFIG_OMAP_WDT,
> >> the watchdog timer needs to be disabled after a WDT reset has happened.
> > One more option is to avoid the software reset using the CONFIG_OMAP_WDT
> > flag. Something like below.
> This was already proposed by Charu, and rejected.
> Doing this means we have a dependency on particular bootloader init, and
> we'd like to get rid of *all* assumptions about what the bootloader does
> (or does not do.)
you mean is not depeding on bootloader to disable WDT. Make sense.
More information about the linux-arm-kernel