On Thu, 2003-02-13 at 03:55, Dave Jones wrote:
> On Wed, Feb 12, 2003 at 07:16:55PM -0800, Rusty Lynch wrote:
> > Basically, with the help of some watchdog infrastructure code, we could make
> > each watchdog device register as a platform_device named watchdog, so for
> > every watchdog on the system there is a /sys/devices/legacy/watchdogN/
> > directory created for it.
>
> Why legacy ? That seems an odd place to be putting these.
>
> Dave
>
> --
> | Dave Jones. http://www.codemonkey.org.uk
> | SuSE Labs
The watchdogN devices show up under the "legacy" directory because
they are platform devices. From reading the driver-model documentation,
I believe that platform devices are the correct way of categorizing
watchdog devices.
<pasting from Documentation/driver-model/platform.txt>
Platform devices
~~~~~~~~~~~~~~~~
Platform devices are devices that typically appear as autonomous
entities in the system. This includes legacy port-based devices and
host bridges to peripheral buses.
Platform drivers
~~~~~~~~~~~~~~~~
Drivers for platform devices have typically very simple and
unstructured. Either the device was present at a particular I/O port
and the driver was loaded, or there was not. There was no possibility
of hotplugging or alternative discovery besides probing at a specific
I/O address and expecting a specific response.
</pasting from Documentation/driver-model/platform.txt>
-
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/
This archive was generated by hypermail 2b29 : Sat Feb 15 2003 - 22:00:47 EST