mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: [RFC] Plan to get rid of all legacy PM handling
Date: Sun, 17 Jun 2012 16:49:40 -0700	[thread overview]
Message-ID: <20120617234940.GB11910@kroah.com> (raw)
In-Reply-To: <201206172310.49148.rjw@sisk.pl>

On Sun, Jun 17, 2012 at 11:10:49PM +0200, Rafael J. Wysocki wrote:
> Hi all,
> 
> I have a plan to replace all of the legacy device PM callbacks throughout
> the kernel with PM handling based on struct dev_pm_ops objects.  Ultimately,
> that should make it possible to remove the legacy hooks from struct bus_type
> and struct device_driver and to siplify the PM core and some bus types
> (most importantly PCI) quite a bit.
> 
> I'm going to start with platform drivers that should be the most
> straightforward to convert and when they all have been dealt with it
> should be possible to drop the platform bus type's PM callbacks entirely.
> Next, I'm going to take care of the bus types that only define PM callbacks
> to call drivers' callbacks, which is completely unnecessary after some PM
> core changes that went in during the 3.4 development cycle.  Finally, I will
> be looking at PCI drivers.
> 
> The task is huge, but I've done similar things already, so it's nothing new
> to me.  So, if you're a maintainer of code that contains legacy PM handling,
> please be prepared to see some patches from me in a not-too-distant-future.

Nice, that work is great to see have happen, thanks for taking this on,
it's much needed.

greg k-h

      reply	other threads:[~2012-06-17 23:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-17 21:10 Rafael J. Wysocki
2012-06-17 23:49 ` Greg KH [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=20120617234940.GB11910@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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

all inboxes | Powered by JetHome®