| Message ID | 29cb6b892a6e7002d2f6271157a5efa648b0dd9b.1486655917.git-series.maxime.ripard@free-electrons.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
On Thu, Feb 09, 2017 at 05:39:20PM +0100, Maxime Ripard wrote: > The operating-points-v2 binding gives a way to provide the OPP of the GPU. > Let's use it. > > Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com> > --- > Documentation/devicetree/bindings/gpu/arm,mali-utgard.txt | 4 ++++ > 1 file changed, 4 insertions(+), 0 deletions(-) Bindings should not unnecessarily evolve. The h/w does not evolve in this way. This should have been part of the original binding given that it was just added. Acked-by: Rob Herring <robh@kernel.org>
On Thu, Feb 09, 2017 at 05:39:20PM +0100, Maxime Ripard wrote: > The operating-points-v2 binding gives a way to provide the OPP of the GPU. > Let's use it. > > Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com> Applied with Rob Acked-by. Maxime
diff --git a/Documentation/devicetree/bindings/gpu/arm,mali-utgard.txt b/Documentation/devicetree/bindings/gpu/arm,mali-utgard.txt index 88df4a276607..2b6243e730f6 100644 --- a/Documentation/devicetree/bindings/gpu/arm,mali-utgard.txt +++ b/Documentation/devicetree/bindings/gpu/arm,mali-utgard.txt @@ -39,6 +39,10 @@ Optional properties: Memory region to allocate from, as defined in Documentation/devicetree/bindi/reserved-memory/reserved-memory.txt + - operating-points-v2: + Operating Points for the GPU, as defined in + Documentation/devicetree/bindings/opp/opp.txt + Vendor-specific bindings ------------------------
The operating-points-v2 binding gives a way to provide the OPP of the GPU. Let's use it. Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com> --- Documentation/devicetree/bindings/gpu/arm,mali-utgard.txt | 4 ++++ 1 file changed, 4 insertions(+), 0 deletions(-)