As I send in my response Eric Biederman,
| If you have a platform where, for example, somehow PCI devices
| are able to continue jabbering away after the computer has been reset,
| then that could probably be done more consistently for most drivers by
| having machine_restart on that platform walk the PCI bus and shut down
| everything (drivers that need to do something really special would
| still use the reboot notifier).
|
| I could even see calling device_shutdown from machine_restart
| on that platform only, [...]
>And I never said anything about needing to allocate memory to do this.
>I agree with you that suspending devices on reboot _is_ silly. However,
>that's not what I was proposing.
Then you've started a new thread of discussion, because
device_shutdown is defined in drivers/base/power.c as:
void device_shutdown(void)
{
device_suspend(4, SUSPEND_POWER_DOWN);
}
Perhaps device_suspend ought to be renamed device_power_down.
However, I'm not trying to quash what you want to discuss.
I'd be interested in hearing about clarifications and perhaps
extensions of the struct device_driver methods, which I think is what
you're getting at, perhaps here or on linux-hotplug. It's just that,
for this thread, I'm trying to focus on my patch that eliminates the
software suspend on reboot (pros and cons, alternatives to it, etc.).
Adam J. Richter __ ______________ 575 Oroville Road
adam@yggdrasil.com \ / Milpitas, California 95035
+1 408 309-6081 | g g d r a s i l United States of America
"Free Software For The Rest Of Us."
-
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/