Re: [PATCH] dt-bindings: Add missing array size constraints
On Tue, Jan 5, 2021 at 12:03 AM Rob Herring wrote: > DT properties which can have multiple entries need to specify what the > entries are and define how many entries there can be. In the case of > only a single entry, just 'maxItems: 1' is sufficient. > > Add the missing entry constraints. These were found with a modified > meta-schema. Unfortunately, there are a few cases where the size > constraints are not defined such as common bindings, so the meta-schema > can't be part of the normal checks. > > Cc: Jens Axboe > Cc: Stephen Boyd > Cc: Thierry Reding > Cc: MyungJoo Ham > Cc: Chanwoo Choi > Cc: Linus Walleij > Cc: Bartosz Golaszewski > Cc: Jonathan Cameron > Cc: Dmitry Torokhov > Cc: Thomas Gleixner > Cc: Marc Zyngier > Cc: Mauro Carvalho Chehab > Cc: Chen-Yu Tsai > Cc: Ulf Hansson > Cc: "David S. Miller" > Cc: Jakub Kicinski > Cc: Sebastian Reichel > Cc: Ohad Ben-Cohen > Cc: Bjorn Andersson > Cc: Greg Kroah-Hartman > Signed-off-by: Rob Herring This is good. The stricter the better. Reviewed-by: Linus Walleij Yours, Linus Walleij
Re: [PATCH] dt-bindings: Add missing array size constraints
On Tue, Jan 5, 2021 at 12:03 AM Rob Herring wrote: > > DT properties which can have multiple entries need to specify what the > entries are and define how many entries there can be. In the case of > only a single entry, just 'maxItems: 1' is sufficient. > > Add the missing entry constraints. These were found with a modified > meta-schema. Unfortunately, there are a few cases where the size > constraints are not defined such as common bindings, so the meta-schema > can't be part of the normal checks. > [snip!] > .../bindings/gpio/gpio-pca95xx.yaml | 1 + [snip!] > diff --git a/Documentation/devicetree/bindings/gpio/gpio-pca95xx.yaml > b/Documentation/devicetree/bindings/gpio/gpio-pca95xx.yaml > index f5ee23c2df60..57cdcfd4ff3c 100644 > --- a/Documentation/devicetree/bindings/gpio/gpio-pca95xx.yaml > +++ b/Documentation/devicetree/bindings/gpio/gpio-pca95xx.yaml > @@ -81,6 +81,7 @@ properties: > const: 2 > >reset-gpios: > +maxItems: 1 > description: >GPIO specification for the RESET input. This is an active low signal to >the PCA953x. Not valid for Maxim MAX732x devices. Acked-by: Bartosz Golaszewski
Re: [PATCH] dt-bindings: Add missing array size constraints
On Mon, Jan 04, 2021 at 04:02:53PM -0700, Rob Herring wrote: > .../input/touchscreen/elan,elants_i2c.yaml| 1 + Acked-by: Dmitry Torokhov -- Dmitry
Re: [PATCH] dt-bindings: Add missing array size constraints
Hi, Le mar. 5 janv. 2021 à 16:27, Mathieu Poirier a écrit : Adding Suman and Paul - guys please have a look. On Mon, Jan 04, 2021 at 04:02:53PM -0700, Rob Herring wrote: DT properties which can have multiple entries need to specify what the entries are and define how many entries there can be. In the case of only a single entry, just 'maxItems: 1' is sufficient. Add the missing entry constraints. These were found with a modified meta-schema. Unfortunately, there are a few cases where the size constraints are not defined such as common bindings, so the meta-schema can't be part of the normal checks. Cc: Jens Axboe Cc: Stephen Boyd Cc: Thierry Reding Cc: MyungJoo Ham Cc: Chanwoo Choi Cc: Linus Walleij Cc: Bartosz Golaszewski Cc: Jonathan Cameron Cc: Dmitry Torokhov Cc: Thomas Gleixner Cc: Marc Zyngier Cc: Mauro Carvalho Chehab Cc: Chen-Yu Tsai Cc: Ulf Hansson Cc: "David S. Miller" Cc: Jakub Kicinski Cc: Sebastian Reichel Cc: Ohad Ben-Cohen Cc: Bjorn Andersson Cc: Greg Kroah-Hartman Signed-off-by: Rob Herring --- Cc: linux-arm-ker...@lists.infradead.org Cc: linux-...@vger.kernel.org Cc: linux-...@vger.kernel.org Cc: dri-de...@lists.freedesktop.org Cc: linux-g...@vger.kernel.org Cc: linux-...@vger.kernel.org Cc: linux-in...@vger.kernel.org Cc: linux-me...@vger.kernel.org Cc: linux-...@vger.kernel.org Cc: net...@vger.kernel.org Cc: linux...@vger.kernel.org Cc: linux-remotep...@vger.kernel.org Cc: linux-ri...@lists.infradead.org Cc: linux-ser...@vger.kernel.org Cc: alsa-de...@alsa-project.org Cc: linux-...@vger.kernel.org Cc: linux-...@vger.kernel.org --- .../socionext,uniphier-system-cache.yaml | 4 ++-- .../bindings/ata/sata_highbank.yaml | 1 + .../bindings/clock/canaan,k210-clk.yaml | 1 + .../bindings/display/brcm,bcm2711-hdmi.yaml | 1 + .../bindings/display/brcm,bcm2835-hdmi.yaml | 1 + .../display/panel/jdi,lt070me05000.yaml | 1 + .../display/panel/mantix,mlaf057we51-x.yaml | 3 ++- .../display/panel/novatek,nt36672a.yaml | 1 + .../devicetree/bindings/dsp/fsl,dsp.yaml | 2 +- .../devicetree/bindings/eeprom/at25.yaml | 3 +-- .../bindings/extcon/extcon-ptn5150.yaml | 2 ++ .../bindings/gpio/gpio-pca95xx.yaml | 1 + .../bindings/iio/adc/adi,ad7768-1.yaml| 2 ++ .../bindings/iio/adc/aspeed,ast2400-adc.yaml | 1 + .../bindings/iio/adc/lltc,ltc2496.yaml| 2 +- .../bindings/iio/adc/qcom,spmi-vadc.yaml | 1 + .../bindings/iio/adc/st,stm32-adc.yaml| 2 ++ .../iio/magnetometer/asahi-kasei,ak8975.yaml | 1 + .../iio/potentiometer/adi,ad5272.yaml | 1 + .../input/touchscreen/elan,elants_i2c.yaml| 1 + .../interrupt-controller/fsl,intmux.yaml | 2 +- .../interrupt-controller/st,stm32-exti.yaml | 2 ++ .../allwinner,sun4i-a10-video-engine.yaml | 1 + .../devicetree/bindings/media/i2c/imx219.yaml | 1 + .../memory-controllers/exynos-srom.yaml | 2 ++ .../bindings/misc/fsl,dpaa2-console.yaml | 1 + .../bindings/mmc/mmc-controller.yaml | 2 ++ .../bindings/net/ti,k3-am654-cpsw-nuss.yaml | 1 + .../bindings/net/ti,k3-am654-cpts.yaml| 1 + .../phy/allwinner,sun4i-a10-usb-phy.yaml | 2 ++ .../phy/allwinner,sun50i-a64-usb-phy.yaml | 2 ++ .../phy/allwinner,sun50i-h6-usb-phy.yaml | 2 ++ .../phy/allwinner,sun5i-a13-usb-phy.yaml | 2 ++ .../phy/allwinner,sun6i-a31-usb-phy.yaml | 2 ++ .../phy/allwinner,sun8i-a23-usb-phy.yaml | 2 ++ .../phy/allwinner,sun8i-a83t-usb-phy.yaml | 2 ++ .../phy/allwinner,sun8i-h3-usb-phy.yaml | 2 ++ .../phy/allwinner,sun8i-r40-usb-phy.yaml | 2 ++ .../phy/allwinner,sun8i-v3s-usb-phy.yaml | 2 ++ .../phy/allwinner,sun9i-a80-usb-phy.yaml | 19 --- .../phy/socionext,uniphier-ahci-phy.yaml | 2 +- .../phy/socionext,uniphier-pcie-phy.yaml | 2 +- .../phy/socionext,uniphier-usb3hs-phy.yaml| 2 +- .../phy/socionext,uniphier-usb3ss-phy.yaml| 2 +- .../bindings/phy/ti,phy-gmii-sel.yaml | 2 +- .../pinctrl/aspeed,ast2400-pinctrl.yaml | 3 +-- .../pinctrl/aspeed,ast2500-pinctrl.yaml | 4 ++-- .../bindings/power/supply/bq25980.yaml| 1 + .../bindings/remoteproc/ingenic,vpu.yaml | 2 +- .../remoteproc/ti,omap-remoteproc.yaml| 3 +++ .../bindings/riscv/sifive-l2-cache.yaml | 1 + .../bindings/serial/renesas,hscif.yaml| 2 ++ .../bindings/serial/renesas,scif.yaml | 2 ++ .../bindings/serial/renesas,scifa.yaml| 2 ++ .../bindings/serial/renesas,scifb.yaml| 2 ++ .../sound/allwinner,sun4i-a10-codec.yaml | 1 + .../bindings/sound/google,sc7180-trogdor.yaml | 1 + .../bindings/sound/samsung,aries-wm8994.yaml | 3 +++ .../bindings/sound/samsung,midas-audio.yaml | 2 ++
Re: [PATCH] dt-bindings: Add missing array size constraints
On 1/5/21 5:27 PM, Mathieu Poirier wrote: > Adding Suman and Paul - guys please have a look. > > On Mon, Jan 04, 2021 at 04:02:53PM -0700, Rob Herring wrote: >> DT properties which can have multiple entries need to specify what the >> entries are and define how many entries there can be. In the case of >> only a single entry, just 'maxItems: 1' is sufficient. >> >> Add the missing entry constraints. These were found with a modified >> meta-schema. Unfortunately, there are a few cases where the size >> constraints are not defined such as common bindings, so the meta-schema >> can't be part of the normal checks. >> >> Cc: Jens Axboe >> Cc: Stephen Boyd >> Cc: Thierry Reding >> Cc: MyungJoo Ham >> Cc: Chanwoo Choi >> Cc: Linus Walleij >> Cc: Bartosz Golaszewski >> Cc: Jonathan Cameron >> Cc: Dmitry Torokhov >> Cc: Thomas Gleixner >> Cc: Marc Zyngier >> Cc: Mauro Carvalho Chehab >> Cc: Chen-Yu Tsai >> Cc: Ulf Hansson >> Cc: "David S. Miller" >> Cc: Jakub Kicinski >> Cc: Sebastian Reichel >> Cc: Ohad Ben-Cohen >> Cc: Bjorn Andersson >> Cc: Greg Kroah-Hartman >> Signed-off-by: Rob Herring >> --- >> Cc: linux-arm-ker...@lists.infradead.org >> Cc: linux-...@vger.kernel.org >> Cc: linux-...@vger.kernel.org >> Cc: dri-de...@lists.freedesktop.org >> Cc: linux-g...@vger.kernel.org >> Cc: linux-...@vger.kernel.org >> Cc: linux-in...@vger.kernel.org >> Cc: linux-me...@vger.kernel.org >> Cc: linux-...@vger.kernel.org >> Cc: net...@vger.kernel.org >> Cc: linux...@vger.kernel.org >> Cc: linux-remotep...@vger.kernel.org >> Cc: linux-ri...@lists.infradead.org >> Cc: linux-ser...@vger.kernel.org >> Cc: alsa-de...@alsa-project.org >> Cc: linux-...@vger.kernel.org >> Cc: linux-...@vger.kernel.org >> --- >> .../socionext,uniphier-system-cache.yaml | 4 ++-- >> .../bindings/ata/sata_highbank.yaml | 1 + >> .../bindings/clock/canaan,k210-clk.yaml | 1 + >> .../bindings/display/brcm,bcm2711-hdmi.yaml | 1 + >> .../bindings/display/brcm,bcm2835-hdmi.yaml | 1 + >> .../display/panel/jdi,lt070me05000.yaml | 1 + >> .../display/panel/mantix,mlaf057we51-x.yaml | 3 ++- >> .../display/panel/novatek,nt36672a.yaml | 1 + >> .../devicetree/bindings/dsp/fsl,dsp.yaml | 2 +- >> .../devicetree/bindings/eeprom/at25.yaml | 3 +-- >> .../bindings/extcon/extcon-ptn5150.yaml | 2 ++ >> .../bindings/gpio/gpio-pca95xx.yaml | 1 + >> .../bindings/iio/adc/adi,ad7768-1.yaml| 2 ++ >> .../bindings/iio/adc/aspeed,ast2400-adc.yaml | 1 + >> .../bindings/iio/adc/lltc,ltc2496.yaml| 2 +- >> .../bindings/iio/adc/qcom,spmi-vadc.yaml | 1 + >> .../bindings/iio/adc/st,stm32-adc.yaml| 2 ++ >> .../iio/magnetometer/asahi-kasei,ak8975.yaml | 1 + >> .../iio/potentiometer/adi,ad5272.yaml | 1 + >> .../input/touchscreen/elan,elants_i2c.yaml| 1 + >> .../interrupt-controller/fsl,intmux.yaml | 2 +- >> .../interrupt-controller/st,stm32-exti.yaml | 2 ++ >> .../allwinner,sun4i-a10-video-engine.yaml | 1 + >> .../devicetree/bindings/media/i2c/imx219.yaml | 1 + >> .../memory-controllers/exynos-srom.yaml | 2 ++ >> .../bindings/misc/fsl,dpaa2-console.yaml | 1 + >> .../bindings/mmc/mmc-controller.yaml | 2 ++ >> .../bindings/net/ti,k3-am654-cpsw-nuss.yaml | 1 + >> .../bindings/net/ti,k3-am654-cpts.yaml| 1 + >> .../phy/allwinner,sun4i-a10-usb-phy.yaml | 2 ++ >> .../phy/allwinner,sun50i-a64-usb-phy.yaml | 2 ++ >> .../phy/allwinner,sun50i-h6-usb-phy.yaml | 2 ++ >> .../phy/allwinner,sun5i-a13-usb-phy.yaml | 2 ++ >> .../phy/allwinner,sun6i-a31-usb-phy.yaml | 2 ++ >> .../phy/allwinner,sun8i-a23-usb-phy.yaml | 2 ++ >> .../phy/allwinner,sun8i-a83t-usb-phy.yaml | 2 ++ >> .../phy/allwinner,sun8i-h3-usb-phy.yaml | 2 ++ >> .../phy/allwinner,sun8i-r40-usb-phy.yaml | 2 ++ >> .../phy/allwinner,sun8i-v3s-usb-phy.yaml | 2 ++ >> .../phy/allwinner,sun9i-a80-usb-phy.yaml | 19 --- >> .../phy/socionext,uniphier-ahci-phy.yaml | 2 +- >> .../phy/socionext,uniphier-pcie-phy.yaml | 2 +- >> .../phy/socionext,uniphier-usb3hs-phy.yaml| 2 +- >> .../phy/socionext,uniphier-usb3ss-phy.yaml| 2 +- >> .../bindings/phy/ti,phy-gmii-sel.yaml | 2 +- >> .../pinctrl/aspeed,ast2400-pinctrl.yaml | 3 +-- >> .../pinctrl/aspeed,ast2500-pinctrl.yaml | 4 ++-- >> .../bindings/power/supply/bq25980.yaml| 1 + >> .../bindings/remoteproc/ingenic,vpu.yaml | 2 +- >> .../remoteproc/ti,omap-remoteproc.yaml| 3 +++ >> .../bindings/riscv/sifive-l2-cache.yaml | 1 + >> .../bindings/serial/renesas,hscif.yaml| 2 ++ >> .../bindings/serial/renesas,scif.yaml | 2 ++ >> .../bindings/serial/renesas,scifa.yaml| 2 ++ >> .../bindings/serial/renesas,scifb.yaml| 2 ++ >> .../sound/allwinner,sun4i-a10-codec.yaml | 1 + >>
Re: [PATCH] dt-bindings: Add missing array size constraints
Adding Suman and Paul - guys please have a look. On Mon, Jan 04, 2021 at 04:02:53PM -0700, Rob Herring wrote: > DT properties which can have multiple entries need to specify what the > entries are and define how many entries there can be. In the case of > only a single entry, just 'maxItems: 1' is sufficient. > > Add the missing entry constraints. These were found with a modified > meta-schema. Unfortunately, there are a few cases where the size > constraints are not defined such as common bindings, so the meta-schema > can't be part of the normal checks. > > Cc: Jens Axboe > Cc: Stephen Boyd > Cc: Thierry Reding > Cc: MyungJoo Ham > Cc: Chanwoo Choi > Cc: Linus Walleij > Cc: Bartosz Golaszewski > Cc: Jonathan Cameron > Cc: Dmitry Torokhov > Cc: Thomas Gleixner > Cc: Marc Zyngier > Cc: Mauro Carvalho Chehab > Cc: Chen-Yu Tsai > Cc: Ulf Hansson > Cc: "David S. Miller" > Cc: Jakub Kicinski > Cc: Sebastian Reichel > Cc: Ohad Ben-Cohen > Cc: Bjorn Andersson > Cc: Greg Kroah-Hartman > Signed-off-by: Rob Herring > --- > Cc: linux-arm-ker...@lists.infradead.org > Cc: linux-...@vger.kernel.org > Cc: linux-...@vger.kernel.org > Cc: dri-de...@lists.freedesktop.org > Cc: linux-g...@vger.kernel.org > Cc: linux-...@vger.kernel.org > Cc: linux-in...@vger.kernel.org > Cc: linux-me...@vger.kernel.org > Cc: linux-...@vger.kernel.org > Cc: net...@vger.kernel.org > Cc: linux...@vger.kernel.org > Cc: linux-remotep...@vger.kernel.org > Cc: linux-ri...@lists.infradead.org > Cc: linux-ser...@vger.kernel.org > Cc: alsa-de...@alsa-project.org > Cc: linux-...@vger.kernel.org > Cc: linux-...@vger.kernel.org > --- > .../socionext,uniphier-system-cache.yaml | 4 ++-- > .../bindings/ata/sata_highbank.yaml | 1 + > .../bindings/clock/canaan,k210-clk.yaml | 1 + > .../bindings/display/brcm,bcm2711-hdmi.yaml | 1 + > .../bindings/display/brcm,bcm2835-hdmi.yaml | 1 + > .../display/panel/jdi,lt070me05000.yaml | 1 + > .../display/panel/mantix,mlaf057we51-x.yaml | 3 ++- > .../display/panel/novatek,nt36672a.yaml | 1 + > .../devicetree/bindings/dsp/fsl,dsp.yaml | 2 +- > .../devicetree/bindings/eeprom/at25.yaml | 3 +-- > .../bindings/extcon/extcon-ptn5150.yaml | 2 ++ > .../bindings/gpio/gpio-pca95xx.yaml | 1 + > .../bindings/iio/adc/adi,ad7768-1.yaml| 2 ++ > .../bindings/iio/adc/aspeed,ast2400-adc.yaml | 1 + > .../bindings/iio/adc/lltc,ltc2496.yaml| 2 +- > .../bindings/iio/adc/qcom,spmi-vadc.yaml | 1 + > .../bindings/iio/adc/st,stm32-adc.yaml| 2 ++ > .../iio/magnetometer/asahi-kasei,ak8975.yaml | 1 + > .../iio/potentiometer/adi,ad5272.yaml | 1 + > .../input/touchscreen/elan,elants_i2c.yaml| 1 + > .../interrupt-controller/fsl,intmux.yaml | 2 +- > .../interrupt-controller/st,stm32-exti.yaml | 2 ++ > .../allwinner,sun4i-a10-video-engine.yaml | 1 + > .../devicetree/bindings/media/i2c/imx219.yaml | 1 + > .../memory-controllers/exynos-srom.yaml | 2 ++ > .../bindings/misc/fsl,dpaa2-console.yaml | 1 + > .../bindings/mmc/mmc-controller.yaml | 2 ++ > .../bindings/net/ti,k3-am654-cpsw-nuss.yaml | 1 + > .../bindings/net/ti,k3-am654-cpts.yaml| 1 + > .../phy/allwinner,sun4i-a10-usb-phy.yaml | 2 ++ > .../phy/allwinner,sun50i-a64-usb-phy.yaml | 2 ++ > .../phy/allwinner,sun50i-h6-usb-phy.yaml | 2 ++ > .../phy/allwinner,sun5i-a13-usb-phy.yaml | 2 ++ > .../phy/allwinner,sun6i-a31-usb-phy.yaml | 2 ++ > .../phy/allwinner,sun8i-a23-usb-phy.yaml | 2 ++ > .../phy/allwinner,sun8i-a83t-usb-phy.yaml | 2 ++ > .../phy/allwinner,sun8i-h3-usb-phy.yaml | 2 ++ > .../phy/allwinner,sun8i-r40-usb-phy.yaml | 2 ++ > .../phy/allwinner,sun8i-v3s-usb-phy.yaml | 2 ++ > .../phy/allwinner,sun9i-a80-usb-phy.yaml | 19 --- > .../phy/socionext,uniphier-ahci-phy.yaml | 2 +- > .../phy/socionext,uniphier-pcie-phy.yaml | 2 +- > .../phy/socionext,uniphier-usb3hs-phy.yaml| 2 +- > .../phy/socionext,uniphier-usb3ss-phy.yaml| 2 +- > .../bindings/phy/ti,phy-gmii-sel.yaml | 2 +- > .../pinctrl/aspeed,ast2400-pinctrl.yaml | 3 +-- > .../pinctrl/aspeed,ast2500-pinctrl.yaml | 4 ++-- > .../bindings/power/supply/bq25980.yaml| 1 + > .../bindings/remoteproc/ingenic,vpu.yaml | 2 +- > .../remoteproc/ti,omap-remoteproc.yaml| 3 +++ > .../bindings/riscv/sifive-l2-cache.yaml | 1 + > .../bindings/serial/renesas,hscif.yaml| 2 ++ > .../bindings/serial/renesas,scif.yaml | 2 ++ > .../bindings/serial/renesas,scifa.yaml| 2 ++ > .../bindings/serial/renesas,scifb.yaml| 2 ++ > .../sound/allwinner,sun4i-a10-codec.yaml | 1 + > .../bindings/sound/google,sc7180-trogdor.yaml | 1 + > .../bindings/sound/samsung,aries-wm8994.yaml | 3 +++ > .../bindings/sound/samsung,midas-audio.yaml
Re: [PATCH] dt-bindings: Add missing array size constraints
Hi Rob, On Tue, Jan 5, 2021 at 8:03 AM Rob Herring wrote: > > DT properties which can have multiple entries need to specify what the > entries are and define how many entries there can be. In the case of > only a single entry, just 'maxItems: 1' is sufficient. > > Add the missing entry constraints. These were found with a modified > meta-schema. Unfortunately, there are a few cases where the size > constraints are not defined such as common bindings, so the meta-schema > can't be part of the normal checks. > > Cc: Jens Axboe > Cc: Stephen Boyd > Cc: Thierry Reding > Cc: MyungJoo Ham > Cc: Chanwoo Choi > Cc: Linus Walleij > Cc: Bartosz Golaszewski > Cc: Jonathan Cameron > Cc: Dmitry Torokhov > Cc: Thomas Gleixner > Cc: Marc Zyngier > Cc: Mauro Carvalho Chehab > Cc: Chen-Yu Tsai > Cc: Ulf Hansson > Cc: "David S. Miller" > Cc: Jakub Kicinski > Cc: Sebastian Reichel > Cc: Ohad Ben-Cohen > Cc: Bjorn Andersson > Cc: Greg Kroah-Hartman > Signed-off-by: Rob Herring > --- > Cc: linux-arm-ker...@lists.infradead.org > Cc: linux-...@vger.kernel.org > Cc: linux-...@vger.kernel.org > Cc: dri-de...@lists.freedesktop.org > Cc: linux-g...@vger.kernel.org > Cc: linux-...@vger.kernel.org > Cc: linux-in...@vger.kernel.org > Cc: linux-me...@vger.kernel.org > Cc: linux-...@vger.kernel.org > Cc: net...@vger.kernel.org > Cc: linux...@vger.kernel.org > Cc: linux-remotep...@vger.kernel.org > Cc: linux-ri...@lists.infradead.org > Cc: linux-ser...@vger.kernel.org > Cc: alsa-de...@alsa-project.org > Cc: linux-...@vger.kernel.org > Cc: linux-...@vger.kernel.org > --- > .../socionext,uniphier-system-cache.yaml | 4 ++-- > .../bindings/ata/sata_highbank.yaml | 1 + > .../bindings/clock/canaan,k210-clk.yaml | 1 + > .../bindings/display/brcm,bcm2711-hdmi.yaml | 1 + > .../bindings/display/brcm,bcm2835-hdmi.yaml | 1 + > .../display/panel/jdi,lt070me05000.yaml | 1 + > .../display/panel/mantix,mlaf057we51-x.yaml | 3 ++- > .../display/panel/novatek,nt36672a.yaml | 1 + > .../devicetree/bindings/dsp/fsl,dsp.yaml | 2 +- > .../devicetree/bindings/eeprom/at25.yaml | 3 +-- > .../bindings/extcon/extcon-ptn5150.yaml | 2 ++ For extcon part, Acked-by: Chanwoo Choi (snip) Best Regards, Chanwoo Choi
Re: [PATCH] dt-bindings: Add missing array size constraints
On Tue, Jan 05, 2021 at 10:40:08AM -0700, Rob Herring wrote: > On Tue, Jan 05, 2021 at 02:04:14PM +0100, Greg Kroah-Hartman wrote: > > On Mon, Jan 04, 2021 at 04:02:53PM -0700, Rob Herring wrote: > > > DT properties which can have multiple entries need to specify what the > > > entries are and define how many entries there can be. In the case of > > > only a single entry, just 'maxItems: 1' is sufficient. > > > > > > Add the missing entry constraints. These were found with a modified > > > meta-schema. Unfortunately, there are a few cases where the size > > > constraints are not defined such as common bindings, so the meta-schema > > > can't be part of the normal checks. > > > > > > Cc: Jens Axboe > > > Cc: Stephen Boyd > > > Cc: Thierry Reding > > > Cc: MyungJoo Ham > > > Cc: Chanwoo Choi > > > Cc: Linus Walleij > > > Cc: Bartosz Golaszewski > > > Cc: Jonathan Cameron > > > Cc: Dmitry Torokhov > > > Cc: Thomas Gleixner > > > Cc: Marc Zyngier > > > Cc: Mauro Carvalho Chehab > > > Cc: Chen-Yu Tsai > > > Cc: Ulf Hansson > > > Cc: "David S. Miller" > > > Cc: Jakub Kicinski > > > Cc: Sebastian Reichel > > > Cc: Ohad Ben-Cohen > > > Cc: Bjorn Andersson > > > Cc: Greg Kroah-Hartman > > > Signed-off-by: Rob Herring > > > > > > > > > diff --git a/Documentation/devicetree/bindings/usb/generic-ehci.yaml > > > b/Documentation/devicetree/bindings/usb/generic-ehci.yaml > > > index 247ef00381ea..f76b25f7fc7a 100644 > > > --- a/Documentation/devicetree/bindings/usb/generic-ehci.yaml > > > +++ b/Documentation/devicetree/bindings/usb/generic-ehci.yaml > > > @@ -83,6 +83,7 @@ properties: > > >Phandle of a companion. > > > > > >phys: > > > +maxItems: 1 > > > description: PHY specifier for the USB PHY > > > > > >phy-names: > > > diff --git a/Documentation/devicetree/bindings/usb/generic-ohci.yaml > > > b/Documentation/devicetree/bindings/usb/generic-ohci.yaml > > > index 2178bcc401bc..8e2bd61f2075 100644 > > > --- a/Documentation/devicetree/bindings/usb/generic-ohci.yaml > > > +++ b/Documentation/devicetree/bindings/usb/generic-ohci.yaml > > > @@ -71,6 +71,7 @@ properties: > > >Overrides the detected port count > > > > > >phys: > > > +maxItems: 1 > > > description: PHY specifier for the USB PHY > > > > > >phy-names: > > > diff --git a/Documentation/devicetree/bindings/usb/ingenic,musb.yaml > > > b/Documentation/devicetree/bindings/usb/ingenic,musb.yaml > > > index 678396eeeb78..f506225a4d57 100644 > > > --- a/Documentation/devicetree/bindings/usb/ingenic,musb.yaml > > > +++ b/Documentation/devicetree/bindings/usb/ingenic,musb.yaml > > > @@ -40,7 +40,7 @@ properties: > > >- const: mc > > > > > >phys: > > > -description: PHY specifier for the USB PHY > > > +maxItems: 1 > > > > > >usb-role-switch: > > > type: boolean > > > > Any reason you dropped the description for this entry, but not the other > > ones above? > > No, I should have dropped those too. I dropped cases of genericish > descriptions on common properties. There's nothing specific to this > binding here really. > > > > > > diff --git a/Documentation/devicetree/bindings/usb/ti,j721e-usb.yaml > > > b/Documentation/devicetree/bindings/usb/ti,j721e-usb.yaml > > > index 388245b91a55..adce36e48bc9 100644 > > > --- a/Documentation/devicetree/bindings/usb/ti,j721e-usb.yaml > > > +++ b/Documentation/devicetree/bindings/usb/ti,j721e-usb.yaml > > > @@ -15,13 +15,14 @@ properties: > > >- const: ti,j721e-usb > > > > > >reg: > > > -description: module registers > > > +maxItems: 1 > > > > > >power-domains: > > > description: > > >PM domain provider node and an args specifier containing > > >the USB device id value. See, > > >Documentation/devicetree/bindings/soc/ti/sci-pm-domain.txt > > > +maxItems: 1 > > > > > >clocks: > > > description: Clock phandles to usb2_refclk and lpm_clk > > > > Same here, why remove the description? > > Really, the question is why keep 'description' on power-domains. Perhaps > there's a little value in the reference to sci-pm-domain.txt, so I left > it. Ok, if you are fine with this, that's ok with me, just didn't look very consistent :)
Re: [PATCH] dt-bindings: Add missing array size constraints
On Tue, Jan 05, 2021 at 02:04:14PM +0100, Greg Kroah-Hartman wrote: > On Mon, Jan 04, 2021 at 04:02:53PM -0700, Rob Herring wrote: > > DT properties which can have multiple entries need to specify what the > > entries are and define how many entries there can be. In the case of > > only a single entry, just 'maxItems: 1' is sufficient. > > > > Add the missing entry constraints. These were found with a modified > > meta-schema. Unfortunately, there are a few cases where the size > > constraints are not defined such as common bindings, so the meta-schema > > can't be part of the normal checks. > > > > Cc: Jens Axboe > > Cc: Stephen Boyd > > Cc: Thierry Reding > > Cc: MyungJoo Ham > > Cc: Chanwoo Choi > > Cc: Linus Walleij > > Cc: Bartosz Golaszewski > > Cc: Jonathan Cameron > > Cc: Dmitry Torokhov > > Cc: Thomas Gleixner > > Cc: Marc Zyngier > > Cc: Mauro Carvalho Chehab > > Cc: Chen-Yu Tsai > > Cc: Ulf Hansson > > Cc: "David S. Miller" > > Cc: Jakub Kicinski > > Cc: Sebastian Reichel > > Cc: Ohad Ben-Cohen > > Cc: Bjorn Andersson > > Cc: Greg Kroah-Hartman > > Signed-off-by: Rob Herring > > > > > diff --git a/Documentation/devicetree/bindings/usb/generic-ehci.yaml > > b/Documentation/devicetree/bindings/usb/generic-ehci.yaml > > index 247ef00381ea..f76b25f7fc7a 100644 > > --- a/Documentation/devicetree/bindings/usb/generic-ehci.yaml > > +++ b/Documentation/devicetree/bindings/usb/generic-ehci.yaml > > @@ -83,6 +83,7 @@ properties: > >Phandle of a companion. > > > >phys: > > +maxItems: 1 > > description: PHY specifier for the USB PHY > > > >phy-names: > > diff --git a/Documentation/devicetree/bindings/usb/generic-ohci.yaml > > b/Documentation/devicetree/bindings/usb/generic-ohci.yaml > > index 2178bcc401bc..8e2bd61f2075 100644 > > --- a/Documentation/devicetree/bindings/usb/generic-ohci.yaml > > +++ b/Documentation/devicetree/bindings/usb/generic-ohci.yaml > > @@ -71,6 +71,7 @@ properties: > >Overrides the detected port count > > > >phys: > > +maxItems: 1 > > description: PHY specifier for the USB PHY > > > >phy-names: > > diff --git a/Documentation/devicetree/bindings/usb/ingenic,musb.yaml > > b/Documentation/devicetree/bindings/usb/ingenic,musb.yaml > > index 678396eeeb78..f506225a4d57 100644 > > --- a/Documentation/devicetree/bindings/usb/ingenic,musb.yaml > > +++ b/Documentation/devicetree/bindings/usb/ingenic,musb.yaml > > @@ -40,7 +40,7 @@ properties: > >- const: mc > > > >phys: > > -description: PHY specifier for the USB PHY > > +maxItems: 1 > > > >usb-role-switch: > > type: boolean > > Any reason you dropped the description for this entry, but not the other > ones above? No, I should have dropped those too. I dropped cases of genericish descriptions on common properties. There's nothing specific to this binding here really. > > > diff --git a/Documentation/devicetree/bindings/usb/ti,j721e-usb.yaml > > b/Documentation/devicetree/bindings/usb/ti,j721e-usb.yaml > > index 388245b91a55..adce36e48bc9 100644 > > --- a/Documentation/devicetree/bindings/usb/ti,j721e-usb.yaml > > +++ b/Documentation/devicetree/bindings/usb/ti,j721e-usb.yaml > > @@ -15,13 +15,14 @@ properties: > >- const: ti,j721e-usb > > > >reg: > > -description: module registers > > +maxItems: 1 > > > >power-domains: > > description: > >PM domain provider node and an args specifier containing > >the USB device id value. See, > >Documentation/devicetree/bindings/soc/ti/sci-pm-domain.txt > > +maxItems: 1 > > > >clocks: > > description: Clock phandles to usb2_refclk and lpm_clk > > Same here, why remove the description? Really, the question is why keep 'description' on power-domains. Perhaps there's a little value in the reference to sci-pm-domain.txt, so I left it. Rob
Re: [PATCH] dt-bindings: Add missing array size constraints
On Mon, 4 Jan 2021 16:02:53 -0700 Rob Herring wrote: > DT properties which can have multiple entries need to specify what the > entries are and define how many entries there can be. In the case of > only a single entry, just 'maxItems: 1' is sufficient. > > Add the missing entry constraints. These were found with a modified > meta-schema. Unfortunately, there are a few cases where the size > constraints are not defined such as common bindings, so the meta-schema > can't be part of the normal checks. > > Cc: Jens Axboe > Cc: Stephen Boyd > Cc: Thierry Reding > Cc: MyungJoo Ham > Cc: Chanwoo Choi > Cc: Linus Walleij > Cc: Bartosz Golaszewski > Cc: Jonathan Cameron > Cc: Dmitry Torokhov > Cc: Thomas Gleixner > Cc: Marc Zyngier > Cc: Mauro Carvalho Chehab > Cc: Chen-Yu Tsai > Cc: Ulf Hansson > Cc: "David S. Miller" > Cc: Jakub Kicinski > Cc: Sebastian Reichel > Cc: Ohad Ben-Cohen > Cc: Bjorn Andersson > Cc: Greg Kroah-Hartman > Signed-off-by: Rob Herring Acked-by: Jonathan Cameron #for-iio > --- > Cc: linux-arm-ker...@lists.infradead.org > Cc: linux-...@vger.kernel.org > Cc: linux-...@vger.kernel.org > Cc: dri-de...@lists.freedesktop.org > Cc: linux-g...@vger.kernel.org > Cc: linux-...@vger.kernel.org > Cc: linux-in...@vger.kernel.org > Cc: linux-me...@vger.kernel.org > Cc: linux-...@vger.kernel.org > Cc: net...@vger.kernel.org > Cc: linux...@vger.kernel.org > Cc: linux-remotep...@vger.kernel.org > Cc: linux-ri...@lists.infradead.org > Cc: linux-ser...@vger.kernel.org > Cc: alsa-de...@alsa-project.org > Cc: linux-...@vger.kernel.org > Cc: linux-...@vger.kernel.org > --- > .../socionext,uniphier-system-cache.yaml | 4 ++-- > .../bindings/ata/sata_highbank.yaml | 1 + > .../bindings/clock/canaan,k210-clk.yaml | 1 + > .../bindings/display/brcm,bcm2711-hdmi.yaml | 1 + > .../bindings/display/brcm,bcm2835-hdmi.yaml | 1 + > .../display/panel/jdi,lt070me05000.yaml | 1 + > .../display/panel/mantix,mlaf057we51-x.yaml | 3 ++- > .../display/panel/novatek,nt36672a.yaml | 1 + > .../devicetree/bindings/dsp/fsl,dsp.yaml | 2 +- > .../devicetree/bindings/eeprom/at25.yaml | 3 +-- > .../bindings/extcon/extcon-ptn5150.yaml | 2 ++ > .../bindings/gpio/gpio-pca95xx.yaml | 1 + > .../bindings/iio/adc/adi,ad7768-1.yaml| 2 ++ > .../bindings/iio/adc/aspeed,ast2400-adc.yaml | 1 + > .../bindings/iio/adc/lltc,ltc2496.yaml| 2 +- > .../bindings/iio/adc/qcom,spmi-vadc.yaml | 1 + > .../bindings/iio/adc/st,stm32-adc.yaml| 2 ++ > .../iio/magnetometer/asahi-kasei,ak8975.yaml | 1 + > .../iio/potentiometer/adi,ad5272.yaml | 1 + > .../input/touchscreen/elan,elants_i2c.yaml| 1 + > .../interrupt-controller/fsl,intmux.yaml | 2 +- > .../interrupt-controller/st,stm32-exti.yaml | 2 ++ > .../allwinner,sun4i-a10-video-engine.yaml | 1 + > .../devicetree/bindings/media/i2c/imx219.yaml | 1 + > .../memory-controllers/exynos-srom.yaml | 2 ++ > .../bindings/misc/fsl,dpaa2-console.yaml | 1 + > .../bindings/mmc/mmc-controller.yaml | 2 ++ > .../bindings/net/ti,k3-am654-cpsw-nuss.yaml | 1 + > .../bindings/net/ti,k3-am654-cpts.yaml| 1 + > .../phy/allwinner,sun4i-a10-usb-phy.yaml | 2 ++ > .../phy/allwinner,sun50i-a64-usb-phy.yaml | 2 ++ > .../phy/allwinner,sun50i-h6-usb-phy.yaml | 2 ++ > .../phy/allwinner,sun5i-a13-usb-phy.yaml | 2 ++ > .../phy/allwinner,sun6i-a31-usb-phy.yaml | 2 ++ > .../phy/allwinner,sun8i-a23-usb-phy.yaml | 2 ++ > .../phy/allwinner,sun8i-a83t-usb-phy.yaml | 2 ++ > .../phy/allwinner,sun8i-h3-usb-phy.yaml | 2 ++ > .../phy/allwinner,sun8i-r40-usb-phy.yaml | 2 ++ > .../phy/allwinner,sun8i-v3s-usb-phy.yaml | 2 ++ > .../phy/allwinner,sun9i-a80-usb-phy.yaml | 19 --- > .../phy/socionext,uniphier-ahci-phy.yaml | 2 +- > .../phy/socionext,uniphier-pcie-phy.yaml | 2 +- > .../phy/socionext,uniphier-usb3hs-phy.yaml| 2 +- > .../phy/socionext,uniphier-usb3ss-phy.yaml| 2 +- > .../bindings/phy/ti,phy-gmii-sel.yaml | 2 +- > .../pinctrl/aspeed,ast2400-pinctrl.yaml | 3 +-- > .../pinctrl/aspeed,ast2500-pinctrl.yaml | 4 ++-- > .../bindings/power/supply/bq25980.yaml| 1 + > .../bindings/remoteproc/ingenic,vpu.yaml | 2 +- > .../remoteproc/ti,omap-remoteproc.yaml| 3 +++ > .../bindings/riscv/sifive-l2-cache.yaml | 1 + > .../bindings/serial/renesas,hscif.yaml| 2 ++ > .../bindings/serial/renesas,scif.yaml | 2 ++ > .../bindings/serial/renesas,scifa.yaml| 2 ++ > .../bindings/serial/renesas,scifb.yaml| 2 ++ > .../sound/allwinner,sun4i-a10-codec.yaml | 1 + > .../bindings/sound/google,sc7180-trogdor.yaml | 1 + > .../bindings/sound/samsung,aries-wm8994.yaml | 3 +++ > .../bindings/sound/samsung,midas-audio.yaml | 2 ++ >
Re: [PATCH] dt-bindings: Add missing array size constraints
On Mon, Jan 04, 2021 at 04:02:53PM -0700, Rob Herring wrote: > DT properties which can have multiple entries need to specify what the > entries are and define how many entries there can be. In the case of > only a single entry, just 'maxItems: 1' is sufficient. > > Add the missing entry constraints. These were found with a modified > meta-schema. Unfortunately, there are a few cases where the size > constraints are not defined such as common bindings, so the meta-schema > can't be part of the normal checks. > > Cc: Jens Axboe > Cc: Stephen Boyd > Cc: Thierry Reding > Cc: MyungJoo Ham > Cc: Chanwoo Choi > Cc: Linus Walleij > Cc: Bartosz Golaszewski > Cc: Jonathan Cameron > Cc: Dmitry Torokhov > Cc: Thomas Gleixner > Cc: Marc Zyngier > Cc: Mauro Carvalho Chehab > Cc: Chen-Yu Tsai > Cc: Ulf Hansson > Cc: "David S. Miller" > Cc: Jakub Kicinski > Cc: Sebastian Reichel > Cc: Ohad Ben-Cohen > Cc: Bjorn Andersson > Cc: Greg Kroah-Hartman > Signed-off-by: Rob Herring > diff --git a/Documentation/devicetree/bindings/usb/generic-ehci.yaml > b/Documentation/devicetree/bindings/usb/generic-ehci.yaml > index 247ef00381ea..f76b25f7fc7a 100644 > --- a/Documentation/devicetree/bindings/usb/generic-ehci.yaml > +++ b/Documentation/devicetree/bindings/usb/generic-ehci.yaml > @@ -83,6 +83,7 @@ properties: >Phandle of a companion. > >phys: > +maxItems: 1 > description: PHY specifier for the USB PHY > >phy-names: > diff --git a/Documentation/devicetree/bindings/usb/generic-ohci.yaml > b/Documentation/devicetree/bindings/usb/generic-ohci.yaml > index 2178bcc401bc..8e2bd61f2075 100644 > --- a/Documentation/devicetree/bindings/usb/generic-ohci.yaml > +++ b/Documentation/devicetree/bindings/usb/generic-ohci.yaml > @@ -71,6 +71,7 @@ properties: >Overrides the detected port count > >phys: > +maxItems: 1 > description: PHY specifier for the USB PHY > >phy-names: > diff --git a/Documentation/devicetree/bindings/usb/ingenic,musb.yaml > b/Documentation/devicetree/bindings/usb/ingenic,musb.yaml > index 678396eeeb78..f506225a4d57 100644 > --- a/Documentation/devicetree/bindings/usb/ingenic,musb.yaml > +++ b/Documentation/devicetree/bindings/usb/ingenic,musb.yaml > @@ -40,7 +40,7 @@ properties: >- const: mc > >phys: > -description: PHY specifier for the USB PHY > +maxItems: 1 > >usb-role-switch: > type: boolean Any reason you dropped the description for this entry, but not the other ones above? > diff --git a/Documentation/devicetree/bindings/usb/ti,j721e-usb.yaml > b/Documentation/devicetree/bindings/usb/ti,j721e-usb.yaml > index 388245b91a55..adce36e48bc9 100644 > --- a/Documentation/devicetree/bindings/usb/ti,j721e-usb.yaml > +++ b/Documentation/devicetree/bindings/usb/ti,j721e-usb.yaml > @@ -15,13 +15,14 @@ properties: >- const: ti,j721e-usb > >reg: > -description: module registers > +maxItems: 1 > >power-domains: > description: >PM domain provider node and an args specifier containing >the USB device id value. See, >Documentation/devicetree/bindings/soc/ti/sci-pm-domain.txt > +maxItems: 1 > >clocks: > description: Clock phandles to usb2_refclk and lpm_clk Same here, why remove the description? thanks, greg k-h
Re: [PATCH] dt-bindings: Add missing array size constraints
Hi Rob, On Mon, Jan 04, 2021 at 04:02:53PM -0700, Rob Herring wrote: > DT properties which can have multiple entries need to specify what the > entries are and define how many entries there can be. In the case of > only a single entry, just 'maxItems: 1' is sufficient. > > Add the missing entry constraints. These were found with a modified > meta-schema. Unfortunately, there are a few cases where the size > constraints are not defined such as common bindings, so the meta-schema > can't be part of the normal checks. > > [...] > .../bindings/power/supply/bq25980.yaml| 1 + > [...] Acked-by: Sebastian Reichel -- Sebastian signature.asc Description: PGP signature
[PATCH] dt-bindings: Add missing array size constraints
DT properties which can have multiple entries need to specify what the entries are and define how many entries there can be. In the case of only a single entry, just 'maxItems: 1' is sufficient. Add the missing entry constraints. These were found with a modified meta-schema. Unfortunately, there are a few cases where the size constraints are not defined such as common bindings, so the meta-schema can't be part of the normal checks. Cc: Jens Axboe Cc: Stephen Boyd Cc: Thierry Reding Cc: MyungJoo Ham Cc: Chanwoo Choi Cc: Linus Walleij Cc: Bartosz Golaszewski Cc: Jonathan Cameron Cc: Dmitry Torokhov Cc: Thomas Gleixner Cc: Marc Zyngier Cc: Mauro Carvalho Chehab Cc: Chen-Yu Tsai Cc: Ulf Hansson Cc: "David S. Miller" Cc: Jakub Kicinski Cc: Sebastian Reichel Cc: Ohad Ben-Cohen Cc: Bjorn Andersson Cc: Greg Kroah-Hartman Signed-off-by: Rob Herring --- Cc: linux-arm-ker...@lists.infradead.org Cc: linux-...@vger.kernel.org Cc: linux-...@vger.kernel.org Cc: dri-de...@lists.freedesktop.org Cc: linux-g...@vger.kernel.org Cc: linux-...@vger.kernel.org Cc: linux-in...@vger.kernel.org Cc: linux-me...@vger.kernel.org Cc: linux-...@vger.kernel.org Cc: net...@vger.kernel.org Cc: linux...@vger.kernel.org Cc: linux-remotep...@vger.kernel.org Cc: linux-ri...@lists.infradead.org Cc: linux-ser...@vger.kernel.org Cc: alsa-de...@alsa-project.org Cc: linux-...@vger.kernel.org Cc: linux-...@vger.kernel.org --- .../socionext,uniphier-system-cache.yaml | 4 ++-- .../bindings/ata/sata_highbank.yaml | 1 + .../bindings/clock/canaan,k210-clk.yaml | 1 + .../bindings/display/brcm,bcm2711-hdmi.yaml | 1 + .../bindings/display/brcm,bcm2835-hdmi.yaml | 1 + .../display/panel/jdi,lt070me05000.yaml | 1 + .../display/panel/mantix,mlaf057we51-x.yaml | 3 ++- .../display/panel/novatek,nt36672a.yaml | 1 + .../devicetree/bindings/dsp/fsl,dsp.yaml | 2 +- .../devicetree/bindings/eeprom/at25.yaml | 3 +-- .../bindings/extcon/extcon-ptn5150.yaml | 2 ++ .../bindings/gpio/gpio-pca95xx.yaml | 1 + .../bindings/iio/adc/adi,ad7768-1.yaml| 2 ++ .../bindings/iio/adc/aspeed,ast2400-adc.yaml | 1 + .../bindings/iio/adc/lltc,ltc2496.yaml| 2 +- .../bindings/iio/adc/qcom,spmi-vadc.yaml | 1 + .../bindings/iio/adc/st,stm32-adc.yaml| 2 ++ .../iio/magnetometer/asahi-kasei,ak8975.yaml | 1 + .../iio/potentiometer/adi,ad5272.yaml | 1 + .../input/touchscreen/elan,elants_i2c.yaml| 1 + .../interrupt-controller/fsl,intmux.yaml | 2 +- .../interrupt-controller/st,stm32-exti.yaml | 2 ++ .../allwinner,sun4i-a10-video-engine.yaml | 1 + .../devicetree/bindings/media/i2c/imx219.yaml | 1 + .../memory-controllers/exynos-srom.yaml | 2 ++ .../bindings/misc/fsl,dpaa2-console.yaml | 1 + .../bindings/mmc/mmc-controller.yaml | 2 ++ .../bindings/net/ti,k3-am654-cpsw-nuss.yaml | 1 + .../bindings/net/ti,k3-am654-cpts.yaml| 1 + .../phy/allwinner,sun4i-a10-usb-phy.yaml | 2 ++ .../phy/allwinner,sun50i-a64-usb-phy.yaml | 2 ++ .../phy/allwinner,sun50i-h6-usb-phy.yaml | 2 ++ .../phy/allwinner,sun5i-a13-usb-phy.yaml | 2 ++ .../phy/allwinner,sun6i-a31-usb-phy.yaml | 2 ++ .../phy/allwinner,sun8i-a23-usb-phy.yaml | 2 ++ .../phy/allwinner,sun8i-a83t-usb-phy.yaml | 2 ++ .../phy/allwinner,sun8i-h3-usb-phy.yaml | 2 ++ .../phy/allwinner,sun8i-r40-usb-phy.yaml | 2 ++ .../phy/allwinner,sun8i-v3s-usb-phy.yaml | 2 ++ .../phy/allwinner,sun9i-a80-usb-phy.yaml | 19 --- .../phy/socionext,uniphier-ahci-phy.yaml | 2 +- .../phy/socionext,uniphier-pcie-phy.yaml | 2 +- .../phy/socionext,uniphier-usb3hs-phy.yaml| 2 +- .../phy/socionext,uniphier-usb3ss-phy.yaml| 2 +- .../bindings/phy/ti,phy-gmii-sel.yaml | 2 +- .../pinctrl/aspeed,ast2400-pinctrl.yaml | 3 +-- .../pinctrl/aspeed,ast2500-pinctrl.yaml | 4 ++-- .../bindings/power/supply/bq25980.yaml| 1 + .../bindings/remoteproc/ingenic,vpu.yaml | 2 +- .../remoteproc/ti,omap-remoteproc.yaml| 3 +++ .../bindings/riscv/sifive-l2-cache.yaml | 1 + .../bindings/serial/renesas,hscif.yaml| 2 ++ .../bindings/serial/renesas,scif.yaml | 2 ++ .../bindings/serial/renesas,scifa.yaml| 2 ++ .../bindings/serial/renesas,scifb.yaml| 2 ++ .../sound/allwinner,sun4i-a10-codec.yaml | 1 + .../bindings/sound/google,sc7180-trogdor.yaml | 1 + .../bindings/sound/samsung,aries-wm8994.yaml | 3 +++ .../bindings/sound/samsung,midas-audio.yaml | 2 ++ .../devicetree/bindings/sound/tas2562.yaml| 2 ++ .../devicetree/bindings/sound/tas2770.yaml| 2 ++ .../bindings/sound/tlv320adcx140.yaml | 1 + .../devicetree/bindings/spi/renesas,rspi.yaml | 2 ++ .../devicetree/bindings/sram/sram.yaml| 2 ++ .../timer/allwinner,sun4i-a10-timer.yaml
