mbox series

[v2,00/52] ARM: dts: Last round of DT schema fixes

Message ID 20210901091852.479202-1-maxime@cerno.tech
Headers show
Series ARM: dts: Last round of DT schema fixes | expand

Message

Maxime Ripard Sept. 1, 2021, 9:18 a.m. UTC
Hi,

Here's another round of schema warnings fixes for the Allwinner platform.

There's a fair share of new schemas in there since the schema tools now warn
when a compatible is not documented in a schema.

We don't have any warning anymore if we use the OPP binding Rob submitted, and
since that means we have all our devices properly validated I don't expect more
fixes now, aside from the usual bunch of regressions.

Let me know what you think,
Maxime

Maxime Ripard (52):
  ASoC: dt-bindings: Add WM8978 Binding
  ASoC: dt-bindings: Convert Bluetooth SCO Link binding to a schema
  ASoC: dt-bindings: Convert SPDIF Transmitter binding to a schema
  ASoC: dt-bindings: Convert Simple Amplifier binding to a schema
  dt-bindings: Convert Reserved Memory binding to a schema
  dt-bindings: arm: Convert ARM CCI-400 binding to a schema
  dt-bindings: bluetooth: broadcom: Fix clocks check
  dt-bindings: bluetooth: realtek: Add missing max-speed
  dt-bindings: clocks: Fix typo in the H6 compatible
  dt-bindings: display: Move idk-1110wr to panel-lvds
  dt-bindings: display: Move idk-2121wr to panel-lvds
  dt-bindings: display: Move ee101ia-01d to panel-lvds
  dt-bindings: display: aa104xd12: Remove unused vcc-supply
  dt-bindings: display: aa104xd12: Fix data-mapping
  dt-bindings: display: Move aa104xd12 to panel-lvds
  dt-bindings: display: aa121td01: Remove unused vcc-supply
  dt-bindings: display: aa121td01: Fix data-mapping
  dt-bindings: display: Move aa121td01 to panel-lvds
  dt-bindings: display: Move gktw70sdae4se to panel-lvds
  dt-bindings: display: panel-lvds: Document missing panel compatibles
  dt-bindings: gnss: Convert UBlox Neo-6M binding to a schema
  dt-bindings: gpio: Convert X-Powers AXP209 GPIO binding to a schema
  dt-bindings: hwmon: Add IIO HWMON binding
  dt-bindings: input: Convert Silead GSL1680 binding to a schema
  dt-bindings: interconnect: sunxi: Add R40 MBUS compatible
  dt-bindings: media: ti,cal: Fix example
  dt-bindings: media: Convert OV5640 binding to a schema
  dt-bindings: mfd: Convert X-Powers AC100 binding to a schema
  dt-bindings: mfd: Convert X-Powers AXP binding to a schema
  dt-bindings: mmc: Convert MMC Card binding to a schema
  dt-bindings: net: dwmac: Fix typo in the R40 compatible
  dt-bindings: net: wireless: Convert ESP ESP8089 binding to a schema
  dt-bindings: regulator: Convert SY8106A binding to a schema
  dt-bindings: sunxi: Add CPU Configuration Controller Binding
  dt-bindings: sunxi: Add Allwinner A80 PRCM Binding
  dt-bindings: usb: Convert SMSC USB3503 binding to a schema
  dt-bindings: usb: dwc3: Fix usb-phy check
  dt-bindings: w1: Convert 1-Wire GPIO binding to a schema
  ARM: dts: sunxi: Rename power-supply names
  ARM: dts: sunxi: Rename gpio pinctrl names
  ARM: dts: sunxi: Fix OPP arrays
  ARM: dts: sunxi: Fix OPPs node name
  ARM: dts: sunxi: Fix the SPI NOR node names
  ARM: dts: v3s: Remove useless DMA properties
  ARM: dts: tbs711: Fix touchscreen compatible
  ARM: dts: cubieboard4: Remove the dumb-vga-dac compatible
  arm64: dts: allwinner: h5: Fix GPU thermal zone node name
  arm64: dts: allwinner: h6: Fix de3 parent clocks ordering
  arm64: dts: allwinner: a100: Fix thermal zone node name
  arm64: dts: allwinner: pinetab: Change regulator node name to avoid
    warning
  arm64: dts: allwinner: teres-i: Add missing reg
  arm64: dts: allwinner: teres-i: Remove wakekup-source from the PMIC

 .../devicetree/bindings/arm/arm,cci-400.yaml  | 216 ++++++++++
 .../bindings/arm/cci-control-port.yaml        |  38 ++
 Documentation/devicetree/bindings/arm/cci.txt | 224 ----------
 .../devicetree/bindings/arm/cpus.yaml         |   2 +
 .../arm/sunxi/allwinner,sun4i-a10-mbus.yaml   |   1 +
 .../sunxi/allwinner,sun6i-a31-cpuconfig.yaml  |  38 ++
 .../arm/sunxi/allwinner,sun9i-a80-prcm.yaml   |  33 ++
 .../clock/allwinner,sun8i-a83t-de2-clk.yaml   |   2 +-
 .../display/panel/advantech,idk-1110wr.yaml   |  69 ---
 .../display/panel/advantech,idk-2121wr.yaml   | 121 ------
 .../display/panel/innolux,ee101ia-01d.yaml    |  31 --
 .../bindings/display/panel/lvds.yaml          | 130 +++++-
 .../display/panel/mitsubishi,aa104xd12.yaml   |  75 ----
 .../display/panel/mitsubishi,aa121td01.yaml   |  74 ----
 .../display/panel/sgd,gktw70sdae4se.yaml      |  68 ---
 .../bindings/gnss/u-blox,neo-6m.yaml          |  62 +++
 .../devicetree/bindings/gnss/u-blox.txt       |  45 --
 .../devicetree/bindings/gpio/gpio-axp209.txt  |  75 ----
 .../bindings/gpio/x-powers,axp209-gpio.yaml   |  55 +++
 .../devicetree/bindings/hwmon/iio-hwmon.yaml  |  37 ++
 .../i2c/allwinner,sun6i-a31-p2wi.yaml         |   2 +-
 .../input/touchscreen/silead,gsl1680.yaml     |  91 ++++
 .../input/touchscreen/silead_gsl1680.txt      |  44 --
 .../devicetree/bindings/media/i2c/ov5640.txt  |  92 ----
 .../bindings/media/i2c/ovti,ov5640.yaml       | 154 +++++++
 .../devicetree/bindings/media/ti,cal.yaml     |   4 +-
 .../devicetree/bindings/mfd/ac100.txt         |  50 ---
 .../devicetree/bindings/mfd/axp20x.txt        | 273 ------------
 .../bindings/mfd/x-powers,ac100.yaml          | 116 +++++
 .../bindings/mfd/x-powers,axp152.yaml         | 400 ++++++++++++++++++
 .../devicetree/bindings/mmc/mmc-card.txt      |  30 --
 .../devicetree/bindings/mmc/mmc-card.yaml     |  48 +++
 .../bindings/mmc/mmc-controller.yaml          |   6 -
 .../net/allwinner,sun8i-a83t-emac.yaml        |   4 +-
 .../bindings/net/broadcom-bluetooth.yaml      |  17 +-
 .../bindings/net/realtek-bluetooth.yaml       |   2 +
 .../devicetree/bindings/net/snps,dwmac.yaml   |   6 +-
 .../bindings/net/wireless/esp,esp8089.txt     |  30 --
 .../bindings/net/wireless/esp,esp8089.yaml    |  43 ++
 .../bindings/regulator/silergy,sy8106a.yaml   |  52 +++
 .../bindings/regulator/sy8106a-regulator.txt  |  23 -
 .../reserved-memory/memory-region.yaml        |  40 ++
 .../reserved-memory/reserved-memory.txt       | 172 +-------
 .../reserved-memory/reserved-memory.yaml      |  96 +++++
 .../reserved-memory/shared-dma-pool.yaml      |  87 ++++
 .../devicetree/bindings/sound/bt-sco.txt      |  13 -
 .../bindings/sound/linux,bt-sco.yaml          |  38 ++
 .../bindings/sound/linux,spdif-dit.yaml       |  32 ++
 .../bindings/sound/simple-amplifier.txt       |  17 -
 .../sound/simple-audio-amplifier.yaml         |  45 ++
 .../bindings/sound/spdif-transmitter.txt      |  10 -
 .../devicetree/bindings/sound/wlf,wm8978.yaml |  58 +++
 .../devicetree/bindings/usb/smsc,usb3503.yaml | 108 +++++
 .../devicetree/bindings/usb/snps,dwc3.yaml    |  10 +-
 .../devicetree/bindings/usb/usb3503.txt       |  39 --
 .../devicetree/bindings/w1/w1-gpio.txt        |  27 --
 .../devicetree/bindings/w1/w1-gpio.yaml       |  44 ++
 arch/arm/boot/dts/axp209.dtsi                 |   6 +-
 arch/arm/boot/dts/axp22x.dtsi                 |   6 +-
 arch/arm/boot/dts/axp81x.dtsi                 |  10 +-
 .../arm/boot/dts/sun4i-a10-olinuxino-lime.dts |  11 +-
 arch/arm/boot/dts/sun4i-a10.dtsi              |  11 +-
 arch/arm/boot/dts/sun5i-a13.dtsi              |  15 +-
 arch/arm/boot/dts/sun6i-a31.dtsi              |  44 +-
 arch/arm/boot/dts/sun7i-a20-bananapi.dts      |  17 +-
 arch/arm/boot/dts/sun7i-a20.dtsi              |  34 +-
 arch/arm/boot/dts/sun8i-a33.dtsi              |   4 +-
 arch/arm/boot/dts/sun8i-a83t-tbs-a711.dts     |   2 +-
 arch/arm/boot/dts/sun8i-a83t.dtsi             |   4 +-
 arch/arm/boot/dts/sun8i-h3.dtsi               |   4 +-
 arch/arm/boot/dts/sun8i-v3-sl631.dtsi         |   2 +-
 arch/arm/boot/dts/sun8i-v3s.dtsi              |   2 -
 arch/arm/boot/dts/sun9i-a80-cubieboard4.dts   |   2 +-
 .../boot/dts/sunxi-libretech-all-h3-it.dtsi   |   2 +-
 arch/arm64/boot/dts/allwinner/axp803.dtsi     |  10 +-
 .../arm64/boot/dts/allwinner/sun50i-a100.dtsi |   6 +-
 .../dts/allwinner/sun50i-a64-cpu-opp.dtsi     |   2 +-
 .../dts/allwinner/sun50i-a64-orangepi-win.dts |   2 +-
 .../boot/dts/allwinner/sun50i-a64-pinetab.dts |   2 +-
 .../boot/dts/allwinner/sun50i-a64-teres-i.dts |   3 +-
 .../boot/dts/allwinner/sun50i-h5-cpu-opp.dtsi |   2 +-
 arch/arm64/boot/dts/allwinner/sun50i-h5.dtsi  |   2 +-
 .../boot/dts/allwinner/sun50i-h6-cpu-opp.dtsi |   2 +-
 arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi  |   8 +-
 84 files changed, 2191 insertions(+), 1743 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/arm/arm,cci-400.yaml
 create mode 100644 Documentation/devicetree/bindings/arm/cci-control-port.yaml
 delete mode 100644 Documentation/devicetree/bindings/arm/cci.txt
 create mode 100644 Documentation/devicetree/bindings/arm/sunxi/allwinner,sun6i-a31-cpuconfig.yaml
 create mode 100644 Documentation/devicetree/bindings/arm/sunxi/allwinner,sun9i-a80-prcm.yaml
 delete mode 100644 Documentation/devicetree/bindings/display/panel/advantech,idk-1110wr.yaml
 delete mode 100644 Documentation/devicetree/bindings/display/panel/advantech,idk-2121wr.yaml
 delete mode 100644 Documentation/devicetree/bindings/display/panel/innolux,ee101ia-01d.yaml
 delete mode 100644 Documentation/devicetree/bindings/display/panel/mitsubishi,aa104xd12.yaml
 delete mode 100644 Documentation/devicetree/bindings/display/panel/mitsubishi,aa121td01.yaml
 delete mode 100644 Documentation/devicetree/bindings/display/panel/sgd,gktw70sdae4se.yaml
 create mode 100644 Documentation/devicetree/bindings/gnss/u-blox,neo-6m.yaml
 delete mode 100644 Documentation/devicetree/bindings/gnss/u-blox.txt
 delete mode 100644 Documentation/devicetree/bindings/gpio/gpio-axp209.txt
 create mode 100644 Documentation/devicetree/bindings/gpio/x-powers,axp209-gpio.yaml
 create mode 100644 Documentation/devicetree/bindings/hwmon/iio-hwmon.yaml
 create mode 100644 Documentation/devicetree/bindings/input/touchscreen/silead,gsl1680.yaml
 delete mode 100644 Documentation/devicetree/bindings/input/touchscreen/silead_gsl1680.txt
 delete mode 100644 Documentation/devicetree/bindings/media/i2c/ov5640.txt
 create mode 100644 Documentation/devicetree/bindings/media/i2c/ovti,ov5640.yaml
 delete mode 100644 Documentation/devicetree/bindings/mfd/ac100.txt
 delete mode 100644 Documentation/devicetree/bindings/mfd/axp20x.txt
 create mode 100644 Documentation/devicetree/bindings/mfd/x-powers,ac100.yaml
 create mode 100644 Documentation/devicetree/bindings/mfd/x-powers,axp152.yaml
 delete mode 100644 Documentation/devicetree/bindings/mmc/mmc-card.txt
 create mode 100644 Documentation/devicetree/bindings/mmc/mmc-card.yaml
 delete mode 100644 Documentation/devicetree/bindings/net/wireless/esp,esp8089.txt
 create mode 100644 Documentation/devicetree/bindings/net/wireless/esp,esp8089.yaml
 create mode 100644 Documentation/devicetree/bindings/regulator/silergy,sy8106a.yaml
 delete mode 100644 Documentation/devicetree/bindings/regulator/sy8106a-regulator.txt
 create mode 100644 Documentation/devicetree/bindings/reserved-memory/memory-region.yaml
 create mode 100644 Documentation/devicetree/bindings/reserved-memory/reserved-memory.yaml
 create mode 100644 Documentation/devicetree/bindings/reserved-memory/shared-dma-pool.yaml
 delete mode 100644 Documentation/devicetree/bindings/sound/bt-sco.txt
 create mode 100644 Documentation/devicetree/bindings/sound/linux,bt-sco.yaml
 create mode 100644 Documentation/devicetree/bindings/sound/linux,spdif-dit.yaml
 delete mode 100644 Documentation/devicetree/bindings/sound/simple-amplifier.txt
 create mode 100644 Documentation/devicetree/bindings/sound/simple-audio-amplifier.yaml
 delete mode 100644 Documentation/devicetree/bindings/sound/spdif-transmitter.txt
 create mode 100644 Documentation/devicetree/bindings/sound/wlf,wm8978.yaml
 create mode 100644 Documentation/devicetree/bindings/usb/smsc,usb3503.yaml
 delete mode 100644 Documentation/devicetree/bindings/usb/usb3503.txt
 delete mode 100644 Documentation/devicetree/bindings/w1/w1-gpio.txt
 create mode 100644 Documentation/devicetree/bindings/w1/w1-gpio.yaml

-- 
2.31.1

Comments

Tom Rini Sept. 1, 2021, 12:10 p.m. UTC | #1
On Wed, Sep 01, 2021 at 11:18:05AM +0200, Maxime Ripard wrote:

> The Reserved Memory mechanism is supported by Linux thanks to its device
> tree binding.
> 
> Now that we have the DT validation in place, let's convert the device
> tree bindings for that driver over to a YAML schema.
> 
> Cc: Mailing List <devicetree-spec@vger.kernel.org>
> Signed-off-by: Maxime Ripard <maxime@cerno.tech>

Minor request.  As device tree bindings are used and valid and
applicable outside of Linux, it shouldn't be mentioned in the commit
message either.  This binding is just as valid for U-Boot, FreeBSD, etc
as it is for Linux :)  Thanks!
Rob Herring (Arm) Sept. 3, 2021, 5:52 p.m. UTC | #2
On Wed, 01 Sep 2021 11:18:02 +0200, Maxime Ripard wrote:
> Bluetooth SCO Link are supported by Linux with a matching device tree

> binding.

> 

> Now that we have the DT validation in place, let's convert the device

> tree bindings for that driver over to a YAML schema.

> 

> Cc: alsa-devel@alsa-project.org

> Cc: devicetree@vger.kernel.org

> Cc: Liam Girdwood <lgirdwood@gmail.com>

> Cc: Mark Brown <broonie@kernel.org>

> Cc: Samuel Holland <samuel@sholland.org>

> Signed-off-by: Maxime Ripard <maxime@cerno.tech>

> 

> ---

> 

> Changes from v1:

>   - Accept either a 0 or 1 #sound-dai-cells

> ---

>  .../devicetree/bindings/sound/bt-sco.txt      | 13 -------

>  .../bindings/sound/linux,bt-sco.yaml          | 38 +++++++++++++++++++

>  2 files changed, 38 insertions(+), 13 deletions(-)

>  delete mode 100644 Documentation/devicetree/bindings/sound/bt-sco.txt

>  create mode 100644 Documentation/devicetree/bindings/sound/linux,bt-sco.yaml

> 


Reviewed-by: Rob Herring <robh@kernel.org>
Rob Herring (Arm) Sept. 3, 2021, 6:08 p.m. UTC | #3
On Wed, 01 Sep 2021 11:18:05 +0200, Maxime Ripard wrote:
> The Reserved Memory mechanism is supported by Linux thanks to its device

> tree binding.

> 

> Now that we have the DT validation in place, let's convert the device

> tree bindings for that driver over to a YAML schema.

> 

> Cc: Mailing List <devicetree-spec@vger.kernel.org>

> Signed-off-by: Maxime Ripard <maxime@cerno.tech>

> 

> ---

> 

> Changes from v1:

>   - Fixed the license

>   - Added a mention that the file has moved

>   - Added a documentation for memory-region

>   - Split the reserved-memory binding in two: one for the generic part

>     and one for shared-dma-pool

> ---

>  .../reserved-memory/memory-region.yaml        |  40 ++++

>  .../reserved-memory/reserved-memory.txt       | 172 +-----------------

>  .../reserved-memory/reserved-memory.yaml      |  96 ++++++++++

>  .../reserved-memory/shared-dma-pool.yaml      |  87 +++++++++

>  4 files changed, 224 insertions(+), 171 deletions(-)

>  create mode 100644 Documentation/devicetree/bindings/reserved-memory/memory-region.yaml

>  create mode 100644 Documentation/devicetree/bindings/reserved-memory/reserved-memory.yaml

>  create mode 100644 Documentation/devicetree/bindings/reserved-memory/shared-dma-pool.yaml

> 


I reworked the commit msg and a couple of nits, and applied, thanks!
Rob Herring (Arm) Sept. 3, 2021, 6:12 p.m. UTC | #4
On Wed, 01 Sep 2021 11:18:06 +0200, Maxime Ripard wrote:
> The ARM CCI-400 Interconnect is supported by Linux thanks to its device

> tree binding.

> 

> Now that we have the DT validation in place, let's convert the device

> tree bindings for that driver over to a YAML schema.

> 

> Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>

> Signed-off-by: Maxime Ripard <maxime@cerno.tech>

> 

> ---

> 

> Changes from v1:

>   - Reduced the max number of interrupts

>   - Comented the pl330 compatible to avoid a warning

>   - Added cci-control-port to the cpus schemas

> ---

>  .../devicetree/bindings/arm/arm,cci-400.yaml  | 216 +++++++++++++++++

>  .../bindings/arm/cci-control-port.yaml        |  38 +++

>  Documentation/devicetree/bindings/arm/cci.txt | 224 ------------------

>  .../devicetree/bindings/arm/cpus.yaml         |   2 +

>  4 files changed, 256 insertions(+), 224 deletions(-)

>  create mode 100644 Documentation/devicetree/bindings/arm/arm,cci-400.yaml

>  create mode 100644 Documentation/devicetree/bindings/arm/cci-control-port.yaml

>  delete mode 100644 Documentation/devicetree/bindings/arm/cci.txt

> 


Applied, thanks!
Rob Herring (Arm) Sept. 3, 2021, 6:30 p.m. UTC | #5
On Wed, 01 Sep 2021 11:18:13 +0200, Maxime Ripard wrote:
> The Mitsubishi AA140XD12 Device Tree Binding was requiring a vcc-supply

> property. However, neither the existing device trees using that binding,

> nor the driver were actually using that property which is also redundant

> with power-supply. Let's just drop it.

> 

> Cc: dri-devel@lists.freedesktop.org

> Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>

> Cc: Sam Ravnborg <sam@ravnborg.org>

> Cc: Thierry Reding <thierry.reding@gmail.com>

> Signed-off-by: Maxime Ripard <maxime@cerno.tech>

> ---

>  .../bindings/display/panel/mitsubishi,aa104xd12.yaml         | 5 -----

>  1 file changed, 5 deletions(-)

> 


Acked-by: Rob Herring <robh@kernel.org>
Rob Herring (Arm) Sept. 3, 2021, 6:31 p.m. UTC | #6
On Wed, 01 Sep 2021 11:18:17 +0200, Maxime Ripard wrote:
> The Mitsubishi AA121TD01 Device Tree Binding was requiring a

> data-mapping property value which was set to another value in the

> existing Device Trees. Fix this.

> 

> Cc: dri-devel@lists.freedesktop.org

> Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>

> Cc: Sam Ravnborg <sam@ravnborg.org>

> Cc: Thierry Reding <thierry.reding@gmail.com>

> Signed-off-by: Maxime Ripard <maxime@cerno.tech>

> ---

>  .../bindings/display/panel/mitsubishi,aa121td01.yaml          | 4 ++--

>  1 file changed, 2 insertions(+), 2 deletions(-)

> 


Acked-by: Rob Herring <robh@kernel.org>
Rob Herring (Arm) Sept. 3, 2021, 7:27 p.m. UTC | #7
On Wed, 01 Sep 2021 11:18:21 +0200, Maxime Ripard wrote:
> The UBlox Neo 6M is supported by Linux thanks to its device tree

> binding.

> 

> Now that we have the DT validation in place, let's convert the device

> tree bindings for that driver over to a YAML schema.

> 

> Cc: Johan Hovold <johan@kernel.org>

> Signed-off-by: Maxime Ripard <maxime@cerno.tech>

> 

> ---

> 

> Changes from v1:

>   - Fixed a typo

>   - Fixed the example node name

> ---

>  .../bindings/gnss/u-blox,neo-6m.yaml          | 62 +++++++++++++++++++

>  .../devicetree/bindings/gnss/u-blox.txt       | 45 --------------

>  2 files changed, 62 insertions(+), 45 deletions(-)

>  create mode 100644 Documentation/devicetree/bindings/gnss/u-blox,neo-6m.yaml

>  delete mode 100644 Documentation/devicetree/bindings/gnss/u-blox.txt

> 


Applied, thanks!
Rob Herring (Arm) Sept. 3, 2021, 7:33 p.m. UTC | #8
On Wed, 01 Sep 2021 11:18:23 +0200, Maxime Ripard wrote:
> Even though we had the iio-hwmon driver for some time and a number of

> boards using it already, we never had a binding for it. Let's add it

> based on what the driver expects and the boards are providing.

> 

> Cc: Guenter Roeck <linux@roeck-us.net>

> Cc: Jean Delvare <jdelvare@suse.com>

> Cc: Jonathan Cameron <jic23@kernel.org>

> Cc: linux-hwmon@vger.kernel.org

> Signed-off-by: Maxime Ripard <maxime@cerno.tech>

> 

> ---

> 

> Changes from v1:

>   - Reduced the maximum number of io-channels, and added a comment for

>     the limitation

> ---

>  .../devicetree/bindings/hwmon/iio-hwmon.yaml  | 37 +++++++++++++++++++

>  1 file changed, 37 insertions(+)

>  create mode 100644 Documentation/devicetree/bindings/hwmon/iio-hwmon.yaml

> 


Reviewed-by: Rob Herring <robh@kernel.org>
Rob Herring (Arm) Sept. 3, 2021, 7:39 p.m. UTC | #9
On Wed, Sep 01, 2021 at 11:18:27AM +0200, Maxime Ripard wrote:
> The Omnivision OV5640 is supported by Linux thanks to its device tree

> binding.

> 

> Now that we have the DT validation in place, let's convert the device

> tree bindings for that driver over to a YAML schema.

> 

> Cc: linux-media@vger.kernel.org

> Cc: Mauro Carvalho Chehab <mchehab@kernel.org>

> Cc: Steve Longerbeam <slongerbeam@gmail.com>

> Signed-off-by: Maxime Ripard <maxime@cerno.tech>

> ---

>  .../devicetree/bindings/media/i2c/ov5640.txt  |  92 -----------

>  .../bindings/media/i2c/ovti,ov5640.yaml       | 154 ++++++++++++++++++

>  2 files changed, 154 insertions(+), 92 deletions(-)

>  delete mode 100644 Documentation/devicetree/bindings/media/i2c/ov5640.txt

>  create mode 100644 Documentation/devicetree/bindings/media/i2c/ovti,ov5640.yaml

> 

> diff --git a/Documentation/devicetree/bindings/media/i2c/ov5640.txt b/Documentation/devicetree/bindings/media/i2c/ov5640.txt

> deleted file mode 100644

> index c97c2f2da12d..000000000000

> --- a/Documentation/devicetree/bindings/media/i2c/ov5640.txt

> +++ /dev/null

> @@ -1,92 +0,0 @@

> -* Omnivision OV5640 MIPI CSI-2 / parallel sensor

> -

> -Required Properties:

> -- compatible: should be "ovti,ov5640"

> -- clocks: reference to the xclk input clock.

> -- clock-names: should be "xclk".

> -- DOVDD-supply: Digital I/O voltage supply, 1.8 volts

> -- AVDD-supply: Analog voltage supply, 2.8 volts

> -- DVDD-supply: Digital core voltage supply, 1.5 volts

> -

> -Optional Properties:

> -- reset-gpios: reference to the GPIO connected to the reset pin, if any.

> -	       This is an active low signal to the OV5640.

> -- powerdown-gpios: reference to the GPIO connected to the powerdown pin,

> -		   if any. This is an active high signal to the OV5640.

> -- rotation: as defined in

> -	    Documentation/devicetree/bindings/media/video-interfaces.txt,

> -	    valid values are 0 (sensor mounted upright) and 180 (sensor

> -	    mounted upside down).

> -

> -The device node must contain one 'port' child node for its digital output

> -video port, in accordance with the video interface bindings defined in

> -Documentation/devicetree/bindings/media/video-interfaces.txt.

> -

> -OV5640 can be connected to a MIPI CSI-2 bus or a parallel bus endpoint.

> -

> -Endpoint node required properties for CSI-2 connection are:

> -- remote-endpoint: a phandle to the bus receiver's endpoint node.

> -- clock-lanes: should be set to <0> (clock lane on hardware lane 0)

> -- data-lanes: should be set to <1> or <1 2> (one or two CSI-2 lanes supported)

> -

> -Endpoint node required properties for parallel connection are:

> -- remote-endpoint: a phandle to the bus receiver's endpoint node.

> -- bus-width: shall be set to <8> for 8 bits parallel bus

> -	     or <10> for 10 bits parallel bus

> -- data-shift: shall be set to <2> for 8 bits parallel bus

> -	      (lines 9:2 are used) or <0> for 10 bits parallel bus

> -- hsync-active: active state of the HSYNC signal, 0/1 for LOW/HIGH respectively.

> -- vsync-active: active state of the VSYNC signal, 0/1 for LOW/HIGH respectively.

> -- pclk-sample: sample data on rising (1) or falling (0) edge of the pixel clock

> -	       signal.

> -

> -Examples:

> -

> -&i2c1 {

> -	ov5640: camera@3c {

> -		compatible = "ovti,ov5640";

> -		pinctrl-names = "default";

> -		pinctrl-0 = <&pinctrl_ov5640>;

> -		reg = <0x3c>;

> -		clocks = <&clks IMX6QDL_CLK_CKO>;

> -		clock-names = "xclk";

> -		DOVDD-supply = <&vgen4_reg>; /* 1.8v */

> -		AVDD-supply = <&vgen3_reg>;  /* 2.8v */

> -		DVDD-supply = <&vgen2_reg>;  /* 1.5v */

> -		powerdown-gpios = <&gpio1 19 GPIO_ACTIVE_HIGH>;

> -		reset-gpios = <&gpio1 20 GPIO_ACTIVE_LOW>;

> -		rotation = <180>;

> -

> -		port {

> -			/* MIPI CSI-2 bus endpoint */

> -			ov5640_to_mipi_csi2: endpoint {

> -				remote-endpoint = <&mipi_csi2_from_ov5640>;

> -				clock-lanes = <0>;

> -				data-lanes = <1 2>;

> -			};

> -		};

> -	};

> -};

> -

> -&i2c1 {

> -	ov5640: camera@3c {

> -		compatible = "ovti,ov5640";

> -		pinctrl-names = "default";

> -		pinctrl-0 = <&pinctrl_ov5640>;

> -		reg = <0x3c>;

> -		clocks = <&clk_ext_camera>;

> -		clock-names = "xclk";

> -

> -		port {

> -			/* Parallel bus endpoint */

> -			ov5640_to_parallel: endpoint {

> -				remote-endpoint = <&parallel_from_ov5640>;

> -				bus-width = <8>;

> -				data-shift = <2>; /* lines 9:2 are used */

> -				hsync-active = <0>;

> -				vsync-active = <0>;

> -				pclk-sample = <1>;

> -			};

> -		};

> -	};

> -};

> diff --git a/Documentation/devicetree/bindings/media/i2c/ovti,ov5640.yaml b/Documentation/devicetree/bindings/media/i2c/ovti,ov5640.yaml

> new file mode 100644

> index 000000000000..0283b1895a75

> --- /dev/null

> +++ b/Documentation/devicetree/bindings/media/i2c/ovti,ov5640.yaml

> @@ -0,0 +1,154 @@

> +# SPDX-License-Identifier: GPL-2.0

> +%YAML 1.2

> +---

> +$id: http://devicetree.org/schemas/media/i2c/ovti,ov5640.yaml#

> +$schema: http://devicetree.org/meta-schemas/core.yaml#

> +

> +title: OmniVision OV5640 Image Sensor Device Tree Bindings

> +

> +maintainers:

> +  - Steve Longerbeam <slongerbeam@gmail.com>

> +

> +allOf:

> +  - $ref: /schemas/media/video-interface-devices.yaml#

> +

> +properties:

> +  compatible:

> +    const: ovti,ov5640

> +

> +  reg:

> +    maxItems: 1

> +

> +  clocks:

> +    description: XCLK Input Clock

> +

> +  clock-names:

> +    const: xclk

> +

> +  AVDD-supply:

> +    description: Analog voltage supply, 2.8 volts

> +

> +  DVDD-supply:

> +    description: Digital core voltage supply, 1.5 volts

> +

> +  DOVDD-supply:

> +    description: Digital I/O voltage supply, 1.8 volts

> +

> +  powerdown-gpios:

> +    maxItems: 1

> +    description: >

> +      Reference to the GPIO connected to the powerdown pin, if any.

> +

> +  reset-gpios:

> +    maxItems: 1

> +    description: >

> +      Reference to the GPIO connected to the reset pin, if any.

> +

> +  rotation:

> +    enum: 

> +      - 0

> +      - 180

> +

> +  port:

> +    description: Digital Output Port

> +    $ref: /schemas/graph.yaml#/properties/port


This needs to be /schemas/graph.yaml#/$defs/port-base

Otherwise, it will fail when we start checking unevaluatedProperties.

> +    additionalProperties: false

> +

> +    properties:

> +      endpoint:

> +        $ref: /schemas/media/video-interfaces.yaml#

> +        unevaluatedProperties: false

> +

> +        properties:

> +          clock-lanes:

> +            const: 0

> +

> +          data-lanes:

> +            minItems: 1

> +            maxItems: 2

> +            items:

> +              enum: [1, 2]

> +

> +          bus-width:

> +            enum: [8, 10]

> +

> +          data-shift:

> +            enum: [0, 2]

> +

> +required:

> +  - compatible

> +  - reg

> +  - clocks

> +  - clock-names

> +  - AVDD-supply

> +  - DVDD-supply

> +  - DOVDD-supply

> +  - port

> +

> +additionalProperties: false

> +

> +examples:

> +  - |

> +      #include <dt-bindings/clock/imx6qdl-clock.h>

> +      #include <dt-bindings/gpio/gpio.h>

> +

> +      i2c {

> +          #address-cells = <1>;

> +          #size-cells = <0>;

> +

> +          camera@3c {

> +              compatible = "ovti,ov5640";

> +              pinctrl-names = "default";

> +              pinctrl-0 = <&pinctrl_ov5640>;

> +              reg = <0x3c>;

> +              clocks = <&clks IMX6QDL_CLK_CKO>;

> +              clock-names = "xclk";

> +              DOVDD-supply = <&vgen4_reg>; /* 1.8v */

> +              AVDD-supply = <&vgen3_reg>;  /* 2.8v */

> +              DVDD-supply = <&vgen2_reg>;  /* 1.5v */

> +              powerdown-gpios = <&gpio1 19 GPIO_ACTIVE_HIGH>;

> +              reset-gpios = <&gpio1 20 GPIO_ACTIVE_LOW>;

> +              rotation = <180>;

> +

> +              port {

> +                  /* MIPI CSI-2 bus endpoint */

> +                  ov5640_to_mipi_csi2: endpoint {

> +                      remote-endpoint = <&mipi_csi2_from_ov5640>;

> +                      clock-lanes = <0>;

> +                      data-lanes = <1 2>;

> +                  };

> +              };

> +          };

> +      };

> +

> +  - |

> +      i2c {

> +          #address-cells = <1>;

> +          #size-cells = <0>;

> +

> +          camera@3c {

> +              compatible = "ovti,ov5640";

> +              pinctrl-names = "default";

> +              pinctrl-0 = <&pinctrl_ov5640>;

> +              reg = <0x3c>;

> +              clocks = <&clk_ext_camera>;

> +              clock-names = "xclk";

> +              DOVDD-supply = <&vgen4_reg>; /* 1.8v */

> +              AVDD-supply = <&vgen3_reg>;  /* 2.8v */

> +              DVDD-supply = <&vgen2_reg>;  /* 1.5v */

> +

> +              port {

> +                  /* Parallel bus endpoint */

> +                  ov5640_to_parallel: endpoint {

> +                      remote-endpoint = <&parallel_from_ov5640>;

> +                      bus-width = <8>;

> +                      data-shift = <2>; /* lines 9:2 are used */

> +                      hsync-active = <0>;

> +                      vsync-active = <0>;

> +                      pclk-sample = <1>;

> +                  };

> +              };

> +          };

> +      };

> +

> +...

> -- 

> 2.31.1

> 

>
Rob Herring (Arm) Sept. 3, 2021, 7:44 p.m. UTC | #10
On Wed, 01 Sep 2021 11:18:29 +0200, Maxime Ripard wrote:
> The X-Powers AXP PMICs are supported by Linux thanks to its device tree

> binding.

> 

> Now that we have the DT validation in place, let's convert the device

> tree bindings for that driver over to a YAML schema.

> 

> Cc: Chen-Yu Tsai <wens@csie.org>

> Cc: Lee Jones <lee.jones@linaro.org>

> Signed-off-by: Maxime Ripard <maxime@cerno.tech>

> 

> ---

> 

> Changes from v1:

>   - Add GPIO example

>   - Remove the limitation on regulator-ramp-delay

> ---

>  .../i2c/allwinner,sun6i-a31-p2wi.yaml         |   2 +-

>  .../devicetree/bindings/mfd/axp20x.txt        | 273 ------------

>  .../bindings/mfd/x-powers,axp152.yaml         | 400 ++++++++++++++++++

>  3 files changed, 401 insertions(+), 274 deletions(-)

>  delete mode 100644 Documentation/devicetree/bindings/mfd/axp20x.txt

>  create mode 100644 Documentation/devicetree/bindings/mfd/x-powers,axp152.yaml

> 


Reviewed-by: Rob Herring <robh@kernel.org>


Note that the gpio child schema needs to be applied with this one.
Rob Herring (Arm) Sept. 3, 2021, 7:47 p.m. UTC | #11
On Wed, 01 Sep 2021 11:18:36 +0200, Maxime Ripard wrote:
> The SMSC USB3503 USB Hub Controller is supported by Linux thanks to

> its device tree binding.

> 

> Now that we have the DT validation in place, let's convert the device

> tree bindings for that driver over to a YAML schema.

> 

> Cc: Dongjin Kim <tobetter@gmail.com>

> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

> Cc: linux-usb@vger.kernel.org

> Signed-off-by: Maxime Ripard <maxime@cerno.tech>

> 

> ---

> 

> Changes from v1:

>   - Added maximum number of items for clocks and gpios

>   - Fixed the example node name

> ---

>  .../devicetree/bindings/usb/smsc,usb3503.yaml | 108 ++++++++++++++++++

>  .../devicetree/bindings/usb/usb3503.txt       |  39 -------

>  2 files changed, 108 insertions(+), 39 deletions(-)

>  create mode 100644 Documentation/devicetree/bindings/usb/smsc,usb3503.yaml

>  delete mode 100644 Documentation/devicetree/bindings/usb/usb3503.txt

> 


Reviewed-by: Rob Herring <robh@kernel.org>
Rob Herring (Arm) Sept. 3, 2021, 7:50 p.m. UTC | #12
On Wed, 01 Sep 2021 11:18:38 +0200, Maxime Ripard wrote:
> Bitbanged 1-Wire buses are supported by Linux thanks to their device

> tree binding.

> 

> Now that we have the DT validation in place, let's convert the device

> tree bindings for that driver over to a YAML schema.

> 

> Cc: Daniel Mack <zonque@gmail.com>

> Cc: Evgeniy Polyakov <zbr@ioremap.net>

> Signed-off-by: Maxime Ripard <maxime@cerno.tech>

> 

> ---

> 

> Changes from v1:

>   - Changed additionalproperties to make sure all the other items in the

>     schema are nodes

> ---

>  .../devicetree/bindings/w1/w1-gpio.txt        | 27 ------------

>  .../devicetree/bindings/w1/w1-gpio.yaml       | 44 +++++++++++++++++++

>  2 files changed, 44 insertions(+), 27 deletions(-)

>  delete mode 100644 Documentation/devicetree/bindings/w1/w1-gpio.txt

>  create mode 100644 Documentation/devicetree/bindings/w1/w1-gpio.yaml

> 


Applied, thanks!
Guenter Roeck Sept. 4, 2021, 3:03 p.m. UTC | #13
On Wed, Sep 01, 2021 at 11:18:23AM +0200, Maxime Ripard wrote:
> Even though we had the iio-hwmon driver for some time and a number of

> boards using it already, we never had a binding for it. Let's add it

> based on what the driver expects and the boards are providing.

> 

> Cc: Guenter Roeck <linux@roeck-us.net>

> Cc: Jean Delvare <jdelvare@suse.com>

> Cc: Jonathan Cameron <jic23@kernel.org>

> Cc: linux-hwmon@vger.kernel.org

> Signed-off-by: Maxime Ripard <maxime@cerno.tech>

> Reviewed-by: Rob Herring <robh@kernel.org>


Applied (assuming this is supposed to be pushed through hwmon).

Thanks,
Guenter
Jernej Škrabec Sept. 5, 2021, 8:50 p.m. UTC | #14
Dne sreda, 01. september 2021 ob 11:18:09 CEST je Maxime Ripard napisal(a):
> Even though both the driver and the device trees all use the

> allwinner,sun50i-h6-de3-clk, we documented the compatible as

> allwinner,sun50i-h6-de2-clk in the binding. Let's fix this.

> 

> Reviewed-by: Rob Herring <robh@kernel.org>

> Signed-off-by: Maxime Ripard <maxime@cerno.tech>


Reviewed-by: Jernej Skrabec <jernej.skrabec@gmail.com>


Best regards,
Jernej
Jernej Škrabec Sept. 5, 2021, 8:53 p.m. UTC | #15
Dne sreda, 01. september 2021 ob 11:18:25 CEST je Maxime Ripard napisal(a):
> The R40 MBUS compatible was introduced recently but it was never

> documented.

> 

> Reviewed-by: Rob Herring <robh@kernel.org>

> Signed-off-by: Maxime Ripard <maxime@cerno.tech>


Reviewed-by: Jernej Skrabec <jernej.skrabec@gmail.com>


Best regards,
Jernej
Jernej Škrabec Sept. 5, 2021, 8:56 p.m. UTC | #16
Dne sreda, 01. september 2021 ob 11:18:31 CEST je Maxime Ripard napisal(a):
> Even though both the driver and the device trees all use the

> allwinner,sun8i-r40-gmac compatible, we documented the compatible as

> allwinner,sun8i-r40-emac in the binding. Let's fix this.

> 

> Cc: Alexandre Torgue <alexandre.torgue@st.com>

> Cc: "David S. Miller" <davem@davemloft.net>

> Cc: Giuseppe Cavallaro <peppe.cavallaro@st.com>

> Cc: Jakub Kicinski <kuba@kernel.org>

> Cc: Jose Abreu <joabreu@synopsys.com>

> Cc: netdev@vger.kernel.org

> Reviewed-by: Rob Herring <robh@kernel.org>

> Signed-off-by: Maxime Ripard <maxime@cerno.tech>


Reviewed-by: Jernej Skrabec <jernej.skrabec@gmail.com>


Best regards,
Jernej
Jernej Škrabec Sept. 5, 2021, 9:01 p.m. UTC | #17
Dne sreda, 01. september 2021 ob 11:18:35 CEST je Maxime Ripard napisal(a):
> Even though we've used the A80 PRCM driver for some time and a number of

> boards using it already, we never had a binding for it. Let's add it

> based on what the driver expects and the boards are providing.

> 

> Reviewed-by: Rob Herring <robh@kernel.org>

> Signed-off-by: Maxime Ripard <maxime@cerno.tech>


Reviewed-by: Jernej Skrabec <jernej.skrabec@gmail.com>


Best regards,
Jernej
Jernej Škrabec Sept. 5, 2021, 9:04 p.m. UTC | #18
Dne sreda, 01. september 2021 ob 11:18:41 CEST je Maxime Ripard napisal(a):
> Even though it translates to the same thing down to the binary level, we

> should have an array of 2 number cells to describe each OPP, which in

> turns create a validation warning.

> 

> Let's fix this.

> 

> Signed-off-by: Maxime Ripard <maxime@cerno.tech>


Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com>


Best regards,
Jernej
Jernej Škrabec Sept. 5, 2021, 9:05 p.m. UTC | #19
Dne sreda, 01. september 2021 ob 11:18:42 CEST je Maxime Ripard napisal(a):
> The operating-points-v2 nodes are named inconsistently, but mostly

> either opp_table0 or gpu-opp-table.  However, the underscore is an

> invalid character for a node name and the thermal zone binding

> explicitly requires that zones are called opp-table-*. Let's fix it.

> 

> Signed-off-by: Maxime Ripard <maxime@cerno.tech>


Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com>


Best regards,
Jernej
Jernej Škrabec Sept. 5, 2021, 9:06 p.m. UTC | #20
Dne sreda, 01. september 2021 ob 11:18:43 CEST je Maxime Ripard napisal(a):
> According to the SPI NOR bindings, the flash node names are supposed to

> be flash@<address>. Let's fix our users to use that new scheme.

> 

> Signed-off-by: Maxime Ripard <maxime@cerno.tech>


Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com>


Best regards,
Jernej
Jernej Škrabec Sept. 5, 2021, 9:11 p.m. UTC | #21
Dne sreda, 01. september 2021 ob 11:18:45 CEST je Maxime Ripard napisal(a):
> The edt,edt-ft5x06 compatible has never been a valid compatible

> according to the binding. Let's change for one that is.

> 

> Signed-off-by: Maxime Ripard <maxime@cerno.tech>


Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com>


Best regards,
Jernej
Jernej Škrabec Sept. 5, 2021, 9:12 p.m. UTC | #22
Dne sreda, 01. september 2021 ob 11:18:47 CEST je Maxime Ripard napisal(a):
> The GPU thermal zone is named gpu_thermal. However, the underscore is

> an invalid character for a node name and the thermal zone binding

> explicitly requires that zones are called *-thermal. Let's fix it.

> 

> Signed-off-by: Maxime Ripard <maxime@cerno.tech>


Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com>


Best regards,
Jernej
Jernej Škrabec Sept. 5, 2021, 9:13 p.m. UTC | #23
Dne sreda, 01. september 2021 ob 11:18:49 CEST je Maxime Ripard napisal(a):
> The thermal zones one the A100 are called $device-thermal-zone.

> 

> However, the thermal zone binding explicitly requires that zones are

> called *-thermal. Let's fix it.

> 

> Signed-off-by: Maxime Ripard <maxime@cerno.tech>



Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com>


Best regards,
Jernej
Jernej Škrabec Sept. 5, 2021, 9:14 p.m. UTC | #24
Dne sreda, 01. september 2021 ob 11:18:51 CEST je Maxime Ripard napisal(a):
> The anx6345 bridge mandates that the input port is named port@0. Since

> we have a unit-address, this implies that we need a reg property with

> the same value, but it was found to be missing in the Teres-I device

> tree. Make sure it's there.

> 

> Signed-off-by: Maxime Ripard <maxime@cerno.tech>


Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com>


Best regards,
Jernej
Lee Jones Sept. 6, 2021, 9:02 a.m. UTC | #25
On Fri, 03 Sep 2021, Rob Herring wrote:

> On Wed, 01 Sep 2021 11:18:29 +0200, Maxime Ripard wrote:

> > The X-Powers AXP PMICs are supported by Linux thanks to its device tree

> > binding.

> > 

> > Now that we have the DT validation in place, let's convert the device

> > tree bindings for that driver over to a YAML schema.

> > 

> > Cc: Chen-Yu Tsai <wens@csie.org>

> > Cc: Lee Jones <lee.jones@linaro.org>

> > Signed-off-by: Maxime Ripard <maxime@cerno.tech>

> > 

> > ---

> > 

> > Changes from v1:

> >   - Add GPIO example

> >   - Remove the limitation on regulator-ramp-delay

> > ---

> >  .../i2c/allwinner,sun6i-a31-p2wi.yaml         |   2 +-

> >  .../devicetree/bindings/mfd/axp20x.txt        | 273 ------------

> >  .../bindings/mfd/x-powers,axp152.yaml         | 400 ++++++++++++++++++

> >  3 files changed, 401 insertions(+), 274 deletions(-)

> >  delete mode 100644 Documentation/devicetree/bindings/mfd/axp20x.txt

> >  create mode 100644 Documentation/devicetree/bindings/mfd/x-powers,axp152.yaml

> > 

> 

> Reviewed-by: Rob Herring <robh@kernel.org>

> 

> Note that the gpio child schema needs to be applied with this one.


Not sure I'm in possession of that.

-- 
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
Maxime Ripard Sept. 6, 2021, 1:34 p.m. UTC | #26
On Sun, Sep 05, 2021 at 10:50:32PM +0200, Jernej Škrabec wrote:
> Dne sreda, 01. september 2021 ob 11:18:09 CEST je Maxime Ripard napisal(a):

> > Even though both the driver and the device trees all use the

> > allwinner,sun50i-h6-de3-clk, we documented the compatible as

> > allwinner,sun50i-h6-de2-clk in the binding. Let's fix this.

> > 

> > Reviewed-by: Rob Herring <robh@kernel.org>

> > Signed-off-by: Maxime Ripard <maxime@cerno.tech>

> 

> Reviewed-by: Jernej Skrabec <jernej.skrabec@gmail.com>


Applied, thanks
Maxime
Maxime Ripard Sept. 6, 2021, 1:36 p.m. UTC | #27
On Sun, Sep 05, 2021 at 11:01:17PM +0200, Jernej Škrabec wrote:
> Dne sreda, 01. september 2021 ob 11:18:35 CEST je Maxime Ripard napisal(a):

> > Even though we've used the A80 PRCM driver for some time and a number of

> > boards using it already, we never had a binding for it. Let's add it

> > based on what the driver expects and the boards are providing.

> > 

> > Reviewed-by: Rob Herring <robh@kernel.org>

> > Signed-off-by: Maxime Ripard <maxime@cerno.tech>

> 

> Reviewed-by: Jernej Skrabec <jernej.skrabec@gmail.com>


Applied, thanks
Maxime
Maxime Ripard Sept. 6, 2021, 1:37 p.m. UTC | #28
On Sun, Sep 05, 2021 at 11:04:59PM +0200, Jernej Škrabec wrote:
> Dne sreda, 01. september 2021 ob 11:18:41 CEST je Maxime Ripard napisal(a):

> > Even though it translates to the same thing down to the binary level, we

> > should have an array of 2 number cells to describe each OPP, which in

> > turns create a validation warning.

> > 

> > Let's fix this.

> > 

> > Signed-off-by: Maxime Ripard <maxime@cerno.tech>

> 

> Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com>


Applied, thanks
Maxime Ripard Sept. 6, 2021, 1:38 p.m. UTC | #29
On Sun, Sep 05, 2021 at 11:05:58PM +0200, Jernej Škrabec wrote:
> Dne sreda, 01. september 2021 ob 11:18:42 CEST je Maxime Ripard napisal(a):

> > The operating-points-v2 nodes are named inconsistently, but mostly

> > either opp_table0 or gpu-opp-table.  However, the underscore is an

> > invalid character for a node name and the thermal zone binding

> > explicitly requires that zones are called opp-table-*. Let's fix it.

> > 

> > Signed-off-by: Maxime Ripard <maxime@cerno.tech>

> 

> Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com>


Applied, thanks
Maxime
Maxime Ripard Sept. 6, 2021, 1:38 p.m. UTC | #30
On Sun, Sep 05, 2021 at 11:06:45PM +0200, Jernej Škrabec wrote:
> Dne sreda, 01. september 2021 ob 11:18:43 CEST je Maxime Ripard napisal(a):

> > According to the SPI NOR bindings, the flash node names are supposed to

> > be flash@<address>. Let's fix our users to use that new scheme.

> > 

> > Signed-off-by: Maxime Ripard <maxime@cerno.tech>

> 

> Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com>


Applied, thanks
Maxime
Maxime Ripard Sept. 6, 2021, 1:38 p.m. UTC | #31
On Sun, Sep 05, 2021 at 11:11:58PM +0200, Jernej Škrabec wrote:
> Dne sreda, 01. september 2021 ob 11:18:45 CEST je Maxime Ripard napisal(a):

> > The edt,edt-ft5x06 compatible has never been a valid compatible

> > according to the binding. Let's change for one that is.

> > 

> > Signed-off-by: Maxime Ripard <maxime@cerno.tech>

> 

> Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com>


Applied, thanks
Maxime
Maxime Ripard Sept. 6, 2021, 1:39 p.m. UTC | #32
On Sun, Sep 05, 2021 at 11:12:51PM +0200, Jernej Škrabec wrote:
> Dne sreda, 01. september 2021 ob 11:18:47 CEST je Maxime Ripard napisal(a):

> > The GPU thermal zone is named gpu_thermal. However, the underscore is

> > an invalid character for a node name and the thermal zone binding

> > explicitly requires that zones are called *-thermal. Let's fix it.

> > 

> > Signed-off-by: Maxime Ripard <maxime@cerno.tech>

> 

> Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com>


Applied, thanks
Maxime
Maxime Ripard Sept. 6, 2021, 1:40 p.m. UTC | #33
On Sun, Sep 05, 2021 at 11:13:46PM +0200, Jernej Škrabec wrote:
> Dne sreda, 01. september 2021 ob 11:18:49 CEST je Maxime Ripard napisal(a):

> > The thermal zones one the A100 are called $device-thermal-zone.

> > 

> > However, the thermal zone binding explicitly requires that zones are

> > called *-thermal. Let's fix it.

> > 

> > Signed-off-by: Maxime Ripard <maxime@cerno.tech>

> 

> 

> Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com>


Applied, thanks
Maxime
Maxime Ripard Sept. 6, 2021, 1:41 p.m. UTC | #34
On Sun, Sep 05, 2021 at 11:14:34PM +0200, Jernej Škrabec wrote:
> Dne sreda, 01. september 2021 ob 11:18:51 CEST je Maxime Ripard napisal(a):

> > The anx6345 bridge mandates that the input port is named port@0. Since

> > we have a unit-address, this implies that we need a reg property with

> > the same value, but it was found to be missing in the Teres-I device

> > tree. Make sure it's there.

> > 

> > Signed-off-by: Maxime Ripard <maxime@cerno.tech>

> 

> Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com>


Applied, thanks
Maxime
Mark Brown Sept. 13, 2021, 10:53 a.m. UTC | #35
On Wed, 1 Sep 2021 11:18:00 +0200, Maxime Ripard wrote:
> Here's another round of schema warnings fixes for the Allwinner platform.

> 

> There's a fair share of new schemas in there since the schema tools now warn

> when a compatible is not documented in a schema.

> 

> We don't have any warning anymore if we use the OPP binding Rob submitted, and

> since that means we have all our devices properly validated I don't expect more

> fixes now, aside from the usual bunch of regressions.

> 

> [...]


Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[01/52] ASoC: dt-bindings: Add WM8978 Binding
        commit: 5bd5699c494f42a3c23e377bb35be5d716b85012
[02/52] ASoC: dt-bindings: Convert Bluetooth SCO Link binding to a schema
        commit: 6ef239699102580b104bfca11d9b94abfbc8caec
[03/52] ASoC: dt-bindings: Convert SPDIF Transmitter binding to a schema
        commit: 1c02b74ba20838ba194850beb0adfc6b5e11bb2a
[04/52] ASoC: dt-bindings: Convert Simple Amplifier binding to a schema
        commit: 50a41ce8c56d07f42a97112077acbaeda8b86ed9

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark
Maxime Ripard Sept. 14, 2021, 7:12 a.m. UTC | #36
On Mon, Sep 06, 2021 at 10:02:26AM +0100, Lee Jones wrote:
> On Fri, 03 Sep 2021, Rob Herring wrote:

> 

> > On Wed, 01 Sep 2021 11:18:29 +0200, Maxime Ripard wrote:

> > > The X-Powers AXP PMICs are supported by Linux thanks to its device tree

> > > binding.

> > > 

> > > Now that we have the DT validation in place, let's convert the device

> > > tree bindings for that driver over to a YAML schema.

> > > 

> > > Cc: Chen-Yu Tsai <wens@csie.org>

> > > Cc: Lee Jones <lee.jones@linaro.org>

> > > Signed-off-by: Maxime Ripard <maxime@cerno.tech>

> > > 

> > > ---

> > > 

> > > Changes from v1:

> > >   - Add GPIO example

> > >   - Remove the limitation on regulator-ramp-delay

> > > ---

> > >  .../i2c/allwinner,sun6i-a31-p2wi.yaml         |   2 +-

> > >  .../devicetree/bindings/mfd/axp20x.txt        | 273 ------------

> > >  .../bindings/mfd/x-powers,axp152.yaml         | 400 ++++++++++++++++++

> > >  3 files changed, 401 insertions(+), 274 deletions(-)

> > >  delete mode 100644 Documentation/devicetree/bindings/mfd/axp20x.txt

> > >  create mode 100644 Documentation/devicetree/bindings/mfd/x-powers,axp152.yaml

> > > 

> > 

> > Reviewed-by: Rob Herring <robh@kernel.org>

> > 

> > Note that the gpio child schema needs to be applied with this one.

> 

> Not sure I'm in possession of that.


So, how do you want to merge that? Through the DT tree?

Maxime
Rob Herring (Arm) Sept. 14, 2021, 12:57 p.m. UTC | #37
On Tue, Sep 14, 2021 at 2:12 AM Maxime Ripard <maxime@cerno.tech> wrote:
>

> On Mon, Sep 06, 2021 at 10:02:26AM +0100, Lee Jones wrote:

> > On Fri, 03 Sep 2021, Rob Herring wrote:

> >

> > > On Wed, 01 Sep 2021 11:18:29 +0200, Maxime Ripard wrote:

> > > > The X-Powers AXP PMICs are supported by Linux thanks to its device tree

> > > > binding.

> > > >

> > > > Now that we have the DT validation in place, let's convert the device

> > > > tree bindings for that driver over to a YAML schema.

> > > >

> > > > Cc: Chen-Yu Tsai <wens@csie.org>

> > > > Cc: Lee Jones <lee.jones@linaro.org>

> > > > Signed-off-by: Maxime Ripard <maxime@cerno.tech>

> > > >

> > > > ---

> > > >

> > > > Changes from v1:

> > > >   - Add GPIO example

> > > >   - Remove the limitation on regulator-ramp-delay

> > > > ---

> > > >  .../i2c/allwinner,sun6i-a31-p2wi.yaml         |   2 +-

> > > >  .../devicetree/bindings/mfd/axp20x.txt        | 273 ------------

> > > >  .../bindings/mfd/x-powers,axp152.yaml         | 400 ++++++++++++++++++

> > > >  3 files changed, 401 insertions(+), 274 deletions(-)

> > > >  delete mode 100644 Documentation/devicetree/bindings/mfd/axp20x.txt

> > > >  create mode 100644 Documentation/devicetree/bindings/mfd/x-powers,axp152.yaml

> > > >

> > >

> > > Reviewed-by: Rob Herring <robh@kernel.org>

> > >

> > > Note that the gpio child schema needs to be applied with this one.

> >

> > Not sure I'm in possession of that.

>

> So, how do you want to merge that? Through the DT tree?


Resend the MFD and child patches in a series to Lee.

Rob