dt-bindings: power: Fix path to power-domain.txt bindings
Subsystems (17)
Krzysztof Kozlowski
maintainerPATCH 1/1 dt-bindings: power: Fix path to power-domain.txt bindings
With split of power domain controller bindings to power-domain.yaml, the consumer part was renamed to power-domain.txt. Update the references in other bindings.
--- Documentation/devicetree/bindings/clock/clk-exynos-audss.txt | 2 +- Documentation/devicetree/bindings/clock/exynos5433-clock.txt | 2 +- .../devicetree/bindings/clock/renesas,r8a7778-cpg-clocks.txt | 2 +- .../devicetree/bindings/clock/renesas,r8a7779-cpg-clocks.txt | 2 +- .../bindings/clock/renesas,rcar-gen2-cpg-clocks.txt | 2 +- .../devicetree/bindings/clock/renesas,rz-cpg-clocks.txt | 2 +- .../devicetree/bindings/display/etnaviv/etnaviv-drm.txt | 2 +- Documentation/devicetree/bindings/display/msm/dpu.txt | 2 +- Documentation/devicetree/bindings/display/msm/mdp5.txt | 2 +- Documentation/devicetree/bindings/dsp/fsl,dsp.yaml | 2 +- Documentation/devicetree/bindings/media/imx7-mipi-csi2.txt | 2 +- .../devicetree/bindings/media/mediatek-jpeg-decoder.txt | 2 +- Documentation/devicetree/bindings/media/mediatek-mdp.txt | 2 +- Documentation/devicetree/bindings/opp/qcom-nvmem-cpufreq.txt | 2 +- Documentation/devicetree/bindings/pci/pci-keystone.txt | 2 +- Documentation/devicetree/bindings/phy/ti,phy-am654-serdes.txt | 2 +- Documentation/devicetree/bindings/power/qcom,rpmpd.txt | 2 +- Documentation/devicetree/bindings/power/renesas,rcar-sysc.txt | 2 +- .../devicetree/bindings/usb/nvidia,tegra124-xusb.txt | 4 ++-- 19 files changed, 20 insertions(+), 20 deletions(-)
Documentation/devicetree/bindings/clock/clk-exynos-audss.txt +1 -1
@@ -36,7 +36,7 @@ Required Properties: Optional Properties: - power-domains: a phandle to respective power domain node as described by - generic PM domain bindings (see power/power_domain.txt for more + generic PM domain bindings (see power/power-domain.txt for more information). The following is the list of clocks generated by the controller. Each clock is
Documentation/devicetree/bindings/clock/exynos5433-clock.txt +1 -1
@@ -178,7 +178,7 @@ Required Properties: Optional properties: - power-domains: a phandle to respective power domain node as described by - generic PM domain bindings (see power/power_domain.txt for more + generic PM domain bindings (see power/power-domain.txt for more information). Each clock is assigned an identifier and client nodes can use this identifier
Documentation/devicetree/bindings/clock/renesas,r8a7778-cpg-clocks.txt +1 -1
@@ -17,7 +17,7 @@ Required Properties: SoC devices that are part of the CPG/MSTP Clock Domain and can be power-managed through an MSTP clock should refer to the CPG device node in their "power-domains" property, as documented by the generic PM domain bindings in -Documentation/devicetree/bindings/power/power_domain.txt. +Documentation/devicetree/bindings/power/power-domain.txt. Examples
Documentation/devicetree/bindings/clock/renesas,r8a7779-cpg-clocks.txt +1 -1
@@ -19,7 +19,7 @@ Required Properties: SoC devices that are part of the CPG/MSTP Clock Domain and can be power-managed through an MSTP clock should refer to the CPG device node in their "power-domains" property, as documented by the generic PM domain bindings in -Documentation/devicetree/bindings/power/power_domain.txt. +Documentation/devicetree/bindings/power/power-domain.txt. Examples
Documentation/devicetree/bindings/clock/renesas,rcar-gen2-cpg-clocks.txt +1 -1
@@ -28,7 +28,7 @@ Required Properties: SoC devices that are part of the CPG/MSTP Clock Domain and can be power-managed through an MSTP clock should refer to the CPG device node in their "power-domains" property, as documented by the generic PM domain bindings in -Documentation/devicetree/bindings/power/power_domain.txt. +Documentation/devicetree/bindings/power/power-domain.txt. Examples
Documentation/devicetree/bindings/clock/renesas,rz-cpg-clocks.txt +1 -1
@@ -21,7 +21,7 @@ Required Properties: SoC devices that are part of the CPG/MSTP Clock Domain and can be power-managed through an MSTP clock should refer to the CPG device node in their "power-domains" property, as documented by the generic PM domain bindings in -Documentation/devicetree/bindings/power/power_domain.txt. +Documentation/devicetree/bindings/power/power-domain.txt. Examples
Documentation/devicetree/bindings/display/etnaviv/etnaviv-drm.txt +1 -1
@@ -20,7 +20,7 @@ Required properties: Optional properties: - power-domains: a power domain consumer specifier according to - Documentation/devicetree/bindings/power/power_domain.txt + Documentation/devicetree/bindings/power/power-domain.txt - #cooling-cells: : If used as a cooling device, must be <2> example:
Documentation/devicetree/bindings/display/msm/dpu.txt +1 -1
@@ -13,7 +13,7 @@ Required properties: - reg-names: register region names. The following region is required: * "mdss" - power-domains: a power domain consumer specifier according to - Documentation/devicetree/bindings/power/power_domain.txt + Documentation/devicetree/bindings/power/power-domain.txt - clocks: list of clock specifiers for clocks needed by the device. - clock-names: device clock names, must be in same order as clocks property. The following clocks are required:
Documentation/devicetree/bindings/display/msm/mdp5.txt +1 -1
@@ -19,7 +19,7 @@ Required properties: - #interrupt-cells: specifies the number of cells needed to encode an interrupt source, should be 1. - power-domains: a power domain consumer specifier according to - Documentation/devicetree/bindings/power/power_domain.txt + Documentation/devicetree/bindings/power/power-domain.txt - clocks: device clocks. See ../clocks/clock-bindings.txt for details. - clock-names: the following clocks are required. * "iface"
Documentation/devicetree/bindings/dsp/fsl,dsp.yaml +1 -1
@@ -36,7 +36,7 @@ properties: power-domains: description: List of phandle and PM domain specifier as documented in - Documentation/devicetree/bindings/power/power_domain.txt + Documentation/devicetree/bindings/power/power-domain.txt maxItems: 4 mboxes:
Documentation/devicetree/bindings/media/imx7-mipi-csi2.txt +1 -1
@@ -17,7 +17,7 @@ Required properties: - clock-names : must contain "pclk", "wrap" and "phy" entries, matching entries in the clock property; - power-domains : a phandle to the power domain, see - Documentation/devicetree/bindings/power/power_domain.txt for details. + Documentation/devicetree/bindings/power/power-domain.txt for details. - reset-names : should include following entry "mrst"; - resets : a list of phandle, should contain reset entry of reset-names;
Documentation/devicetree/bindings/media/mediatek-jpeg-decoder.txt +1 -1
@@ -14,7 +14,7 @@ Required properties: Documentation/devicetree/bindings/clock/clock-bindings.txt for details. - clock-names: must contain "jpgdec-smi" and "jpgdec". - power-domains: a phandle to the power domain, see - Documentation/devicetree/bindings/power/power_domain.txt for details. + Documentation/devicetree/bindings/power/power-domain.txt for details. - mediatek,larb: must contain the local arbiters in the current Socs, see Documentation/devicetree/bindings/memory-controllers/mediatek,smi-larb.txt for details.
Documentation/devicetree/bindings/media/mediatek-mdp.txt +1 -1
@@ -17,7 +17,7 @@ Required properties (all function blocks, child node): - clocks: device clocks, see Documentation/devicetree/bindings/clock/clock-bindings.txt for details. - power-domains: a phandle to the power domain, see - Documentation/devicetree/bindings/power/power_domain.txt for details. + Documentation/devicetree/bindings/power/power-domain.txt for details. Required properties (DMA function blocks, child node): - compatible: Should be one of
Documentation/devicetree/bindings/opp/qcom-nvmem-cpufreq.txt +1 -1
@@ -27,7 +27,7 @@ In 'cpu' nodes: - power-domains: A phandle pointing to the PM domain specifier which provides the performance states available for active state management. Please refer to the power-domains bindings - Documentation/devicetree/bindings/power/power_domain.txt + Documentation/devicetree/bindings/power/power-domain.txt and also examples below. - power-domain-names: Should be - 'cpr' for qcs404.
Documentation/devicetree/bindings/pci/pci-keystone.txt +1 -1
@@ -88,7 +88,7 @@ num-ob-windows: As specified in num-lanes: As specified in Documentation/devicetree/bindings/pci/designware-pcie.txt power-domains: As documented by the generic PM domain bindings in - Documentation/devicetree/bindings/power/power_domain.txt. + Documentation/devicetree/bindings/power/power-domain.txt. ti,syscon-pcie-mode: phandle to the device control module required to configure PCI in either RC mode or EP mode.
Documentation/devicetree/bindings/phy/ti,phy-am654-serdes.txt +1 -1
@@ -17,7 +17,7 @@ Required properties: 1 - PCIe0 Lane1 2 - ICSS2 SGMII Lane1 - power-domains: As documented by the generic PM domain bindings in - Documentation/devicetree/bindings/power/power_domain.txt. + Documentation/devicetree/bindings/power/power-domain.txt. - clocks: List of clock-specifiers representing the input to the SERDES. Should have 3 items representing the left input clock, external reference clock and right input clock in that order.
Documentation/devicetree/bindings/power/qcom,rpmpd.txt +1 -1
@@ -13,7 +13,7 @@ Required Properties: - #power-domain-cells: number of cells in Power domain specifier must be 1. - operating-points-v2: Phandle to the OPP table for the Power domain. - Refer to Documentation/devicetree/bindings/power/power_domain.txt + Refer to Documentation/devicetree/bindings/power/power-domain.txt and Documentation/devicetree/bindings/opp/opp.txt for more details Refer to <dt-bindings/power/qcom-rpmpd.h> for the level values for
Documentation/devicetree/bindings/power/renesas,rcar-sysc.txt +1 -1
@@ -44,7 +44,7 @@ Example: Devices residing in a power area must refer to that power area, as documented by the generic PM domain bindings in -Documentation/devicetree/bindings/power/power_domain.txt. +Documentation/devicetree/bindings/power/power-domain.txt. Required properties: - power-domains: A phandle and symbolic PM domain specifier, as defined in
Documentation/devicetree/bindings/usb/nvidia,tegra124-xusb.txt +2 -2
@@ -64,12 +64,12 @@ For Tegra210: For Tegra210 and Tegra186: - power-domains: A list of PM domain specifiers that reference each power-domain used by the xHCI controller. This list must comprise of a specifier for the - XUSBA and XUSBC power-domains. See ../power/power_domain.txt and + XUSBA and XUSBC power-domains. See ../power/power-domain.txt and ../arm/tegra/nvidia,tegra20-pmc.txt for details. - power-domain-names: A list of names that represent each of the specifiers in the 'power-domains' property. Must include 'xusb_ss' and 'xusb_host' which represent the power-domains XUSBA and XUSBC, respectively. See - ../power/power_domain.txt for details. + ../power/power-domain.txt for details. Optional properties: --------------------
Signature · 1 line
2.17.1
Quoted 8 lines · Krzysztof Kozlowski
With split of power domain controller bindings to
power-domain.yaml, the consumer part was renamed to power-domain.txt. Update the references in other bindings.Reported-by Geert Uytterhoeven <[email protected]>Fixes abb4805e343a ("dt-bindings: power: Convert Samsung Exynos Power Domain bindings to json-schema")Signed-off-by Krzysztof Kozlowski <[email protected]>
Oh, I didn't noticed that the patch for conversion got queued up. From what tree?
And why was the file renamed to power-domain.txt?
Kind regards
Uffe
Quoted 278 lines
--- Documentation/devicetree/bindings/clock/clk-exynos-audss.txt | 2 +- Documentation/devicetree/bindings/clock/exynos5433-clock.txt | 2 +- .../devicetree/bindings/clock/renesas,r8a7778-cpg-clocks.txt | 2 +- .../devicetree/bindings/clock/renesas,r8a7779-cpg-clocks.txt | 2 +- .../bindings/clock/renesas,rcar-gen2-cpg-clocks.txt | 2 +- .../devicetree/bindings/clock/renesas,rz-cpg-clocks.txt | 2 +- .../devicetree/bindings/display/etnaviv/etnaviv-drm.txt | 2 +- Documentation/devicetree/bindings/display/msm/dpu.txt | 2 +- Documentation/devicetree/bindings/display/msm/mdp5.txt | 2 +- Documentation/devicetree/bindings/dsp/fsl,dsp.yaml | 2 +- Documentation/devicetree/bindings/media/imx7-mipi-csi2.txt | 2 +- .../devicetree/bindings/media/mediatek-jpeg-decoder.txt | 2 +- Documentation/devicetree/bindings/media/mediatek-mdp.txt | 2 +- Documentation/devicetree/bindings/opp/qcom-nvmem-cpufreq.txt | 2 +- Documentation/devicetree/bindings/pci/pci-keystone.txt | 2 +- Documentation/devicetree/bindings/phy/ti,phy-am654-serdes.txt | 2 +- Documentation/devicetree/bindings/power/qcom,rpmpd.txt | 2 +- Documentation/devicetree/bindings/power/renesas,rcar-sysc.txt | 2 +- .../devicetree/bindings/usb/nvidia,tegra124-xusb.txt | 4 ++-- 19 files changed, 20 insertions(+), 20 deletions(-)Documentation/devicetree/bindings/clock/clk-exynos-audss.txt +1
-1@@ -36,7 +36,7 @@ Required Properties: Optional Properties: - power-domains: a phandle to respective power domain node as described by - generic PM domain bindings (see power/power_domain.txt for more + generic PM domain bindings (see power/power-domain.txt for more information). The following is the list of clocks generated by the controller. Each clock isDocumentation/devicetree/bindings/clock/exynos5433-clock.txt +1
-1@@ -178,7 +178,7 @@ Required Properties: Optional properties: - power-domains: a phandle to respective power domain node as described by - generic PM domain bindings (see power/power_domain.txt for more + generic PM domain bindings (see power/power-domain.txt for more information). Each clock is assigned an identifier and client nodes can use this identifierDocumentation/devicetree/bindings/clock/renesas,r8a7778-cpg-clocks.txt +1
-1@@ -17,7 +17,7 @@ Required Properties: SoC devices that are part of the CPG/MSTP Clock Domain and can be power-managed through an MSTP clock should refer to the CPG device node in their "power-domains" property, as documented by the generic PM domain bindings in -Documentation/devicetree/bindings/power/power_domain.txt. +Documentation/devicetree/bindings/power/power-domain.txt. ExamplesDocumentation/devicetree/bindings/clock/renesas,r8a7779-cpg-clocks.txt +1
-1@@ -19,7 +19,7 @@ Required Properties: SoC devices that are part of the CPG/MSTP Clock Domain and can be power-managed through an MSTP clock should refer to the CPG device node in their "power-domains" property, as documented by the generic PM domain bindings in -Documentation/devicetree/bindings/power/power_domain.txt. +Documentation/devicetree/bindings/power/power-domain.txt. ExamplesDocumentation/devicetree/bindings/clock/renesas,rcar-gen2-cpg-clocks.txt +1
-1@@ -28,7 +28,7 @@ Required Properties: SoC devices that are part of the CPG/MSTP Clock Domain and can be power-managed through an MSTP clock should refer to the CPG device node in their "power-domains" property, as documented by the generic PM domain bindings in -Documentation/devicetree/bindings/power/power_domain.txt. +Documentation/devicetree/bindings/power/power-domain.txt. ExamplesDocumentation/devicetree/bindings/clock/renesas,rz-cpg-clocks.txt +1
-1@@ -21,7 +21,7 @@ Required Properties: SoC devices that are part of the CPG/MSTP Clock Domain and can be power-managed through an MSTP clock should refer to the CPG device node in their "power-domains" property, as documented by the generic PM domain bindings in -Documentation/devicetree/bindings/power/power_domain.txt. +Documentation/devicetree/bindings/power/power-domain.txt. ExamplesDocumentation/devicetree/bindings/display/etnaviv/etnaviv-drm.txt +1
-1@@ -20,7 +20,7 @@ Required properties: Optional properties: - power-domains: a power domain consumer specifier according to - Documentation/devicetree/bindings/power/power_domain.txt + Documentation/devicetree/bindings/power/power-domain.txt - #cooling-cells: : If used as a cooling device, must be <2> example:Documentation/devicetree/bindings/display/msm/dpu.txt +1
-1@@ -13,7 +13,7 @@ Required properties: - reg-names: register region names. The following region is required: * "mdss" - power-domains: a power domain consumer specifier according to - Documentation/devicetree/bindings/power/power_domain.txt + Documentation/devicetree/bindings/power/power-domain.txt - clocks: list of clock specifiers for clocks needed by the device. - clock-names: device clock names, must be in same order as clocks property. The following clocks are required:Documentation/devicetree/bindings/display/msm/mdp5.txt +1
-1@@ -19,7 +19,7 @@ Required properties: - #interrupt-cells: specifies the number of cells needed to encode an interrupt source, should be 1. - power-domains: a power domain consumer specifier according to - Documentation/devicetree/bindings/power/power_domain.txt + Documentation/devicetree/bindings/power/power-domain.txt - clocks: device clocks. See ../clocks/clock-bindings.txt for details. - clock-names: the following clocks are required. * "iface"Documentation/devicetree/bindings/dsp/fsl,dsp.yaml +1
-1@@ -36,7 +36,7 @@ properties: power-domains: description: List of phandle and PM domain specifier as documented in - Documentation/devicetree/bindings/power/power_domain.txt + Documentation/devicetree/bindings/power/power-domain.txt maxItems: 4 mboxes:Documentation/devicetree/bindings/media/imx7-mipi-csi2.txt +1
-1@@ -17,7 +17,7 @@ Required properties: - clock-names : must contain "pclk", "wrap" and "phy" entries, matching entries in the clock property; - power-domains : a phandle to the power domain, see - Documentation/devicetree/bindings/power/power_domain.txt for details. + Documentation/devicetree/bindings/power/power-domain.txt for details. - reset-names : should include following entry "mrst"; - resets : a list of phandle, should contain reset entry of reset-names;Documentation/devicetree/bindings/media/mediatek-jpeg-decoder.txt +1
-1@@ -14,7 +14,7 @@ Required properties: Documentation/devicetree/bindings/clock/clock-bindings.txt for details. - clock-names: must contain "jpgdec-smi" and "jpgdec". - power-domains: a phandle to the power domain, see - Documentation/devicetree/bindings/power/power_domain.txt for details. + Documentation/devicetree/bindings/power/power-domain.txt for details. - mediatek,larb: must contain the local arbiters in the current Socs, see Documentation/devicetree/bindings/memory-controllers/mediatek,smi-larb.txt for details.Documentation/devicetree/bindings/media/mediatek-mdp.txt +1
-1@@ -17,7 +17,7 @@ Required properties (all function blocks, child node): - clocks: device clocks, see Documentation/devicetree/bindings/clock/clock-bindings.txt for details. - power-domains: a phandle to the power domain, see - Documentation/devicetree/bindings/power/power_domain.txt for details. + Documentation/devicetree/bindings/power/power-domain.txt for details. Required properties (DMA function blocks, child node): - compatible: Should be one ofDocumentation/devicetree/bindings/opp/qcom-nvmem-cpufreq.txt +1
-1@@ -27,7 +27,7 @@ In 'cpu' nodes: - power-domains: A phandle pointing to the PM domain specifier which provides the performance states available for active state management. Please refer to the power-domains bindings - Documentation/devicetree/bindings/power/power_domain.txt + Documentation/devicetree/bindings/power/power-domain.txt and also examples below. - power-domain-names: Should be - 'cpr' for qcs404.Documentation/devicetree/bindings/pci/pci-keystone.txt +1
-1@@ -88,7 +88,7 @@ num-ob-windows: As specified in num-lanes: As specified in Documentation/devicetree/bindings/pci/designware-pcie.txt power-domains: As documented by the generic PM domain bindings in - Documentation/devicetree/bindings/power/power_domain.txt. + Documentation/devicetree/bindings/power/power-domain.txt. ti,syscon-pcie-mode: phandle to the device control module required to configure PCI in either RC mode or EP mode.Documentation/devicetree/bindings/phy/ti,phy-am654-serdes.txt +1
-1@@ -17,7 +17,7 @@ Required properties: 1 - PCIe0 Lane1 2 - ICSS2 SGMII Lane1 - power-domains: As documented by the generic PM domain bindings in - Documentation/devicetree/bindings/power/power_domain.txt. + Documentation/devicetree/bindings/power/power-domain.txt. - clocks: List of clock-specifiers representing the input to the SERDES. Should have 3 items representing the left input clock, external reference clock and right input clock in that order.Documentation/devicetree/bindings/power/qcom,rpmpd.txt +1
-1@@ -13,7 +13,7 @@ Required Properties: - #power-domain-cells: number of cells in Power domain specifier must be 1. - operating-points-v2: Phandle to the OPP table for the Power domain. - Refer to Documentation/devicetree/bindings/power/power_domain.txt + Refer to Documentation/devicetree/bindings/power/power-domain.txt and Documentation/devicetree/bindings/opp/opp.txt for more details Refer to <dt-bindings/power/qcom-rpmpd.h> for the level values forDocumentation/devicetree/bindings/power/renesas,rcar-sysc.txt +1
-1@@ -44,7 +44,7 @@ Example: Devices residing in a power area must refer to that power area, as documented by the generic PM domain bindings in -Documentation/devicetree/bindings/power/power_domain.txt. +Documentation/devicetree/bindings/power/power-domain.txt. Required properties: - power-domains: A phandle and symbolic PM domain specifier, as defined inDocumentation/devicetree/bindings/usb/nvidia,tegra124-xusb.txt +2
-3@@ -64,12 +64,12 @@ For Tegra210: For Tegra210 and Tegra186: - power-domains: A list of PM domain specifiers that reference each power-domain used by the xHCI controller. This list must comprise of a specifier for the - XUSBA and XUSBC power-domains. See ../power/power_domain.txt and + XUSBA and XUSBC power-domains. See ../power/power-domain.txt and ../arm/tegra/nvidia,tegra20-pmc.txt for details. - power-domain-names: A list of names that represent each of the specifiers in the 'power-domains' property. Must include 'xusb_ss' and 'xusb_host' which represent the power-domains XUSBA and XUSBC, respectively. See - ../power/power_domain.txt for details. + ../power/power-domain.txt for details. Optional properties: -------------------- --2.17.1
Hi Krzysztof,
Quoted 7 lines · Krzysztof Kozlowski
With split of power domain controller bindings to
power-domain.yaml, the consumer part was renamed to power-domain.txt. Update the references in other bindings.Reported-by Geert Uytterhoeven <[email protected]>Fixes abb4805e343a ("dt-bindings: power: Convert Samsung Exynos Power Domain bindings to json-schema")Signed-off-by Krzysztof Kozlowski <[email protected]>
Thanks for your patch!
Quoted 1 line
.../bindings/clock/renesas,rcar-gen2-cpg-clocks.txt | 2 +-
Please note this file is no longer present in next. But robh/for-next still has it.
Gr{oetje,eeting}s,
Geert
Signature · 9 lines
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected] In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds _______________________________________________ Freedreno mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/freedreno
Rob Herring
maintainerQuoted 21 lines · Krzysztof Kozlowski
With split of power domain controller bindings to
power-domain.yaml, the consumer part was renamed to power-domain.txt. Update the references in other bindings.Reported-by Geert Uytterhoeven <[email protected]>Fixes abb4805e343a ("dt-bindings: power: Convert Samsung Exynos Power Domain bindings to json-schema")Signed-off-by Krzysztof Kozlowski <[email protected]>--- Documentation/devicetree/bindings/clock/clk-exynos-audss.txt | 2 +- Documentation/devicetree/bindings/clock/exynos5433-clock.txt | 2 +- .../devicetree/bindings/clock/renesas,r8a7778-cpg-clocks.txt | 2 +- .../devicetree/bindings/clock/renesas,r8a7779-cpg-clocks.txt | 2 +- .../bindings/clock/renesas,rcar-gen2-cpg-clocks.txt | 2 +- .../devicetree/bindings/clock/renesas,rz-cpg-clocks.txt | 2 +- .../devicetree/bindings/display/etnaviv/etnaviv-drm.txt | 2 +- Documentation/devicetree/bindings/display/msm/dpu.txt | 2 +- Documentation/devicetree/bindings/display/msm/mdp5.txt | 2 +- Documentation/devicetree/bindings/dsp/fsl,dsp.yaml | 2 +- Documentation/devicetree/bindings/media/imx7-mipi-csi2.txt | 2 +- .../devicetree/bindings/media/mediatek-jpeg-decoder.txt | 2 +-
Quoted 8 lines
Documentation/devicetree/bindings/media/mediatek-mdp.txt | 2 +- Documentation/devicetree/bindings/opp/qcom-nvmem-cpufreq.txt | 2 +- Documentation/devicetree/bindings/pci/pci-keystone.txt | 2 +- Documentation/devicetree/bindings/phy/ti,phy-am654-serdes.txt | 2 +- Documentation/devicetree/bindings/power/qcom,rpmpd.txt | 2 +- Documentation/devicetree/bindings/power/renesas,rcar-sysc.txt | 2 +- .../devicetree/bindings/usb/nvidia,tegra124-xusb.txt | 4 ++-- 19 files changed, 20 insertions(+), 20 deletions(-)
Please no. Can you just undo the renaming back to power_domain.txt
Rob
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Krzysztof Kozlowski
maintainerQuoted 32 lines · Rob Herring
Quoted 21 lines · Krzysztof Kozlowski
With split of power domain controller bindings to
power-domain.yaml, the consumer part was renamed to power-domain.txt. Update the references in other bindings.Reported-by Geert Uytterhoeven <[email protected]>Fixes abb4805e343a ("dt-bindings: power: Convert Samsung Exynos Power Domain bindings to json-schema")Signed-off-by Krzysztof Kozlowski <[email protected]>--- Documentation/devicetree/bindings/clock/clk-exynos-audss.txt | 2 +- Documentation/devicetree/bindings/clock/exynos5433-clock.txt | 2 +- .../devicetree/bindings/clock/renesas,r8a7778-cpg-clocks.txt | 2 +- .../devicetree/bindings/clock/renesas,r8a7779-cpg-clocks.txt | 2 +- .../bindings/clock/renesas,rcar-gen2-cpg-clocks.txt | 2 +- .../devicetree/bindings/clock/renesas,rz-cpg-clocks.txt | 2 +- .../devicetree/bindings/display/etnaviv/etnaviv-drm.txt | 2 +- Documentation/devicetree/bindings/display/msm/dpu.txt | 2 +- Documentation/devicetree/bindings/display/msm/mdp5.txt | 2 +- Documentation/devicetree/bindings/dsp/fsl,dsp.yaml | 2 +- Documentation/devicetree/bindings/media/imx7-mipi-csi2.txt | 2 +- .../devicetree/bindings/media/mediatek-jpeg-decoder.txt | 2 +-Quoted 8 lines
Documentation/devicetree/bindings/media/mediatek-mdp.txt | 2 +- Documentation/devicetree/bindings/opp/qcom-nvmem-cpufreq.txt | 2 +- Documentation/devicetree/bindings/pci/pci-keystone.txt | 2 +- Documentation/devicetree/bindings/phy/ti,phy-am654-serdes.txt | 2 +- Documentation/devicetree/bindings/power/qcom,rpmpd.txt | 2 +- Documentation/devicetree/bindings/power/renesas,rcar-sysc.txt | 2 +- .../devicetree/bindings/usb/nvidia,tegra124-xusb.txt | 4 ++-- 19 files changed, 20 insertions(+), 20 deletions(-)
Quoted 1 line
Please no. Can you just undo the renaming back to power_domain.txt
The renaming was done to make it consistent with yaml and other bindings but indeed it creates some churn... I'll send rename-undo then.
Best regards,
Krzysztof
_______________________________________________
Freedreno mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/freedreno