From: Jon Hunter <jonathanh@nvidia.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Kevin Hilman <khilman@linaro.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: [RFD] PM_GENERIC_DOMAINS && !PM
Date: Mon, 30 Nov 2015 16:42:46 +0000 [thread overview]
Message-ID: <565C7C86.7030801@nvidia.com> (raw)
Currently, if PM is disabled in the kernel then so is
PM_GENERIC_DOMAINS. Although this makes sense, I can see a scenario
where having minimal genpd support could be advantageous.
I am looking at enabling genpd for Tegra and ideally we would populate
the power domains when the platform device is probed for the power
management controller (PMC) as this device contains the registers for
enabling the power domains.
This works fine for the case where PM is enabled, but I am concerned
about the case where we don't have PM enabled in the kernel. In this
case, because domains are not populated early during the boot process, I
am concerned that there is a chance for a device dependent on a power
domain to be probed before the PMC device has been probed and had chance
to turn on any power domains.
Obviously, we could try and play with the ordering of devices, but it
seems to me that even if PM is not enabled, it would still be nice to
register power domains with the kernel and allow devices to attach to
them and only probe the device if they are powered.
Does this sound reasonable or is there a better approach?
Cheers
Jon
next reply other threads:[~2015-11-30 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 16:42 Jon Hunter [this message]
2015-11-30 22:42 ` [RFD] PM_GENERIC_DOMAINS && !PM Rafael J. Wysocki
2015-12-01 15:38 ` Jon Hunter
2015-12-01 16:18 ` Thierry Reding
2015-12-02 1:35 ` Rafael J. Wysocki
[not found] ` <1995321.JkVMSghsar-sKB8Sp2ER+y1GS7QM15AGw@public.gmane.org>
2015-12-02 15:40 ` Thierry Reding
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=565C7C86.7030801@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=geert@linux-m68k.org \
--cc=khilman@linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=ulf.hansson@linaro.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;
as well as URLs for NNTP newsgroup(s).