Re: [PATCH][RFC] Proposal for a new watchdog interface using sysfs

Rusty Lynch (rusty@linux.co.intel.com)
14 Feb 2003 07:32:33 -0800


On Fri, 2003-02-14 at 06:48, Alan Cox wrote:
> On Fri, 2003-02-14 at 00:47, Rusty Lynch wrote:
> > Ok, I had to go and read the driver-model documentation a couple of more
> > times, but after I actually started writing some code it finally started
> > to make sense.
>
> The watchdog_ops is probably a good thing anyway. If you also use that
> same structure with the base watchdog module having the ioctl parser all
> the ioctl handling funnies and quirks in the drivers go away except
> for driver private stuff.
>
> Two for the price of one
>
> Alan
>

Since only one driver can register as the /dev/watchdog (ie
major=10/minor=130 char device), would it be better if:

* the first watchdog driver to register with the base also gets
registered as the watchdog misc device, and when that driver unregisters
then the second watchdog to register now gets registered as the misc
device, etc.
* each watchdog driver gets an additional sysfs file named 'misc', where
writing a '1' to the file causes the driver to become the registered
misc watchdog device.
* something else

--rustyl

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/