Re: [PATCH V2 3/9] OPP: Populate required opp tables from "required-opps" property

On 12 October 2018 at 13:11, Viresh Kumar wrote: > The current implementation works only for the case where a single > phandle is present in the "required-opps" property, while DT allows > multiple phandles to be present there. > > This patch adds new infrastructure to parse all the phandles

Re: [PATCH V2 3/9] OPP: Populate required opp tables from "required-opps" property

On 12 October 2018 at 13:11, Viresh Kumar wrote: > The current implementation works only for the case where a single > phandle is present in the "required-opps" property, while DT allows > multiple phandles to be present there. > > This patch adds new infrastructure to parse all the phandles

[PATCH V2 3/9] OPP: Populate required opp tables from "required-opps" property

The current implementation works only for the case where a single phandle is present in the "required-opps" property, while DT allows multiple phandles to be present there. This patch adds new infrastructure to parse all the phandles present in "required-opps" property and save pointers of the

[PATCH V2 3/9] OPP: Populate required opp tables from "required-opps" property

The current implementation works only for the case where a single phandle is present in the "required-opps" property, while DT allows multiple phandles to be present there. This patch adds new infrastructure to parse all the phandles present in "required-opps" property and save pointers of the