[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d3e6a2b1-9c8a-7abf-c0c4-d1de578cbfd5@nvidia.com>
Date: Mon, 10 Apr 2017 09:24:28 +0100
From: Jon Hunter <jonathanh@...dia.com>
To: Rajendra Nayak <rnayak@...eaurora.org>,
"Rafael J . Wysocki" <rjw@...ysocki.net>,
Kevin Hilman <khilman@...nel.org>,
Ulf Hansson <ulf.hansson@...aro.org>, <geert@...ux-m68k.org>
CC: <stanimir.varbanov@...aro.org>, <sboyd@...eaurora.org>,
Marek Szyprowski <m.szyprowski@...sung.com>,
<linux-pm@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-tegra@...r.kernel.org>
Subject: Re: [RFC PATCH 4/4] dt-bindings: Add support for devices with
multiple PM domains
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@...dia.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
Powered by blists - more mailing lists