On Fri, Feb 05, 2010 at 11:09:13PM +0100, Rafael J. Wysocki wrote: > On Friday 05 February 2010, you wrote: > > Hrm, I guess. It seems an odd thing to want to use - for a bus like I2C > > there's nothing other than the driver involved so the request that is > > being vetoed will have been initiated by the driver which seems wrong. > Not really. _idle is also called automatically by the runtime PM core after > _resume in case the device may be suspended again. Your _idle has to handle > this case as well and that's when the driver may want to veto the suspend. I was viewing that as being part of the same case, going on the basis that the driver would have marked the device as active already if something had changed over the suspend. The use cases that jumped out at me for the veto were for buses or classes rather than for individual devices. > > Out of interest do you have any pointers to drivers using this (my greps > > aren't turning anything up in -next)? > There aren't any in -next, because I'm waiting for the base PCI runtime PM > code to settle down. I have two in my private queue at the moment , for r8169 > and e1000e (I posted some older versions of them some time ago, but they > wouldn't fit the current framework too well, which is the basic reason I'm > sitting on them, so that I don't have to post too many updates :-)). > I can send them to you privately, if needed. No, that's OK - like I say, it was just out of interest. -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
