6.16rc1 dts-bindings check fails

6.16rc1 dts-bindings check fails

[Ricardo Ribalda]

Hi

Media-CI is reporting some dts binding errors:

/builds/linux-media/users/ribalda/Documentation/devicetree/bindings/crypto/marvell,orion-crypto.yaml:
properties:reg-names:items:1: 'deprecated' is not one of ['const',
'description', 'enum', 'not', 'pattern']
from schema $id: http://devicetree.org/meta-schemas/string-array.yaml#
/builds/linux-media/users/ribalda/Documentation/devicetree/bindings/pci/marvell,armada8k-pcie.example.dtb:
pcie@f2600000: interrupts: [[0], [32], [4]] is too long
from schema $id: http://devicetree.org/schemas/pci/marvell,armada8k-pcie.yaml#

When I test your  for-next tree I have the same issue:
https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git/log/Documentation/devicetree/bindings/crypto?h=for-next

They do not affect media drivers so right now I am just ignoring them,
but I wanted to know if they are under your radar.


Regards!


-- 
Ricardo Ribalda

Re: 6.16rc1 dts-bindings check fails

[Krzysztof Kozlowski]

On 10/06/2025 18:11, Ricardo Ribalda wrote:
> Hi
> 
> Media-CI is reporting some dts binding errors:

Every builder of linux-next sees this, it's not specific to media.

> 
> /builds/linux-media/users/ribalda/Documentation/devicetree/bindings/crypto/marvell,orion-crypto.yaml:
> properties:reg-names:items:1: 'deprecated' is not one of ['const',
> 'description', 'enum', 'not', 'pattern']
> from schema $id: http://devicetree.org/meta-schemas/string-array.yaml#
> /builds/linux-media/users/ribalda/Documentation/devicetree/bindings/pci/marvell,armada8k-pcie.example.dtb:
> pcie@f2600000: interrupts: [[0], [32], [4]] is too long
> from schema $id: http://devicetree.org/schemas/pci/marvell,armada8k-pcie.yaml#
> 
> When I test your  for-next tree I have the same issue:
> https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git/log/Documentation/devicetree/bindings/crypto?h=for-next
> 
> They do not affect media drivers so right now I am just ignoring them,
> but I wanted to know if they are under your radar.
> 
You need to update your dtschema.

Best regards,
Krzysztof

Re: 6.16rc1 dts-bindings check fails

[Ricardo Ribalda]

Hi Krzysztof

On Wed, 11 Jun 2025 at 08:41, Krzysztof Kozlowski <krzk@kernel.org> wrote:
>
> On 10/06/2025 18:11, Ricardo Ribalda wrote:
> > Hi
> >
> > Media-CI is reporting some dts binding errors:
>
> Every builder of linux-next sees this, it's not specific to media.
>
> >
> > /builds/linux-media/users/ribalda/Documentation/devicetree/bindings/crypto/marvell,orion-crypto.yaml:
> > properties:reg-names:items:1: 'deprecated' is not one of ['const',
> > 'description', 'enum', 'not', 'pattern']
> > from schema $id: http://devicetree.org/meta-schemas/string-array.yaml#
> > /builds/linux-media/users/ribalda/Documentation/devicetree/bindings/pci/marvell,armada8k-pcie.example.dtb:
> > pcie@f2600000: interrupts: [[0], [32], [4]] is too long
> > from schema $id: http://devicetree.org/schemas/pci/marvell,armada8k-pcie.yaml#
> >
> > When I test your  for-next tree I have the same issue:
> > https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git/log/Documentation/devicetree/bindings/crypto?h=for-next
> >
> > They do not affect media drivers so right now I am just ignoring them,
> > but I wanted to know if they are under your radar.
> >
> You need to update your dtschema.

I was using the dtschema from pip.

If I use the version from git, There are other issues as well:

$ python3 -m venv venv
$ . venv/bin/activate
$  pip3 install
git+https://github.com/devicetree-org/dt-schema.git@master yamllint
$ make dt_binding_check

/usr/local/google/home/ribalda/work/linux/Documentation/devicetree/bindings/net/snps,dwmac.yaml:
mac-mode: missing type definition
/usr/local/google/home/ribalda/work/linux/Documentation/devicetree/bindings/regulator/infineon,ir38060.yaml:
maintainers:0: 'Not Me.' does not match '@'
        from schema $id: http://devicetree.org/meta-schemas/base.yaml#
/usr/local/google/home/ribalda/work/linux/Documentation/devicetree/bindings/soc/fsl/fsl,ls1028a-reset.yaml:
        Error in referenced schema matching $id:
http://devicetree.org/schemas/power/reset/syscon-reboot.yaml
        Tried these paths (check schema $id if path is wrong):
        /usr/local/google/home/ribalda/work/linux/Documentation/devicetree/bindingspower/reset/syscon-reboot.yaml
        /usr/local/google/home/ribalda/work/linux/venv/lib/python3.12/site-packages/dtschema/schemas/power/reset/syscon-reboot.yaml

/usr/local/google/home/ribalda/work/linux/Documentation/devicetree/bindings/pinctrl/xlnx,versal-pinctrl.yaml:
allOf: Missing additionalProperties/unevaluatedProperties constraint

/usr/local/google/home/ribalda/work/linux/Documentation/devicetree/bindings/soc/sophgo/sophgo,cv1800b-rtc.yaml:
        Error in referenced schema matching $id:
http://devicetree.org/schemas/rtc/rtc.yaml
        Tried these paths (check schema $id if path is wrong):
        /usr/local/google/home/ribalda/work/linux/Documentation/devicetree/bindings/soc/rtc/rtc.yaml
        /usr/local/google/home/ribalda/work/linux/venv/lib/python3.12/site-packages/dtschema/schemas/rtc/rtc.yaml


Is there a doc besides
https://www.kernel.org/doc/Documentation/devicetree/writing-schema.md
that I can follow to set up media-ci properly?

>
> Best regards,
> Krzysztof



-- 
Ricardo Ribalda

Re: 6.16rc1 dts-bindings check fails

[Krzysztof Kozlowski]

On 11/06/2025 09:06, Ricardo Ribalda wrote:
> Hi Krzysztof
> 
> On Wed, 11 Jun 2025 at 08:41, Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>
>> On 10/06/2025 18:11, Ricardo Ribalda wrote:
>>> Hi
>>>
>>> Media-CI is reporting some dts binding errors:
>>
>> Every builder of linux-next sees this, it's not specific to media.
>>
>>>
>>> /builds/linux-media/users/ribalda/Documentation/devicetree/bindings/crypto/marvell,orion-crypto.yaml:
>>> properties:reg-names:items:1: 'deprecated' is not one of ['const',
>>> 'description', 'enum', 'not', 'pattern']
>>> from schema $id: http://devicetree.org/meta-schemas/string-array.yaml#
>>> /builds/linux-media/users/ribalda/Documentation/devicetree/bindings/pci/marvell,armada8k-pcie.example.dtb:
>>> pcie@f2600000: interrupts: [[0], [32], [4]] is too long
>>> from schema $id: http://devicetree.org/schemas/pci/marvell,armada8k-pcie.yaml#
>>>
>>> When I test your  for-next tree I have the same issue:
>>> https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git/log/Documentation/devicetree/bindings/crypto?h=for-next
>>>
>>> They do not affect media drivers so right now I am just ignoring them,
>>> but I wanted to know if they are under your radar.
>>>
>> You need to update your dtschema.
> 
> I was using the dtschema from pip.

Latest from pip, so June, does not have these warnings. I think you
still use May.

> 
> If I use the version from git, There are other issues as well:
> 
> $ python3 -m venv venv
> $ . venv/bin/activate
> $  pip3 install
> git+https://github.com/devicetree-org/dt-schema.git@master yamllint
> $ make dt_binding_check
> 
> /usr/local/google/home/ribalda/work/linux/Documentation/devicetree/bindings/net/snps,dwmac.yaml:
> mac-mode: missing type definition

This is old.

> /usr/local/google/home/ribalda/work/linux/Documentation/devicetree/bindings/regulator/infineon,ir38060.yaml:
> maintainers:0: 'Not Me.' does not match '@'
>         from schema $id: http://devicetree.org/meta-schemas/base.yaml#
> /usr/local/google/home/ribalda/work/linux/Documentation/devicetree/bindings/soc/fsl/fsl,ls1028a-reset.yaml:
>         Error in referenced schema matching $id:
> http://devicetree.org/schemas/power/reset/syscon-reboot.yaml
>         Tried these paths (check schema $id if path is wrong):
>         /usr/local/google/home/ribalda/work/linux/Documentation/devicetree/bindingspower/reset/syscon-reboot.yaml
>         /usr/local/google/home/ribalda/work/linux/venv/lib/python3.12/site-packages/dtschema/schemas/power/reset/syscon-reboot.yaml
> 
> /usr/local/google/home/ribalda/work/linux/Documentation/devicetree/bindings/pinctrl/xlnx,versal-pinctrl.yaml:
> allOf: Missing additionalProperties/unevaluatedProperties constraint
> 
> /usr/local/google/home/ribalda/work/linux/Documentation/devicetree/bindings/soc/sophgo/sophgo,cv1800b-rtc.yaml:
>         Error in referenced schema matching $id:
> http://devicetree.org/schemas/rtc/rtc.yaml
>         Tried these paths (check schema $id if path is wrong):
>         /usr/local/google/home/ribalda/work/linux/Documentation/devicetree/bindings/soc/rtc/rtc.yaml
>         /usr/local/google/home/ribalda/work/linux/venv/lib/python3.12/site-packages/dtschema/schemas/rtc/rtc.yaml


These are known:
https://gitlab.com/robherring/linux-dt/-/jobs/10290125099
https://krzk.eu/#/builders/117/builds/613/steps/11/logs/warnings__2_

> 
> Is there a doc besides
> https://www.kernel.org/doc/Documentation/devicetree/writing-schema.md
> that I can follow to set up media-ci properly?


To update dtschema? No clue, I just run pipx upgrade. Works for me, but
depends on your OS/packaging.


Best regards,
Krzysztof

Re: 6.16rc1 dts-bindings check fails

[Ricardo Ribalda]

On Wed, 11 Jun 2025 at 09:11, Krzysztof Kozlowski <krzk@kernel.org> wrote:
>
> On 11/06/2025 09:06, Ricardo Ribalda wrote:
> > Hi Krzysztof
> >
> > On Wed, 11 Jun 2025 at 08:41, Krzysztof Kozlowski <krzk@kernel.org> wrote:
> >>
> >> On 10/06/2025 18:11, Ricardo Ribalda wrote:
> >>> Hi
> >>>
> >>> Media-CI is reporting some dts binding errors:
> >>
> >> Every builder of linux-next sees this, it's not specific to media.
> >>
> >>>
> >>> /builds/linux-media/users/ribalda/Documentation/devicetree/bindings/crypto/marvell,orion-crypto.yaml:
> >>> properties:reg-names:items:1: 'deprecated' is not one of ['const',
> >>> 'description', 'enum', 'not', 'pattern']
> >>> from schema $id: http://devicetree.org/meta-schemas/string-array.yaml#
> >>> /builds/linux-media/users/ribalda/Documentation/devicetree/bindings/pci/marvell,armada8k-pcie.example.dtb:
> >>> pcie@f2600000: interrupts: [[0], [32], [4]] is too long
> >>> from schema $id: http://devicetree.org/schemas/pci/marvell,armada8k-pcie.yaml#
> >>>
> >>> When I test your  for-next tree I have the same issue:
> >>> https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git/log/Documentation/devicetree/bindings/crypto?h=for-next
> >>>
> >>> They do not affect media drivers so right now I am just ignoring them,
> >>> but I wanted to know if they are under your radar.
> >>>
> >> You need to update your dtschema.
> >
> > I was using the dtschema from pip.
>
> Latest from pip, so June, does not have these warnings. I think you
> still use May.

Looks like pip was released  yesterday:
https://pypi.org/project/dtschema/#history

The image was created on monday, so yes I was using may.


>
> >
> > If I use the version from git, There are other issues as well:
> >
> > $ python3 -m venv venv
> > $ . venv/bin/activate
> > $  pip3 install
> > git+https://github.com/devicetree-org/dt-schema.git@master yamllint
> > $ make dt_binding_check
> >
> > /usr/local/google/home/ribalda/work/linux/Documentation/devicetree/bindings/net/snps,dwmac.yaml:
> > mac-mode: missing type definition
>
> This is old.
>
> > /usr/local/google/home/ribalda/work/linux/Documentation/devicetree/bindings/regulator/infineon,ir38060.yaml:
> > maintainers:0: 'Not Me.' does not match '@'
> >         from schema $id: http://devicetree.org/meta-schemas/base.yaml#
> > /usr/local/google/home/ribalda/work/linux/Documentation/devicetree/bindings/soc/fsl/fsl,ls1028a-reset.yaml:
> >         Error in referenced schema matching $id:
> > http://devicetree.org/schemas/power/reset/syscon-reboot.yaml
> >         Tried these paths (check schema $id if path is wrong):
> >         /usr/local/google/home/ribalda/work/linux/Documentation/devicetree/bindingspower/reset/syscon-reboot.yaml
> >         /usr/local/google/home/ribalda/work/linux/venv/lib/python3.12/site-packages/dtschema/schemas/power/reset/syscon-reboot.yaml
> >
> > /usr/local/google/home/ribalda/work/linux/Documentation/devicetree/bindings/pinctrl/xlnx,versal-pinctrl.yaml:
> > allOf: Missing additionalProperties/unevaluatedProperties constraint
> >
> > /usr/local/google/home/ribalda/work/linux/Documentation/devicetree/bindings/soc/sophgo/sophgo,cv1800b-rtc.yaml:
> >         Error in referenced schema matching $id:
> > http://devicetree.org/schemas/rtc/rtc.yaml
> >         Tried these paths (check schema $id if path is wrong):
> >         /usr/local/google/home/ribalda/work/linux/Documentation/devicetree/bindings/soc/rtc/rtc.yaml
> >         /usr/local/google/home/ribalda/work/linux/venv/lib/python3.12/site-packages/dtschema/schemas/rtc/rtc.yaml
>
>
> These are known:
> https://gitlab.com/robherring/linux-dt/-/jobs/10290125099
> https://krzk.eu/#/builders/117/builds/613/steps/11/logs/warnings__2_

ok. I will add them to the ignore list for now.

Thanks!

>
> >
> > Is there a doc besides
> > https://www.kernel.org/doc/Documentation/devicetree/writing-schema.md
> > that I can follow to set up media-ci properly?
>
>
> To update dtschema? No clue, I just run pipx upgrade. Works for me, but
> depends on your OS/packaging.
>
>
> Best regards,
> Krzysztof



-- 
Ricardo Ribalda

Re: 6.16rc1 dts-bindings check fails

[Rob Herring]

On Wed, Jun 11, 2025 at 2:06 AM Ricardo Ribalda <ribalda@chromium.org> wrote:
>
> Hi Krzysztof
>
> On Wed, 11 Jun 2025 at 08:41, Krzysztof Kozlowski <krzk@kernel.org> wrote:
> >
> > On 10/06/2025 18:11, Ricardo Ribalda wrote:
> > > Hi
> > >
> > > Media-CI is reporting some dts binding errors:
> >
> > Every builder of linux-next sees this, it's not specific to media.
> >
> > >
> > > /builds/linux-media/users/ribalda/Documentation/devicetree/bindings/crypto/marvell,orion-crypto.yaml:
> > > properties:reg-names:items:1: 'deprecated' is not one of ['const',
> > > 'description', 'enum', 'not', 'pattern']
> > > from schema $id: http://devicetree.org/meta-schemas/string-array.yaml#
> > > /builds/linux-media/users/ribalda/Documentation/devicetree/bindings/pci/marvell,armada8k-pcie.example.dtb:
> > > pcie@f2600000: interrupts: [[0], [32], [4]] is too long
> > > from schema $id: http://devicetree.org/schemas/pci/marvell,armada8k-pcie.yaml#
> > >
> > > When I test your  for-next tree I have the same issue:
> > > https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git/log/Documentation/devicetree/bindings/crypto?h=for-next
> > >
> > > They do not affect media drivers so right now I am just ignoring them,
> > > but I wanted to know if they are under your radar.
> > >
> > You need to update your dtschema.
>
> I was using the dtschema from pip.

I just released v2025.06.1, so update again.

>
> If I use the version from git, There are other issues as well:
>
> $ python3 -m venv venv
> $ . venv/bin/activate
> $  pip3 install
> git+https://github.com/devicetree-org/dt-schema.git@master yamllint
> $ make dt_binding_check
>
> /usr/local/google/home/ribalda/work/linux/Documentation/devicetree/bindings/net/snps,dwmac.yaml:
> mac-mode: missing type definition

This is now fixed with dtschema update.

> /usr/local/google/home/ribalda/work/linux/Documentation/devicetree/bindings/regulator/infineon,ir38060.yaml:
> maintainers:0: 'Not Me.' does not match '@'
>         from schema $id: http://devicetree.org/meta-schemas/base.yaml#

So far Not Me hasn't cared to add their email address. I guess we can
delete the binding and driver...

> /usr/local/google/home/ribalda/work/linux/Documentation/devicetree/bindings/soc/fsl/fsl,ls1028a-reset.yaml:
>         Error in referenced schema matching $id:
> http://devicetree.org/schemas/power/reset/syscon-reboot.yaml
>         Tried these paths (check schema $id if path is wrong):
>         /usr/local/google/home/ribalda/work/linux/Documentation/devicetree/bindingspower/reset/syscon-reboot.yaml
>         /usr/local/google/home/ribalda/work/linux/venv/lib/python3.12/site-packages/dtschema/schemas/power/reset/syscon-reboot.yaml

Fixed in next now, in Linus's tree soon.

> /usr/local/google/home/ribalda/work/linux/Documentation/devicetree/bindings/pinctrl/xlnx,versal-pinctrl.yaml:
> allOf: Missing additionalProperties/unevaluatedProperties constraint

This is now fixed with dtschema update.


> /usr/local/google/home/ribalda/work/linux/Documentation/devicetree/bindings/soc/sophgo/sophgo,cv1800b-rtc.yaml:
>         Error in referenced schema matching $id:
> http://devicetree.org/schemas/rtc/rtc.yaml
>         Tried these paths (check schema $id if path is wrong):
>         /usr/local/google/home/ribalda/work/linux/Documentation/devicetree/bindings/soc/rtc/rtc.yaml
>         /usr/local/google/home/ribalda/work/linux/venv/lib/python3.12/site-packages/dtschema/schemas/rtc/rtc.yaml

Patch posted, but still some discussion on this one.

Rob