Re: pci bridge suspend/resume (Re: PCI not restored correctly after suspend to ram)

[Russell King <rmk-pci-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>]

On Tue, Mar 23, 2004 at 05:35:57PM -0800, Greg KH wrote:
> On Mon, Mar 22, 2004 at 10:34:25PM +0000, Adam Belay wrote:
> > > Yes, this will happen in 2.7 when we add the ability to have "generic"
> > > and "specific" type drivers for devices.
> > 
> > What do you think would be the best way to go about this?
> > 
> > I was able to come up with the following options:
> > 
> > 1.) flags in struct device_driver
> 
> I think this is the best place for it.  We will have to do something
> like weight the different ways to specify a driver can handle a device
> differently.  Something like this kind of priority:
> 	- device id
> 	- device class

The way I discussed with Pat two OLS's ago (I think it was two) was that
the bus type match method would return a value to indicate how well the
IDs matched the device.

When a driver matches a device, we remember this value, and call the
drivers ->probe function, as we do today.

However, when we add a new driver, we attempt to re-match all devices,
including those with drivers.  If a device with an existing driver is
found to have a "better" match with the new driver, the original driver's
->remove function is called to unbind the driver, and the new driver
bound to the device.

The match function would, for instance, return a lower value for a
device driver matching only the class IDs, a higher ID for a device
driver matching only the vendor ID, vendor ID + device ID, and the
highest value for vendor ID + device ID + class ID.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click