> > probe:
> > Check for device existence and associate driver with it.
>
> What, exactly, does "associate driver" mean? Filling in the struct device
> field, perhaps? Calling register_chrdev (or register_whatever)? Creation
> of a ddfs entry? As a driver writer I can understand that the probe
> routine should check for the existence of some device, and perhaps set up
> an internal data structure. What else happens?
That's basically it. The bus should have already known about the existence
of the device, filled in the fields of struct device and registered it in
the global tree.
As Jeff Garzik suggested:
probe:
register interface
sanity check h/w to make sure it's there and alive
stop DMA/interrupts/etc., just in case
start timer to powerdown h/w in N seconds
in which interface would be your device node (char dev, devfs node, etc).
-pat
-
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 : Tue Oct 23 2001 - 21:00:21 EST