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

> is this completely bad mojo ?  is there some other mechanism that
> provides what i want and i just dont know about it ?  or do i just
> make people change the driver to fit their application, thus throwing
> out the idea of keeping all board-specific details in just the boards
> file ...

There are two possibilities of interest I can think of (and maybe both
are useful). One is to deliver a signal to someone on expiry the other
would be to use notifier chains and export either the notifier or
add/remove operations. That allows multiple modules and users to chain
onto the expiry event

Take a look at include/linux/notifier.h

-
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/

---

• References:
  • how to allow board writers to customize driver behavior (watchdog here)
    • From: "Mike Frysinger" <[email protected]>

• Prev by Date: Re: Define CONFIG_BOUNCE to avoid useless inclusion of bounce buffer logic.
• Next by Date: Re: [PATCH 1/2] limit print_fatal_signal() rate (was: [RFC] log out-of-virtual-memory events)
• Previous by thread: Re: how to allow board writers to customize driver behavior (watchdog here)
• Next by thread: [PATCH netdev] "wrong timeout value" in sk_wait_data()
• Index(es):
  • Date
  • Thread

[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]