From: Zhen Lei <thunder.leizhen@huawei.com> To: Rob Herring <robh+dt@kernel.org>, Pavel Machek <pavel@ucw.cz>, Dan Murphy <dmurphy@ti.com>, linux-leds <linux-leds@vger.kernel.org>, Lee Jones <lee.jones@linaro.org>, Benson Leung <bleung@chromium.org>, "Enric Balletbo i Serra" <enric.balletbo@collabora.com>, Guenter Roeck <groeck@chromium.org>, Mark Brown <broonie@kernel.org>, linux-spi <linux-spi@vger.kernel.org>, Lubomir Rintel <lkundrak@v3.sk>, devicetree <devicetree@vger.kernel.org>, linux-arm-kernel <linux-arm-kernel@lists.infradead.org>, linux-kernel <linux-kernel@vger.kernel.org> Cc: Zhen Lei <thunder.leizhen@huawei.com> Subject: [PATCH 0/6] fix all errors except one reported by dt_binding_check Date: Wed, 14 Oct 2020 00:08:39 +0800 [thread overview] Message-ID: <20201013160845.1772-1-thunder.leizhen@huawei.com> (raw) When people add multiple or common YAML files, they usually perform a full dt_binding_check. Unfortunately, some YAML files cannot pass the self-check. The errors or warning are listed below. It is necessary to eliminate them, so that people's time and energy are not wasted every time when execute comprehensive dt_binding_check. This error is fixed by Patch 1: /root/leizhen/linux-next/Documentation/devicetree/bindings/leds/leds-lp55xx.example.dt.yaml: led-controller@33: multi-led@2:color:0:0: 9 is greater than the maximum of 8 From schema: /root/leizhen/linux-next/Documentation/devicetree/bindings/leds/leds-lp55xx.yaml These errors are fixed by Patch 2: /root/leizhen/linux-next/Documentation/devicetree/bindings/chrome/google,cros-ec-typec.example.dt.yaml: ec@0: 'typec' does not match any of the regexes: 'pinctrl-[0-9]+' From schema: /root/leizhen/linux-next/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml /root/leizhen/linux-next/Documentation/devicetree/bindings/extcon/extcon-usbc-cros-ec.example.dt.yaml: cros-ec@0: 'extcon0', 'extcon1' do not match any of the regexes: 'pinctrl-[0-9]+' From schema: /root/leizhen/linux-next/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml /root/leizhen/linux-next/Documentation/devicetree/bindings/pwm/google,cros-ec-pwm.example.dt.yaml: cros-ec@0: 'ec-pwm' does not match any of the regexes: 'pinctrl-[0-9]+' From schema: /root/leizhen/linux-next/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml /root/leizhen/linux-next/Documentation/devicetree/bindings/regulator/google,cros-ec-regulator.example.dt.yaml: ec@0: '#address-cells', '#size-cells', 'regulator@0' do not match any of the regexes: 'pinctrl-[0-9]+' From schema: /root/leizhen/linux-next/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml /root/leizhen/linux-next/Documentation/devicetree/bindings/sound/google,cros-ec-codec.example.dt.yaml: cros-ec@0: '#address-cells', '#size-cells', 'ec-codec@10500000' do not match any of the regexes: 'pinctrl-[0-9]+' From schema: /root/leizhen/linux-next/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml These errors are fixed by Patch 3 and 4: Documentation/devicetree/bindings/misc/olpc,xo1.75-ec.example.dts:21.13-30.11: Warning (spi_bus_bridge): /example-0/spi: incorrect #address-cells for SPI bus Documentation/devicetree/bindings/misc/olpc,xo1.75-ec.example.dts:21.13-30.11: Warning (spi_bus_bridge): /example-0/spi: incorrect #size-cells for SPI bus Documentation/devicetree/bindings/misc/olpc,xo1.75-ec.example.dt.yaml: Warning (spi_bus_reg): Failed prerequisite 'spi_bus_bridge' Patch 5 and 6 fix the dtbs_check errors detected by Documentation/devicetree/bindings/misc/olpc,xo1.75-ec.yaml arch/arm/boot/dts/mmp2.dtsi:472.23-480.6: Warning (spi_bus_bridge): /soc/apb@d4000000/spi@d4037000: incorrect #address-cells for SPI bus also defined at arch/arm/boot/dts/mmp2-olpc-xo-1-75.dts:225.7-237.3 arch/arm/boot/dts/mmp2.dtsi:472.23-480.6: Warning (spi_bus_bridge): /soc/apb@d4000000/spi@d4037000: incorrect #size-cells for SPI bus also defined at arch/arm/boot/dts/mmp2-olpc-xo-1-75.dts:225.7-237.3 arch/arm/boot/dts/mmp2-olpc-xo-1-75.dtb: Warning (spi_bus_reg): Failed prerequisite 'spi_bus_bridge' arch/arm/boot/dts/mmp2.dtsi:472.23-480.6: Warning (spi_bus_bridge): /soc/apb@d4000000/spi@d4037000: incorrect #address-cells for SPI bus also defined at arch/arm/boot/dts/mmp2-olpc-xo-1-75.dts:225.7-237.3 arch/arm/boot/dts/mmp2.dtsi:472.23-480.6: Warning (spi_bus_bridge): /soc/apb@d4000000/spi@d4037000: incorrect #size-cells for SPI bus also defined at arch/arm/boot/dts/mmp2-olpc-xo-1-75.dts:225.7-237.3 arch/arm/boot/dts/mmp2-olpc-xo-1-75.dt.yaml: Warning (spi_bus_reg): Failed prerequisite 'spi_bus_bridge' /root/leizhen/linux-next/arch/arm/boot/dts/mmp2-olpc-xo-1-75.dt.yaml: slave: 'cmd-gpios' is a required property From schema: /root/leizhen/linux-next/Documentation/devicetree/bindings/misc/olpc,xo1.75-ec.yaml /root/leizhen/linux-next/arch/arm/boot/dts/mmp2-olpc-xo-1-75.dt.yaml: slave: 'cmd-gpio' does not match any of the regexes: 'pinctrl-[0-9]+' From schema: /root/leizhen/linux-next/Documentation/devicetree/bindings/misc/olpc,xo1.75-ec.yaml I have no good idea for this one, so leave it. Documentation/devicetree/bindings/pci/xilinx-versal-cpm.example.dts:43.62-47.30: Warning (pci_device_reg): /example-0/versal/pcie@fca10000/interrupt-controller: missing PCI reg property Zhen Lei (6): dt-bindings: leds: choose correct color value of multi-led dt-bindings: mfd: google,cros-ec: explicitly allow additional properties spi: dt-bindings: spi-controller: explicitly require #address-cells=<0> for slave mode dt-bindings: misc: explicitly add #address-cells for slave mode ARM: dts: mmp2-olpc-xo-1-75: explicitly add #address-cells=<0> for slave mode dt-bindings: misc: correct the property name cmd-gpios to cmd-gpio .../devicetree/bindings/leds/leds-lp55xx.yaml | 2 +- .../devicetree/bindings/mfd/google,cros-ec.yaml | 2 +- .../devicetree/bindings/misc/olpc,xo1.75-ec.yaml | 8 +++++--- .../devicetree/bindings/spi/spi-controller.yaml | 20 ++++++++++++++------ arch/arm/boot/dts/mmp2-olpc-xo-1-75.dts | 2 +- 5 files changed, 22 insertions(+), 12 deletions(-) -- 1.8.3
WARNING: multiple messages have this Message-ID (diff)
From: Zhen Lei <thunder.leizhen@huawei.com> To: Rob Herring <robh+dt@kernel.org>, Pavel Machek <pavel@ucw.cz>, Dan Murphy <dmurphy@ti.com>, linux-leds <linux-leds@vger.kernel.org>, Lee Jones <lee.jones@linaro.org>, Benson Leung <bleung@chromium.org>, "Enric Balletbo i Serra" <enric.balletbo@collabora.com>, Guenter Roeck <groeck@chromium.org>, Mark Brown <broonie@kernel.org>, linux-spi <linux-spi@vger.kernel.org>, Lubomir Rintel <lkundrak@v3.sk>, devicetree <devicetree@vger.kernel.org>, linux-arm-kernel <linux-arm-kernel@lists.infradead.org>, linux-kernel <linux-kernel@vger.kernel.org> Cc: Zhen Lei <thunder.leizhen@huawei.com> Subject: [PATCH 0/6] fix all errors except one reported by dt_binding_check Date: Wed, 14 Oct 2020 00:08:39 +0800 [thread overview] Message-ID: <20201013160845.1772-1-thunder.leizhen@huawei.com> (raw) When people add multiple or common YAML files, they usually perform a full dt_binding_check. Unfortunately, some YAML files cannot pass the self-check. The errors or warning are listed below. It is necessary to eliminate them, so that people's time and energy are not wasted every time when execute comprehensive dt_binding_check. This error is fixed by Patch 1: /root/leizhen/linux-next/Documentation/devicetree/bindings/leds/leds-lp55xx.example.dt.yaml: led-controller@33: multi-led@2:color:0:0: 9 is greater than the maximum of 8 From schema: /root/leizhen/linux-next/Documentation/devicetree/bindings/leds/leds-lp55xx.yaml These errors are fixed by Patch 2: /root/leizhen/linux-next/Documentation/devicetree/bindings/chrome/google,cros-ec-typec.example.dt.yaml: ec@0: 'typec' does not match any of the regexes: 'pinctrl-[0-9]+' From schema: /root/leizhen/linux-next/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml /root/leizhen/linux-next/Documentation/devicetree/bindings/extcon/extcon-usbc-cros-ec.example.dt.yaml: cros-ec@0: 'extcon0', 'extcon1' do not match any of the regexes: 'pinctrl-[0-9]+' From schema: /root/leizhen/linux-next/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml /root/leizhen/linux-next/Documentation/devicetree/bindings/pwm/google,cros-ec-pwm.example.dt.yaml: cros-ec@0: 'ec-pwm' does not match any of the regexes: 'pinctrl-[0-9]+' From schema: /root/leizhen/linux-next/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml /root/leizhen/linux-next/Documentation/devicetree/bindings/regulator/google,cros-ec-regulator.example.dt.yaml: ec@0: '#address-cells', '#size-cells', 'regulator@0' do not match any of the regexes: 'pinctrl-[0-9]+' From schema: /root/leizhen/linux-next/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml /root/leizhen/linux-next/Documentation/devicetree/bindings/sound/google,cros-ec-codec.example.dt.yaml: cros-ec@0: '#address-cells', '#size-cells', 'ec-codec@10500000' do not match any of the regexes: 'pinctrl-[0-9]+' From schema: /root/leizhen/linux-next/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml These errors are fixed by Patch 3 and 4: Documentation/devicetree/bindings/misc/olpc,xo1.75-ec.example.dts:21.13-30.11: Warning (spi_bus_bridge): /example-0/spi: incorrect #address-cells for SPI bus Documentation/devicetree/bindings/misc/olpc,xo1.75-ec.example.dts:21.13-30.11: Warning (spi_bus_bridge): /example-0/spi: incorrect #size-cells for SPI bus Documentation/devicetree/bindings/misc/olpc,xo1.75-ec.example.dt.yaml: Warning (spi_bus_reg): Failed prerequisite 'spi_bus_bridge' Patch 5 and 6 fix the dtbs_check errors detected by Documentation/devicetree/bindings/misc/olpc,xo1.75-ec.yaml arch/arm/boot/dts/mmp2.dtsi:472.23-480.6: Warning (spi_bus_bridge): /soc/apb@d4000000/spi@d4037000: incorrect #address-cells for SPI bus also defined at arch/arm/boot/dts/mmp2-olpc-xo-1-75.dts:225.7-237.3 arch/arm/boot/dts/mmp2.dtsi:472.23-480.6: Warning (spi_bus_bridge): /soc/apb@d4000000/spi@d4037000: incorrect #size-cells for SPI bus also defined at arch/arm/boot/dts/mmp2-olpc-xo-1-75.dts:225.7-237.3 arch/arm/boot/dts/mmp2-olpc-xo-1-75.dtb: Warning (spi_bus_reg): Failed prerequisite 'spi_bus_bridge' arch/arm/boot/dts/mmp2.dtsi:472.23-480.6: Warning (spi_bus_bridge): /soc/apb@d4000000/spi@d4037000: incorrect #address-cells for SPI bus also defined at arch/arm/boot/dts/mmp2-olpc-xo-1-75.dts:225.7-237.3 arch/arm/boot/dts/mmp2.dtsi:472.23-480.6: Warning (spi_bus_bridge): /soc/apb@d4000000/spi@d4037000: incorrect #size-cells for SPI bus also defined at arch/arm/boot/dts/mmp2-olpc-xo-1-75.dts:225.7-237.3 arch/arm/boot/dts/mmp2-olpc-xo-1-75.dt.yaml: Warning (spi_bus_reg): Failed prerequisite 'spi_bus_bridge' /root/leizhen/linux-next/arch/arm/boot/dts/mmp2-olpc-xo-1-75.dt.yaml: slave: 'cmd-gpios' is a required property From schema: /root/leizhen/linux-next/Documentation/devicetree/bindings/misc/olpc,xo1.75-ec.yaml /root/leizhen/linux-next/arch/arm/boot/dts/mmp2-olpc-xo-1-75.dt.yaml: slave: 'cmd-gpio' does not match any of the regexes: 'pinctrl-[0-9]+' From schema: /root/leizhen/linux-next/Documentation/devicetree/bindings/misc/olpc,xo1.75-ec.yaml I have no good idea for this one, so leave it. Documentation/devicetree/bindings/pci/xilinx-versal-cpm.example.dts:43.62-47.30: Warning (pci_device_reg): /example-0/versal/pcie@fca10000/interrupt-controller: missing PCI reg property Zhen Lei (6): dt-bindings: leds: choose correct color value of multi-led dt-bindings: mfd: google,cros-ec: explicitly allow additional properties spi: dt-bindings: spi-controller: explicitly require #address-cells=<0> for slave mode dt-bindings: misc: explicitly add #address-cells for slave mode ARM: dts: mmp2-olpc-xo-1-75: explicitly add #address-cells=<0> for slave mode dt-bindings: misc: correct the property name cmd-gpios to cmd-gpio .../devicetree/bindings/leds/leds-lp55xx.yaml | 2 +- .../devicetree/bindings/mfd/google,cros-ec.yaml | 2 +- .../devicetree/bindings/misc/olpc,xo1.75-ec.yaml | 8 +++++--- .../devicetree/bindings/spi/spi-controller.yaml | 20 ++++++++++++++------ arch/arm/boot/dts/mmp2-olpc-xo-1-75.dts | 2 +- 5 files changed, 22 insertions(+), 12 deletions(-) -- 1.8.3 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-10-13 16:09 UTC|newest] Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-13 16:08 Zhen Lei [this message] 2020-10-13 16:08 ` [PATCH 0/6] fix all errors except one reported by dt_binding_check Zhen Lei 2020-10-13 16:08 ` [PATCH 1/6] dt-bindings: leds: choose correct color value of multi-led Zhen Lei 2020-10-13 16:08 ` Zhen Lei 2020-10-13 16:17 ` Dan Murphy 2020-10-13 16:17 ` Dan Murphy 2020-10-13 17:04 ` Pavel Machek 2020-10-13 17:04 ` Pavel Machek 2020-10-14 1:08 ` Leizhen (ThunderTown) 2020-10-14 1:08 ` Leizhen (ThunderTown) 2020-10-13 16:08 ` [PATCH 2/6] dt-bindings: mfd: google,cros-ec: explicitly allow additional properties Zhen Lei 2020-10-13 16:08 ` [PATCH 2/6] dt-bindings: mfd: google, cros-ec: " Zhen Lei 2020-10-13 17:53 ` [PATCH 2/6] dt-bindings: mfd: google,cros-ec: " Dan Murphy 2020-10-13 17:53 ` Dan Murphy 2020-10-14 1:52 ` Leizhen (ThunderTown) 2020-10-14 1:52 ` Leizhen (ThunderTown) 2020-10-14 13:38 ` Rob Herring 2020-10-14 13:38 ` Rob Herring 2020-10-15 6:55 ` Leizhen (ThunderTown) 2020-10-15 6:55 ` Leizhen (ThunderTown) 2020-10-13 16:08 ` [PATCH 3/6] spi: dt-bindings: spi-controller: explicitly require #address-cells=<0> for slave mode Zhen Lei 2020-10-13 16:08 ` Zhen Lei 2020-10-14 13:41 ` Rob Herring 2020-10-14 13:41 ` Rob Herring 2020-10-13 16:08 ` [PATCH 4/6] dt-bindings: misc: explicitly add #address-cells " Zhen Lei 2020-10-13 16:08 ` Zhen Lei 2020-10-14 13:42 ` Rob Herring 2020-10-14 13:42 ` Rob Herring 2020-10-13 16:08 ` [PATCH 5/6] ARM: dts: mmp2-olpc-xo-1-75: explicitly add #address-cells=<0> " Zhen Lei 2020-10-13 16:08 ` Zhen Lei 2020-10-15 9:56 ` Leizhen (ThunderTown) 2020-10-15 9:56 ` Leizhen (ThunderTown) 2020-12-04 7:48 ` Leizhen (ThunderTown) 2020-12-04 7:48 ` Leizhen (ThunderTown) 2020-10-13 16:08 ` [PATCH 6/6] dt-bindings: misc: correct the property name cmd-gpios to cmd-gpio Zhen Lei 2020-10-13 16:08 ` Zhen Lei 2020-10-13 17:32 ` Dan Murphy 2020-10-13 17:32 ` Dan Murphy 2020-10-14 1:29 ` Leizhen (ThunderTown) 2020-10-14 1:29 ` Leizhen (ThunderTown) 2020-10-14 13:50 ` Rob Herring 2020-10-14 13:50 ` Rob Herring 2020-10-15 3:23 ` Leizhen (ThunderTown) 2020-10-15 3:23 ` Leizhen (ThunderTown) 2020-10-16 14:13 ` Rob Herring 2020-10-16 14:13 ` Rob Herring 2020-10-15 7:12 ` Lubomir Rintel 2020-10-15 7:12 ` Lubomir Rintel 2020-10-15 7:32 ` Leizhen (ThunderTown) 2020-10-15 7:32 ` Leizhen (ThunderTown)
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=20201013160845.1772-1-thunder.leizhen@huawei.com \ --to=thunder.leizhen@huawei.com \ --cc=bleung@chromium.org \ --cc=broonie@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=dmurphy@ti.com \ --cc=enric.balletbo@collabora.com \ --cc=groeck@chromium.org \ --cc=lee.jones@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-leds@vger.kernel.org \ --cc=linux-spi@vger.kernel.org \ --cc=lkundrak@v3.sk \ --cc=pavel@ucw.cz \ --cc=robh+dt@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.