public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ricardo Ribalda <ribalda@chromium.org>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	devicetree@vger.kernel.org
Subject: Re: 6.16rc1 dts-bindings check fails
Date: Wed, 11 Jun 2025 09:11:14 +0200	[thread overview]
Message-ID: <afe90a1f-ac43-46bf-b5bd-723a214a6a2b@kernel.org> (raw)
In-Reply-To: <CANiDSCs0xp_PsKmyNpY3zHh9xuvJEgYXysB2wyLEZOL_+4Lokw@mail.gmail.com>

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

  reply	other threads:[~2025-06-11  7:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10 16:11 6.16rc1 dts-bindings check fails Ricardo Ribalda
2025-06-11  6:41 ` Krzysztof Kozlowski
2025-06-11  7:06   ` Ricardo Ribalda
2025-06-11  7:11     ` Krzysztof Kozlowski [this message]
2025-06-11  7:24       ` Ricardo Ribalda
2025-06-13  0:47     ` Rob Herring

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=afe90a1f-ac43-46bf-b5bd-723a214a6a2b@kernel.org \
    --to=krzk@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=ribalda@chromium.org \
    --cc=robh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox