The PCIESYS register space contains a pure clock controller, which
has no system controller register, so this definitely doesn't need
any "syscon" compatible.
As a side note, luckily no devicetree ever added the syscon string
to PCIESYS clock controller node compatibles, so this also resolves
a dtbs_check warning for mt7622.
Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
---
.../bindings/clock/mediatek,mt7622-pciesys.yaml | 10 ++++------
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/Documentation/devicetree/bindings/clock/mediatek,mt7622-pciesys.yaml b/Documentation/devicetree/bindings/clock/mediatek,mt7622-pciesys.yaml
index 9c3913f9092c..c77111d10f90 100644
--- a/Documentation/devicetree/bindings/clock/mediatek,mt7622-pciesys.yaml
+++ b/Documentation/devicetree/bindings/clock/mediatek,mt7622-pciesys.yaml
@@ -14,11 +14,9 @@ maintainers:
properties:
compatible:
- oneOf:
- - items:
- - const: mediatek,mt7622-pciesys
- - const: syscon
- - const: mediatek,mt7629-pciesys
+ enum:
+ - mediatek,mt7622-pciesys
+ - mediatek,mt7629-pciesys
reg:
maxItems: 1
@@ -40,7 +38,7 @@ additionalProperties: false
examples:
- |
clock-controller@1a100800 {
- compatible = "mediatek,mt7622-pciesys", "syscon";
+ compatible = "mediatek,mt7622-pciesys";
reg = <0x1a100800 0x1000>;
#clock-cells = <1>;
#reset-cells = <1>;
--
2.52.0
Quoting AngeloGioacchino Del Regno (2026-01-13 04:00:08) > The PCIESYS register space contains a pure clock controller, which > has no system controller register, so this definitely doesn't need > any "syscon" compatible. > > As a side note, luckily no devicetree ever added the syscon string > to PCIESYS clock controller node compatibles, so this also resolves > a dtbs_check warning for mt7622. > > Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> > --- Applied to clk-next
On 13/1/26 12:00, AngeloGioacchino Del Regno wrote:
> The PCIESYS register space contains a pure clock controller, which
> has no system controller register, so this definitely doesn't need
> any "syscon" compatible.
>
> As a side note, luckily no devicetree ever added the syscon string
> to PCIESYS clock controller node compatibles, so this also resolves
> a dtbs_check warning for mt7622.
>
> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Reviewed-by: Matthias Brugger <matthias.bgg@gmail.com>
> ---
> .../bindings/clock/mediatek,mt7622-pciesys.yaml | 10 ++++------
> 1 file changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/clock/mediatek,mt7622-pciesys.yaml b/Documentation/devicetree/bindings/clock/mediatek,mt7622-pciesys.yaml
> index 9c3913f9092c..c77111d10f90 100644
> --- a/Documentation/devicetree/bindings/clock/mediatek,mt7622-pciesys.yaml
> +++ b/Documentation/devicetree/bindings/clock/mediatek,mt7622-pciesys.yaml
> @@ -14,11 +14,9 @@ maintainers:
>
> properties:
> compatible:
> - oneOf:
> - - items:
> - - const: mediatek,mt7622-pciesys
> - - const: syscon
> - - const: mediatek,mt7629-pciesys
> + enum:
> + - mediatek,mt7622-pciesys
> + - mediatek,mt7629-pciesys
>
> reg:
> maxItems: 1
> @@ -40,7 +38,7 @@ additionalProperties: false
> examples:
> - |
> clock-controller@1a100800 {
> - compatible = "mediatek,mt7622-pciesys", "syscon";
> + compatible = "mediatek,mt7622-pciesys";
> reg = <0x1a100800 0x1000>;
> #clock-cells = <1>;
> #reset-cells = <1>;
On Tue, 13 Jan 2026 12:00:08 +0100, AngeloGioacchino Del Regno wrote: > The PCIESYS register space contains a pure clock controller, which > has no system controller register, so this definitely doesn't need > any "syscon" compatible. > > As a side note, luckily no devicetree ever added the syscon string > to PCIESYS clock controller node compatibles, so this also resolves > a dtbs_check warning for mt7622. > > Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> > --- > .../bindings/clock/mediatek,mt7622-pciesys.yaml | 10 ++++------ > 1 file changed, 4 insertions(+), 6 deletions(-) > Acked-by: Rob Herring (Arm) <robh@kernel.org>
© 2016 - 2026 Red Hat, Inc.