[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200705240929.51696.rgetz@blackfin.uclinux.org>
Date: Thu, 24 May 2007 09:29:51 -0400
From: Robin Getz <rgetz@...ckfin.uclinux.org>
To: "Paul Mundt" <lethal@...ux-sh.org>
Cc: "Mike Frysinger" <vapier.adi@...il.com>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
"Bryan Wu" <Bryan.Wu@...log.com>
Subject: Re: how to allow board writers to customize driver behavior (watchdog here)
On Thu 24 May 2007 01:23, Paul Mundt pondered:
> On Thu, May 24, 2007 at 12:21:47AM -0400, Mike Frysinger wrote:
> > 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 ...
>
> It sounds like your constraining your driver based on terminology.
> Watchdogs on most embedded platforms support either a 'reset' mode or
> otherwise act as periodic timers, trying to push both of these
> functionalities in to a watchdog driver is rather pointless.
> CONFIG_WATCHDOG implies 'reset' mode by definition.
I understand what you mean - typically - most people think of watchdog ==
reset.
But, calling it a periodic timer, and servicing it with the watchdog user
space demon is even more confusing - isn't it?
-Robin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists