Removing dev.power.power_state (WAS: Feature Removals for 2.6.25)

[David Brownell]

Quoth Harvey Harrison:

> Ping?
> What:	dev->power.power_state
> When:	July 2007
> Why:	Broken design for runtime control over driver power states, confusing
> 	driver-internal runtime power management with:  mechanisms to support
> 	system-wide sleep state transitions; event codes that distinguish
> 	different phases of swsusp "sleep" transitions; and userspace policy
> 	inputs.  This framework was never widely used, and most attempts to
> 	use it were broken.  Drivers should instead be exposing domain-specific
> 	interfaces either to kernel or to userspace.
> Who:	Pavel Machek <pavel@xxxxxxx>

A lot of the infrastructure using that has already been deleted, and
there are some incremental improvements pending for 2.6.25:

 - drivers/input/touchscreen/ads7846.c ... patch fixing this
   should be in either MM or the input queue

 - Documentation/power/devices.txt ... patch fixing this is
   in the suspend tree, due to merge RSN

 - drivers/spi/spi.c ... patch fixing this is in MM, due to
   merge with other SPI patches

 - drivers/pcmcia/ds.c ... at least I *think* that patch got sent

But there are still quite a few users left, and a new one was (sigh)
recently added.

 - drivers/rtc/rtc-sa1100.c ... new usage, merged last week

 - drivers/usb/... has various users, HCDs look easy enough to fix but
   the other bits will take more thought

 - drivers/ata/... has some too

 - drivers/ide/ppc/pmac.c

 - drivers/spi/... some controller drivers use this (look easy to fix)

 - drivers/scsi/mesh.c

 - drivers/input/serio/... has a few users

 - ... more ...

I'll probably send in a few more patches for easy stuff in areas
that I touch semi-frequently, but other folk should fix ATA, IDE,
SCSI, SERIO, and so forth.  It'd be good if Alan would help fix
the USB stuff too.  I'm not sure what Pavel's doing there...

- Dave

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/