From: Jon Hunter <jonathanh@nvidia.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Ulf Hansson <ulf.hansson@linaro.org>,
Kevin Hilman <khilman@kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: [PATCH V2] PM / Domains: Return -EPROBE_DEFER if we fail to init or turn-on domain
Date: Thu, 6 Aug 2015 12:46:23 +0100 [thread overview]
Message-ID: <55C3490F.20307@nvidia.com> (raw)
In-Reply-To: <CAMuHMdV7AMQD564AgUSACAJFTdqtmMxU9yoefuZ2CXEEhR57RQ@mail.gmail.com>
Hi Geert,
On 06/08/15 12:26, Geert Uytterhoeven wrote:
> Hi Jon,
>
> On Thu, Aug 6, 2015 at 11:26 AM, Jon Hunter <jonathanh@nvidia.com> wrote:
>
> [...]
>
>>>>>>>>> This causes a regression for platforms where:
>>>>>>>>> 1. DT describes the hardware power domains, and
>>>>>>>>> 2. The boot loader or reset state has enabled all power domains, and
>>>>>>>>> 3. Linux doesn't have a driver for the power controller yet.
>>>>>>>>>
>>>>>>>>> Before, devices for which the PM domain couldn't be found just probed and
>>>>>>>>> worked, Now, these devices don't probe anymore, and the kernel fails to boot.
>
> [...]
>
>> It still sounds to me that the nodes should be disabled/removed from the
>> dtb. Having a dynamic way to do this would be useful, I can see.
>
> I had a quick look, and it already seem to exist..
> Hence on platforms not implementing power controllers yet, the early platform
> code could do:
>
> struct device_node *np;
> for_each_node_with_property(dn, "power-domains")
> of_remove_property(np, "power-domains");
>
> Haven't tested that yet, though...
Yes that could be an option, however, it would mean doing this type of
thing for various types of nodes. You mentioned dma was another case.
> Heck, even the core power domain code could do that, if
> CONFIG_PM_GENERIC_DOMAINS=n ;-)
Yes that's true. Hopefully it would WARN too ;-)
Jon
-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information. Any unauthorized review, use, disclosure or distribution
is prohibited. If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
next prev parent reply other threads:[~2015-08-06 11:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 9:20 [PATCH V2] PM / Domains: Return -EPROBE_DEFER if we fail to init or turn-on domain Jon Hunter
2015-08-01 0:12 ` Rafael J. Wysocki
2015-08-04 13:03 ` Geert Uytterhoeven
2015-08-04 13:57 ` Jon Hunter
2015-08-05 14:06 ` Geert Uytterhoeven
2015-08-05 23:59 ` Rafael J. Wysocki
2015-08-06 7:42 ` Jon Hunter
2015-08-06 8:28 ` Jon Hunter
2015-08-06 8:46 ` Geert Uytterhoeven
2015-08-06 9:26 ` Jon Hunter
2015-08-06 11:26 ` Geert Uytterhoeven
2015-08-06 11:46 ` Jon Hunter [this message]
2015-08-06 12:10 ` Geert Uytterhoeven
2015-08-06 8:08 ` Jon Hunter
2015-08-06 8:48 ` Geert Uytterhoeven
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=55C3490F.20307@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=geert@linux-m68k.org \
--cc=khilman@kernel.org \
--cc=linux-pm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.