58b3b71dfa
Commit bd804eba1c ("PM: Introduce
pm_power_off_prepare") caused problems in the poweroff path, as reported by
YOSHIFUJI Hideaki / 吉藤英明.
Generally, sysdev_shutdown() should be called after the ACPI preparation for
powering the system off. To make it happen, we can separate sysdev_shutdown()
from device_shutdown() and call it directly wherever necessary.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Tested-by: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@linux-ipv6.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
48 lines
1.1 KiB
C
48 lines
1.1 KiB
C
/*
|
|
* shutdown.c - power management functions for the device tree.
|
|
*
|
|
* Copyright (c) 2002-3 Patrick Mochel
|
|
* 2002-3 Open Source Development Lab
|
|
*
|
|
* This file is released under the GPLv2
|
|
*
|
|
*/
|
|
|
|
#include <linux/device.h>
|
|
#include <asm/semaphore.h>
|
|
|
|
#include "../base.h"
|
|
#include "power.h"
|
|
|
|
#define to_dev(node) container_of(node, struct device, kobj.entry)
|
|
|
|
|
|
/**
|
|
* We handle system devices differently - we suspend and shut them
|
|
* down last and resume them first. That way, we don't do anything stupid like
|
|
* shutting down the interrupt controller before any devices..
|
|
*
|
|
* Note that there are not different stages for power management calls -
|
|
* they only get one called once when interrupts are disabled.
|
|
*/
|
|
|
|
|
|
/**
|
|
* device_shutdown - call ->shutdown() on each device to shutdown.
|
|
*/
|
|
void device_shutdown(void)
|
|
{
|
|
struct device * dev, *devn;
|
|
|
|
list_for_each_entry_safe_reverse(dev, devn, &devices_subsys.list,
|
|
kobj.entry) {
|
|
if (dev->bus && dev->bus->shutdown) {
|
|
dev_dbg(dev, "shutdown\n");
|
|
dev->bus->shutdown(dev);
|
|
} else if (dev->driver && dev->driver->shutdown) {
|
|
dev_dbg(dev, "shutdown\n");
|
|
dev->driver->shutdown(dev);
|
|
}
|
|
}
|
|
}
|
|
|