Re: how to allow board writers to customize driver behavior (watchdog here)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 5/25/07, Daniel Newby <[email protected]> wrote:
On 5/24/07, Paul Mundt <[email protected]> wrote:
> So far the only example anyone has provided outside of periodic timers or
> hardware reset has been dumping the stack when something gets stuck.
> Softlockup does this already today, using a timer.

Many watchdogs can be hooked up to a non-maskable interrupt (NMI) that
cannot be disabled or preempted.  You get a stack dump even for drastic
bugs:  ISR lock up, timer misconfiguration, level-sensitive interrupt
line stuck asserted, and so forth.  Getting that information by other
means can be painful and/or expensive.

The Blackfin chip in the original message appears to support watchdog
NMI.

it does ... it has four modes:
- reset (drivers/char/watchdog/bfin_wdt.c)
- interrupt (i'll prob write a clockevents driver for this)
- NMI (no plans to do anything for this as NMI is unused in Blackfin)
- nothing (have yet to find a use case for this)
-mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux