Hi Rob, On Sun, Jan 27, 2019 at 4:00 AM Rob Herring <robh@xxxxxxxxxx> wrote: > On Wed, Jan 23, 2019 at 9:33 AM Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> wrote: > > On Tue, Dec 11, 2018 at 9:24 PM Rob Herring <robh@xxxxxxxxxx> wrote: > > > This adds the build infrastructure for checking DT binding schema > > > documents and validating dts files using the binding schema. > > > > > > Check DT binding schema documents: > > > make dt_binding_check > > > > > > Build dts files and check using DT binding schema: > > > make dtbs_check > > > > > > Optionally, DT_SCHEMA_FILES can be passed in with a schema file(s) to > > > use for validation. This makes it easier to find and fix errors > > > generated by a specific schema. > > > > > > Currently, the validation targets are separate from a normal build to > > > avoid a hard dependency on the external DT schema project and because > > > there are lots of warnings generated. > > > > Thanks, I'm giving this a try, and get errors like: > > > > DTC arch/arm/boot/dts/emev2-kzm9d.dt.yaml > > FATAL ERROR: No markers present in property 'cpu0' value > > > > and > > > > DTC arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dt.yaml > > FATAL ERROR: No markers present in property 'audio_clk_a' value > > > > Do you have a clue? > > That's really strange because those aren't even properties. Are other > dts files okay? This is the in tree dtc? > > The only time you should be missing markers is if you did a dts -> dts > -> dt.yaml. Found it: make dtbs_check doesn't play well with my local change to add symbols for DT overlays: --- a/scripts/Makefile.lib +++ b/scripts/Makefile.lib @@ -285,6 +285,10 @@ cmd_dt_S_dtb= \ $(obj)/%.dtb.S: $(obj)/%.dtb FORCE $(call if_changed,dt_S_dtb) +ifeq ($(CONFIG_OF_OVERLAY),y) +DTC_FLAGS += -@ +endif + quiet_cmd_dtc = DTC $@ cmd_dtc = mkdir -p $(dir ${dtc-tmp}) ; \ $(HOSTCC) -E $(dtc_cpp_flags) -x assembler-with-cpp -o $(dtc-tmp) $< ; \ Do you see a way to handle that better? Apart from a few expected issues, I'm seeing one other strange message: arch/arm/boot/dts/sh73a0-kzm9g.dt.yaml: interrupts: [[2, 4], [3, 4]] is too long This is the interrupts property in the adi,adxl345 node in arch/arm/boot/dts/sh73a0-kzm9g.dts. Apparently the check complains if more than one interrupt is listed here. Is this a known issue? Thanks! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx 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