mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Rajendra Nayak <rnayak@codeaurora.org>,
	"Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Kevin Hilman <khilman@kernel.org>,
	Ulf Hansson <ulf.hansson@linaro.org>, <geert@linux-m68k.org>
Cc: <stanimir.varbanov@linaro.org>, <sboyd@codeaurora.org>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	<linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-tegra@vger.kernel.org>
Subject: Re: [RFC PATCH 4/4] dt-bindings: Add support for devices with multiple PM domains
Date: Mon, 10 Apr 2017 09:24:28 +0100	[thread overview]
Message-ID: <d3e6a2b1-9c8a-7abf-c0c4-d1de578cbfd5@nvidia.com> (raw)
In-Reply-To: <3f96256d-0de5-26a2-e656-7912e06806ea@codeaurora.org>


On 10/04/17 05:12, Rajendra Nayak wrote:
> 
> 
> On 03/28/2017 07:44 PM, Jon Hunter wrote:
>> Now that the generic PM domain framework supports consumers that can
>> control multiple PM domains, update the device-tree binding for generic
>> PM domains to state that one or more PM domain is permitted for a
>> device.
>>
>> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
>> ---
>>  Documentation/devicetree/bindings/power/power_domain.txt | 11 +++++++++--
>>  1 file changed, 9 insertions(+), 2 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/power/power_domain.txt b/Documentation/devicetree/bindings/power/power_domain.txt
>> index 723e1ad937da..fb28d37f9e1f 100644
>> --- a/Documentation/devicetree/bindings/power/power_domain.txt
>> +++ b/Documentation/devicetree/bindings/power/power_domain.txt
>> @@ -20,8 +20,15 @@ Required properties:
>>     as specified by device tree binding documentation of particular provider.
>>  
>>  Optional properties:
>> - - power-domains : A phandle and PM domain specifier as defined by bindings of
>> -                   the power controller specified by phandle.
>> + - power-domains : An array of one or more PM domain specifiers (defined by the
>> +		   bindings of the PM domain provider) for each PM domain that
>> +		   is required by the device.
>> + - power-domain-names: A list of strings of PM domain names. The list must have
>> +                       a name for each PM domain specifier in the
>> +		       'power-domains' property and these names must be unique
>> +		       within the context of this property. The names must be
>> +		       indexed so that the first name corresponds to the first
>> +		       PM domain specifier and so on.
> 
> These bindings are for power-domain providers. We also need to update the bindings
> for the consumers (look further down in the same file)

Thanks, will take a look at that.

Cheers
Jon

-- 
nvpublic

  reply	other threads:[~2017-04-10  8:25 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28 14:13 [RFC PATCH 0/4] PM / Domains: Add support for explicit control of " Jon Hunter
2017-03-28 14:14 ` [RFC PATCH 1/4] PM / Domains: Prepare for supporting explicit PM domain control Jon Hunter
2017-03-28 14:14 ` [RFC PATCH 2/4] PM / Domains: Add support for explicit control of PM domains Jon Hunter
2017-04-10  4:09   ` Rajendra Nayak
2017-04-10  8:24     ` Jon Hunter
2017-04-10 10:02       ` Rajendra Nayak
2017-04-10 19:48         ` Jon Hunter
2017-03-28 14:14 ` [RFC PATCH 3/4] PM / Domains: Add OF helpers for getting " Jon Hunter
2017-03-28 14:14 ` [RFC PATCH 4/4] dt-bindings: Add support for devices with multiple " Jon Hunter
2017-04-10  4:12   ` Rajendra Nayak
2017-04-10  8:24     ` Jon Hunter [this message]
2017-04-25 11:13 ` [RFC PATCH 0/4] PM / Domains: Add support for explicit control of " Jon Hunter
2017-04-25 19:34   ` Ulf Hansson
2017-04-25 21:17     ` Rafael J. Wysocki
2017-05-02 10:10       ` Jon Hunter
2017-05-02 21:51         ` Rafael J. Wysocki
2017-05-03  8:12           ` Ulf Hansson
2017-05-03  8:32             ` Jon Hunter
2017-05-03 13:43               ` Ulf Hansson
2017-05-03 14:57                 ` Jon Hunter
2017-05-03 17:12                   ` Ulf Hansson
2017-05-04  8:44                     ` Jon Hunter
2017-05-30  3:41                       ` Rajendra Nayak
2017-10-09 16:36                         ` Todor Tomov
2017-10-10  9:13                           ` Jon Hunter
2017-05-03  8:12           ` Jon Hunter
2017-04-26  8:06     ` Geert Uytterhoeven
2017-04-26  9:04       ` Ulf Hansson
2017-04-26  9:17         ` Geert Uytterhoeven
2017-04-26  9:55           ` Ulf Hansson
2017-05-03  6:43             ` Geert Uytterhoeven
2017-05-03  8:54               ` 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=d3e6a2b1-9c8a-7abf-c0c4-d1de578cbfd5@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=geert@linux-m68k.org \
    --cc=khilman@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=rjw@rjwysocki.net \
    --cc=rnayak@codeaurora.org \
    --cc=sboyd@codeaurora.org \
    --cc=stanimir.varbanov@linaro.org \
    --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

all inboxes | Powered by JetHome®