[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3135210.ApPvOPL31q@vostro.rjw.lan>
Date: Wed, 02 Jul 2014 01:18:11 +0200
From: "Rafael J. Wysocki" <rjw@...ysocki.net>
To: Alan Stern <stern@...land.harvard.edu>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Allen Yu <alleny@...dia.com>, Pavel Machek <pavel@....cz>,
Len Brown <len.brown@...el.com>,
Dan Williams <dan.j.williams@...el.com>,
Linux-pm mailing list <linux-pm@...r.kernel.org>,
Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] Add "rpm_not_supported" flag
On Monday, June 30, 2014 10:42:19 AM Alan Stern wrote:
> On Mon, 30 Jun 2014, Rafael J. Wysocki wrote:
>
> > > > Do you know of any tools that actually look at these files?
> > >
> > > I don't. Of course, that doesn't mean much.
> >
> > The only tool I'm aware of that may be looking at them is powertop, so
> > if the change doesn't affect powertop adversely, it should be generally
> > safe.
> >
> > > > If there isn't any, then we can try to change it and see who screams :)
> > >
> > > It'll be a learning experience...
> >
> > Yes, it will. :-)
>
> Then you have no other objections to the patch?
My concern still is that it will be confusing, because people won't read the
documentation carefully enough and will confuse "runtime PM never used" with
"hardware can't do PM". I'm not sure how to make that more clear, though.
Also we have the no_callbacks flag and I wonder if/how it is related to the
new one. Do we still need both?
In addition to that, I think that "hardware can't do PM" should apply to the
handling of system suspend resume too.
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists