- Move SMP check to software_suspend() (from software_resume()), so we will
  not even attempt to sleep with it enabled.
- Make software_resume() a late initcall, removing the explicit call from
  prepare_namespace(). 
- Initialize software_suspend_enabled to 1, instead of doing it manually in
  software_resume().
- Don't explicitly initialzie resume_file.
- Remove resume_status variable, as we can simply check for (non-) NULL 
  resume_file string. 
- "noresume" setup function changed to simply zero first byte of resume_file
  string, simplifying logic.
- Don't attempt to reset swap signature if noresume is specified.
  - Downstream function (bdev_write_page() wasn't implemented anyway, so we
    can just remove that also).

If noresume is specified, there will still be a suspend image left on the 
swap partition. It may behoove us to never reset the swap signature, and 
always leave the image intact on the disk, since it is a valid snapshot 
that we can resume from at anytime. 

This unconditional behavior would force the user to add 'mkswap <part>' to
their init scripts to reset the partition to swap use. IMO, this is better
anyway.

- Make software_suspend() return an int, so caller can tell what happened.
- Do check for HIGHMEM and DISCONTIGMEM early in software_suspend() and 
  fail gracefully, instead of checking far down the call chain and having
  to call panic().

From Pavel Machek.

From Pavel Machek.

- Moves sysfs controls to drivers/base/power/sysfs.c
- Creates dpm_sysfs_{add,remove} to add/remove sysfs attribute group.
- Creates 'state' file in 'pm' directory that properly controls device
  power state at runtime.

into osdl.org:/home/mochel/src/kernel/devel/linux-2.5-power

dpm_runtime_{suspend,resume} control the power state of a single device 
while the system is running. 

dpm_runtime_suspend() will save state of the device, then attempt to power
it down. This happens with interrupts enabled, so if the device does not 
support that, the device's state is restored, and we continue on our merry
way.

dpm_runtime_resume() powers the device back on, then restores state of the
device.

dpm_set_power_state() simply notifies the core of the power state the
device is in. Drivers can use this, since they are the only ones that can
really tell.

From Janice Girouard. 

Currently if an error is detected when probing a device,
this error is not reported. Generally, an error value from
errno.h will be returned when the driver->probe function
fails. However, these errors are not logged, and the device
fails silently.

From Stephen Hemminger: 

Several of the class_device functions don't modify their arguments and can
take const pointers.

From Stephen Hemminger

From Stephen Hemminger. Needed to use attribute groups effectively.
 

into osdl.org:/home/mochel/src/kernel/devel/linux-2.5-core

- Add ->pm_users and ->pm_parent fields to struct dev_pm_info. 
- Add function device_pm_set_parent()

The default power parent for a device is the device's physical parent, but
a driver may change it to represent a tranversal power dependency. 

Though it's not incorporated into the suspend/resume sequences yet, the 
core will respect the power tree, rather than the physical/electrical one.

Also added is a power usage count for devices, which indicates how many 
devices are dependent on that one for power (how many children it has in 
the power tree). The core will use this count to determine whether or not
a device can be put into a low power state or not. 

into osdl.org:/home/mochel/src/kernel/devel/linux-2.5-power

into osdl.org:/home/mochel/src/kernel/devel/linux-2.5-power

The following patch has been floating around forever.  It is required
for several ARM framebuffer drivers, and several other drivers.  James
has indicated that this is the correct fix back in May.

This provides the necessary infrastructure for PowerMac specific drivers
(and actually some Open Firmware platform drivers on non-PowerMacs as
well provided somebody port them) to be properly probed & referenced via
the new driver model and be part of sysfs.

As-is, this patch doesn't break anything nor change any driver.  I'll
send you individual driver patches as I clean them up & get them tested
on as many machines as possible, though I don't expect much problems.

While reviewing my 2.4 backport of the 2.6 cpu capabilities (including
the Via RNG support), Mikael Pettersson noticed a bug in both my
backport, and 2.6:  when NCAPINTS (x86_capability array size) is
increased, one must adjust the offset in arch/i386/kernel/head.S also.

Contributed by Mikael Pettersson.

This makes the HISAX ST5481 driver build again with 2.6.0-test3 where
the usb_host_config structure has changed.

some small clean-ups: do correct errorhandling

added WDIOC_SETTIMEOUT and WDIOC_GETTIMEOUT ioctls
made timeout (the emulated heartbeat) a module_param
made the keepalive ping an internal subroutine

add CONFIG_WATCHDOG_NOWAYOUT support
changed watchdog_info to correctly reflect what the driver offers
added WDIOC_GETSTATUS, WDIOC_GETBOOTSTATUS and WDIOC_SETOPTIONS ioctls
use module_param

cleanup comments and trailing spaces
eliminate extra spin_unlock
add KERN_* tags to printks
added extra printk's to report what problem occured

some small clean-ups (use PFX + report default timeout as it's value in the MODULE_PARM_DESC)

some last clean-ups

added extra printk's to report what problem occured

make wdt_stop and wdt_start module params

report default timeout as a number

general cleanup of trailing spaces and comments
fix possible wdt_is_open race
add KERN_* to printk's
changed watchdog_info to correctly reflect what the driver offers
added WDIOC_GETSTATUS, WDIOC_GETBOOTSTATUS, WDIOC_SETTIMEOUT, WDIOC_GETTIMEOUT, and WDIOC_SETOPTIONS ioctls
made timeout (the emulated heartbeat) a module_param
made the keepalive ping an internal subroutine
added MODULE_AUTHOR and MODULE_DESCRIPTION info

Contributed by VIA, via Jean Tourrilhes.

ir260_tekram-sir.diff :
~~~~~~~~~~~~~~~~~~~~~
		<Patch from Martin Diehl>
	o [CORRECT] Update tekram-sir dongle driver to common power-settling

ir260_usb_probe-4.diff :
~~~~~~~~~~~~~~~~~~~~~~
		<Patch from Oliver Neukum and Daniele Bellucci>
	o [CORRECT] minor fix to the probe failure path of irda-usb.

ir260_lap_retry_count.diff :
~~~~~~~~~~~~~~~~~~~~~~~~~~
	o [CORRECT] add interoperability workaround for 2.4.X IrDA stacks

ir260_donau_cleanup.diff :
~~~~~~~~~~~~~~~~~~~~~~~~
		<Patch from Christian Gennerat>
	o [CORRECT] Disable chip probing that fail too often
	o [FEATURE] Cleanup STATIC

We don't need the spinlock to protect the lists (at least not now), since 
we have a semaphore to synchronize all operations device PM operations.

into home.osdl.org:/home/torvalds/v2.5/linux

into home.osdl.org:/home/torvalds/v2.5/linux

into kroah.com:/home/greg/linux/BK/pci-2.6

Bug #1 (found by Jay Estabrook).
On Alpha, under certain circumstances the firmware may close the IO
window of PCI-to-PCI bridge even if there is IO behind.
This wouldn't be a problem - linux PCI setup code does set up this
window properly, but in addition the firmware clears the IO-enable
bit in the PCI_COMMAND register of the bridge.
Since we don't call pci_enable_* routines for bridges in non-hotplug
path, we end up with disabled IO. Fixed by adding pci_enable_bridges()
to pci_assign_unassigned_resources().
Architectures which don't use the latter, but do use other setup-bus
code (parisc?) also should call pci_enable_bridges() for each root bus.

Bug #2 (closely related to #1).
As it turns out, pci_enable_device() doesn't work for bridges at all,
only for regular devices (header type 0) due to 0x3f mask passed to
pci_enable_device_bars(). The mask should be (1 << PCI_NUM_RESOURCES) - 1.

Bug #3 (quite a few archs, including i386).
pcibios_enable_device() does only check first 6 resources (regardless
of the mask) to decide whether or not to enable IO and MEM.
Bridge resources start at 7.

#2 and #3 affect hotplug. I wonder, has anybody ever tried *bridged*
PCI card behind a hot-plug controller?