On Thu, 2 Sep 2010, Rafael J. Wysocki wrote: > > The driver can't use a different value without having it show up in > > sysfs. Unless we store _two_ suspend_delay values in dev_pm_info: the > > value to display in sysfs and the value to actually be used. This > > doesn't seem like a good idea. > > I wanted to say that, if the value in suspend_delay was regarded as the preferred > one (not mandatory), the driver would be free to actually suspend the device > without waiting that time or to wait longer, depending on circumstances. That > doesn't imply having a separate delay field for the driver to use. Ah, but the way this is designed means that the value to be used _must_ be stored in dev_pm_info. This will become obvious when you see the code. I can send a preliminary patch if you are interested. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
