mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Linux PM list <linux-pm@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	Arnd Bergmann <arnd@arndb.de>
Subject: [PATCH 0/2] PM / Domains: Allow drivers to attach PM domain callbacks to devices at any time
Date: Tue, 3 Jul 2012 12:27:45 +0200	[thread overview]
Message-ID: <201207031227.45383.rjw@sisk.pl> (raw)

Hi,

This is a follow-up of the discussion I had with Arnd and Magnus during
the LCJ last month.

Namely, one of the limitations of the current generic PM domains code is that
pm_genpd_add_callbacks() has to be executed after the device in question has
been added to a PM domain.  This means that, if a driver wants to run this
routine from its .probe() callback, it cannot be registered before adding
the device to the PM domain, which potentially may be a problem when device
trees get involved into the system initialization.

For this reason, it is desirable to allow pm_genpd_add_callbacks() to be called
for devices that haven't been added to any generic PM domains yet and the
following patches attempt to make that happen.

[1/2] Add reference counter for objects used to store PM domains data related
      to devices.
[2/2] Make it possible to call pm_genpd_add_callbacks() before the device is
      added to a PM domain.

Thanks,
Rafael


             reply	other threads:[~2012-07-03 10:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03 10:27 Rafael J. Wysocki [this message]
2012-07-03 10:28 ` [PATCH 1/2] PM / Domains: Add device domain data reference counter Rafael J. Wysocki
2012-07-03 10:29 ` [PATCH 2/2] PM / Domains: Allow device callbacks to be added at any time Rafael J. Wysocki
2012-07-05 19:46 ` [PATCH 0/2] PM / Domains: Allow drivers to attach PM domain callbacks to devices " Rafael J. Wysocki

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=201207031227.45383.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    /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®