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

[Adam Belay <ambx1-IBH0VoN/3vPQT0dZR+AlfA@public.gmane.org>]

On Sat, Mar 20, 2004 at 10:10:00AM -0800, Greg KH wrote:
> On Sat, Mar 20, 2004 at 01:45:42PM +0000, Matthew Wilcox wrote:
> > On Sat, Mar 20, 2004 at 03:28:54AM -0500, Jeff Garzik wrote:
> > > Len Brown wrote:
> > > >Linux PCI list,
> > > >
> > > >Stefan noticed bits changing in the config space for
> > > >his PCI/PCI bridge across a C3 suspend/resume.
> > > >
> > > >Is there any software in Linux responsible for preserving
> > > >and restoring the PCI config space for PCI/PCI bridges
> > > >across a suspend/resume?
> > >
> > > Left up to the individual drivers unfortunately...
> >
> > I've often thought we needed a generic pci bridge driver ...

I agree.  It would be nice to see devices such as a PCI bridge
using the standard driver model methods.

>
> Yes, this will happen in 2.7 when we add the ability to have "generic"
> and "specific" type drivers for devices.
>
> thanks,
>
> greg k-h

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
2.) return codes from (*match)
3.) a seperate bus specific function to evaluate driver priority

Also how can we prevent the order in which drivers are loaded from
determining which driver is bound?  It seems that we would need to
delay device matching.

Thanks,
Adam


-------------------------------------------------------
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