| Message ID | 1490710443-27425-5-git-send-email-jonathanh@nvidia.com (mailing list archive) |
|---|---|
| State | RFC, archived |
| Headers | show |
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) > Some power domains might be powered from another power domain (or have > other hardware specific dependencies). For representing such dependency > a standard PM domain consumer binding is used. When provided, all 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@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
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. Some power domains might be powered from another power domain (or have other hardware specific dependencies). For representing such dependency a standard PM domain consumer binding is used. When provided, all domains
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(-)