dt-bindings: drop type for operating-points-v2
Commit Message
The type for operating-points-v2 property is coming from dtschema
(/schemas/opp/opp.yaml), so individual bindings can just use simple
"true".
Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
---
This depends on my pull request, at least logically:
https://github.com/devicetree-org/dt-schema/pull/95
Patch could be applied in parallel but only if above PULL is
accepted/correct.
---
.../devicetree/bindings/display/msm/dp-controller.yaml | 3 +--
.../devicetree/bindings/display/tegra/nvidia,tegra20-dc.yaml | 3 +--
.../devicetree/bindings/display/tegra/nvidia,tegra20-dsi.yaml | 3 +--
.../devicetree/bindings/display/tegra/nvidia,tegra20-epp.yaml | 3 +--
.../devicetree/bindings/display/tegra/nvidia,tegra20-gr2d.yaml | 3 +--
.../devicetree/bindings/display/tegra/nvidia,tegra20-gr3d.yaml | 3 +--
.../devicetree/bindings/display/tegra/nvidia,tegra20-hdmi.yaml | 3 +--
.../bindings/display/tegra/nvidia,tegra20-host1x.yaml | 3 +--
.../devicetree/bindings/display/tegra/nvidia,tegra20-mpe.yaml | 3 +--
.../devicetree/bindings/display/tegra/nvidia,tegra20-tvo.yaml | 3 +--
.../devicetree/bindings/display/tegra/nvidia,tegra20-vi.yaml | 3 +--
.../devicetree/bindings/fuse/nvidia,tegra20-fuse.yaml | 3 +--
.../devicetree/bindings/mmc/nvidia,tegra20-sdhci.yaml | 3 +--
Documentation/devicetree/bindings/power/power-domain.yaml | 3 ---
Documentation/devicetree/bindings/pwm/nvidia,tegra20-pwm.yaml | 3 +--
15 files changed, 14 insertions(+), 31 deletions(-)
Comments
On Thu, 19 Jan 2023 14:10:33 +0100, Krzysztof Kozlowski wrote:
> The type for operating-points-v2 property is coming from dtschema
> (/schemas/opp/opp.yaml), so individual bindings can just use simple
> "true".
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>
> ---
>
> This depends on my pull request, at least logically:
> https://github.com/devicetree-org/dt-schema/pull/95
>
> Patch could be applied in parallel but only if above PULL is
> accepted/correct.
> ---
> .../devicetree/bindings/display/msm/dp-controller.yaml | 3 +--
> .../devicetree/bindings/display/tegra/nvidia,tegra20-dc.yaml | 3 +--
> .../devicetree/bindings/display/tegra/nvidia,tegra20-dsi.yaml | 3 +--
> .../devicetree/bindings/display/tegra/nvidia,tegra20-epp.yaml | 3 +--
> .../devicetree/bindings/display/tegra/nvidia,tegra20-gr2d.yaml | 3 +--
> .../devicetree/bindings/display/tegra/nvidia,tegra20-gr3d.yaml | 3 +--
> .../devicetree/bindings/display/tegra/nvidia,tegra20-hdmi.yaml | 3 +--
> .../bindings/display/tegra/nvidia,tegra20-host1x.yaml | 3 +--
> .../devicetree/bindings/display/tegra/nvidia,tegra20-mpe.yaml | 3 +--
> .../devicetree/bindings/display/tegra/nvidia,tegra20-tvo.yaml | 3 +--
> .../devicetree/bindings/display/tegra/nvidia,tegra20-vi.yaml | 3 +--
> .../devicetree/bindings/fuse/nvidia,tegra20-fuse.yaml | 3 +--
> .../devicetree/bindings/mmc/nvidia,tegra20-sdhci.yaml | 3 +--
> Documentation/devicetree/bindings/power/power-domain.yaml | 3 ---
> Documentation/devicetree/bindings/pwm/nvidia,tegra20-pwm.yaml | 3 +--
> 15 files changed, 14 insertions(+), 31 deletions(-)
>
Applied, thanks!
@@ -71,8 +71,7 @@ properties:
items:
- const: dp
- operating-points-v2:
- maxItems: 1
+ operating-points-v2: true
opp-table: true
@@ -59,8 +59,7 @@ properties:
iommus:
maxItems: 1
- operating-points-v2:
- $ref: "/schemas/types.yaml#/definitions/phandle"
+ operating-points-v2: true
power-domains:
items:
@@ -47,8 +47,7 @@ properties:
items:
- const: dsi
- operating-points-v2:
- $ref: "/schemas/types.yaml#/definitions/phandle"
+ operating-points-v2: true
power-domains:
maxItems: 1
@@ -46,8 +46,7 @@ properties:
interconnect-names:
maxItems: 4
- operating-points-v2:
- $ref: "/schemas/types.yaml#/definitions/phandle"
+ operating-points-v2: true
power-domains:
items:
@@ -49,8 +49,7 @@ properties:
interconnect-names:
maxItems: 4
- operating-points-v2:
- $ref: "/schemas/types.yaml#/definitions/phandle"
+ operating-points-v2: true
power-domains:
items:
@@ -51,8 +51,7 @@ properties:
minItems: 4
maxItems: 10
- operating-points-v2:
- $ref: "/schemas/types.yaml#/definitions/phandle"
+ operating-points-v2: true
power-domains:
minItems: 1
@@ -50,8 +50,7 @@ properties:
items:
- const: hdmi
- operating-points-v2:
- $ref: "/schemas/types.yaml#/definitions/phandle"
+ operating-points-v2: true
power-domains:
items:
@@ -90,8 +90,7 @@ properties:
items:
- const: dma-mem # read
- operating-points-v2:
- $ref: "/schemas/types.yaml#/definitions/phandle"
+ operating-points-v2: true
power-domains:
items:
@@ -47,8 +47,7 @@ properties:
interconnect-names:
maxItems: 6
- operating-points-v2:
- $ref: "/schemas/types.yaml#/definitions/phandle"
+ operating-points-v2: true
power-domains:
items:
@@ -30,8 +30,7 @@ properties:
items:
- description: module clock
- operating-points-v2:
- $ref: "/schemas/types.yaml#/definitions/phandle"
+ operating-points-v2: true
power-domains:
items:
@@ -55,8 +55,7 @@ properties:
minItems: 4
maxItems: 5
- operating-points-v2:
- $ref: "/schemas/types.yaml#/definitions/phandle"
+ operating-points-v2: true
power-domains:
items:
@@ -44,8 +44,7 @@ properties:
items:
- const: fuse
- operating-points-v2:
- $ref: "/schemas/types.yaml#/definitions/phandle"
+ operating-points-v2: true
power-domains:
items:
@@ -82,8 +82,7 @@ properties:
iommus:
maxItems: 1
- operating-points-v2:
- $ref: "/schemas/types.yaml#/definitions/phandle"
+ operating-points-v2: true
power-domains:
items:
@@ -43,9 +43,6 @@ properties:
domain would be considered as capable of being powered-on or powered-off.
operating-points-v2:
- $ref: /schemas/types.yaml#/definitions/phandle-array
- items:
- maxItems: 1
description:
Phandles to the OPP tables of power domains provided by a power domain
provider. If the provider provides a single power domain only or all
@@ -63,8 +63,7 @@ properties:
pinctrl-1:
description: configuration for the sleep state
- operating-points-v2:
- $ref: /schemas/types.yaml#/definitions/phandle
+ operating-points-v2: true
power-domains:
items: