From: David Brownell <david-b@pacbell.net>
To: linux-kernel@vger.kernel.org
Cc: linux-pm@lists.linux-foundation.org, Harvey.Harrison@gmail.com,
Alan Stern <stern@rowland.harvard.edu>
Subject: Removing dev.power.power_state (WAS: Feature Removals for 2.6.25)
Date: Thu, 31 Jan 2008 21:28:09 -0800 [thread overview]
Message-ID: <200801312128.10700.david-b@pacbell.net> (raw)
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@suse.cz>
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
next reply other threads:[~2008-02-01 5:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 5:28 David Brownell [this message]
2008-02-01 15:22 ` Removing dev.power.power_state (WAS: Feature Removals for 2.6.25) Alan Stern
2008-02-01 21:24 ` David Brownell
2008-02-01 21:12 ` David Brownell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200801312128.10700.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=Harvey.Harrison@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox