From: Pavel Machek <pavel@ucw.cz>
To: David Brownell <david-b@pacbell.net>
Cc: Linus Torvalds <torvalds@osdl.org>,
Linux-pm mailing list <linux-pm@lists.osdl.org>
Subject: Re: [patch 2.6.18-rc2-mm 1/2] PM: make /sys/devices/.../power/state optional
Date: Wed, 16 Aug 2006 21:08:03 +0200 [thread overview]
Message-ID: <20060816190803.GB16571@elf.ucw.cz> (raw)
In-Reply-To: <200608161140.54035.david-b@pacbell.net>
Hi!
> > > Add a new PM_SYSFS_DEPRECATED config option to control whether or
> > > not the /sys/devices/.../power/state files are provided. ...
> >
> > Looks good to me, ACK.
> >
> > (And sorry for long delay).
>
> Greg still hasn't merged it; so, no prob. :)
>
> I updated patch 2/2 so that it doesn't test for the problematic and
> incomplete prepare_suspend() method, and to remove prepare_suspend().
> (That removal was discussed separately.)
>
>
>
> > I guess this should go with it...? OTOH andrew wanted alternative,
> > first, before removing the feature... but it is unclear to me if we
> > want the feature at all on the production system, so...
>
> How about this one instead? The issue is not limited to that sysfs
> file and its use of PM_EVENT_* codes, that's just the most visible
> facet of the problem.
Looks good to me.
> Index: o26/Documentation/feature-removal-schedule.txt
> ===================================================================
> --- o26.orig/Documentation/feature-removal-schedule.txt 2006-07-30 22:08:10.000000000 -0700
> +++ o26/Documentation/feature-removal-schedule.txt 2006-08-16 11:34:54.000000000 -0700
> @@ -6,6 +6,21 @@ be removed from this file.
>
> ---------------------------
>
> +What: /sys/devices/.../power/state
> + dev->power.power_state
> + dpm_runtime_{suspend,resume)()
> +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, iff they are even needed.
> +Who: Pavel Machek <pavel@suse.cz>
> +
> +---------------------------
> +
> What: RAW driver (CONFIG_RAW_DRIVER)
> When: December 2005
> Why: declared obsolete since kernel 2.6.3
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2006-08-16 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 20:37 [patch 2.6.18-rc2-mm 1/2] PM: make /sys/devices/.../power/state optional David Brownell
2006-08-16 11:57 ` Pavel Machek
2006-08-16 18:40 ` David Brownell
2006-08-16 19:08 ` Pavel Machek [this message]
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=20060816190803.GB16571@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=david-b@pacbell.net \
--cc=linux-pm@lists.osdl.org \
--cc=torvalds@osdl.org \
/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