linux-watchdog.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Johan Jonker <jbx6244@gmail.com>
Cc: linux-mmc@vger.kernel.org, linux-rockchip@lists.infradead.org,
	vkoul@kernel.org, gregkh@linuxfoundation.org,
	wim@linux-watchdog.org, broonie@kernel.org, sjg@chromium.org,
	linux@roeck-us.net, linux-watchdog@vger.kernel.org,
	linux-mtd@lists.infradead.org, linux-serial@vger.kernel.org,
	richard@nod.at, kever.yang@rock-chips.com,
	zhangqing@rock-chips.com, vigneshr@ti.com, jamie@jamieiles.com,
	linux-pwm@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org,
	heiko@sntech.de, linux-arm-kernel@lists.infradead.org,
	robh+dt@kernel.org, miquel.raynal@bootlin.com,
	u.kleine-koenig@pengutronix.de, linux-usb@vger.kernel.org,
	linux-i2c@vger.kernel.org, ulf.hansson@linaro.org, kishon@ti.com,
	devicetree@vger.kernel.org, thierry.reding@gmail.com,
	linux-kernel@vger.kernel.org, philipp.tomsich@vrull.eu,
	linux-spi@vger.kernel.org, linux-phy@lists.infradead.org
Subject: Re: [PATCH v1 05/11] dt-bindings: spi: rockchip: add rockchip,rk3128-spi
Date: Sat, 10 Sep 2022 09:53:55 -0500	[thread overview]
Message-ID: <1662821635.172121.34698.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <c05fb9a3-ebf7-adec-e8ca-bd137d157f50@gmail.com>

On Sat, 10 Sep 2022 00:02:07 +0200, Johan Jonker wrote:
> Add rockchip,rk3128-spi compatible string.
> 
> Signed-off-by: Johan Jonker <jbx6244@gmail.com>
> ---
>  Documentation/devicetree/bindings/spi/spi-rockchip.yaml | 1 +
>  1 file changed, 1 insertion(+)
> 

Running 'make dtbs_check' with the schema in this patch gives the
following warnings. Consider if they are expected or the schema is
incorrect. These may not be new warnings.

Note that it is not yet a requirement to have 0 warnings for dtbs_check.
This will change in the future.

Full log is available here: https://patchwork.ozlabs.org/patch/


spi@ff1d0000: Unevaluated properties are not allowed ('max-freq' was unexpected)
	arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dtb

spi@ff200000: Unevaluated properties are not allowed ('power-domains' was unexpected)
	arch/arm64/boot/dts/rockchip/rk3399-evb.dtb
	arch/arm64/boot/dts/rockchip/rk3399-ficus.dtb
	arch/arm64/boot/dts/rockchip/rk3399-firefly.dtb
	arch/arm64/boot/dts/rockchip/rk3399-gru-bob.dtb
	arch/arm64/boot/dts/rockchip/rk3399-gru-kevin.dtb
	arch/arm64/boot/dts/rockchip/rk3399-gru-scarlet-dumo.dtb
	arch/arm64/boot/dts/rockchip/rk3399-gru-scarlet-inx.dtb
	arch/arm64/boot/dts/rockchip/rk3399-gru-scarlet-kd.dtb
	arch/arm64/boot/dts/rockchip/rk3399-hugsun-x99.dtb
	arch/arm64/boot/dts/rockchip/rk3399-khadas-edge-captain.dtb
	arch/arm64/boot/dts/rockchip/rk3399-khadas-edge.dtb
	arch/arm64/boot/dts/rockchip/rk3399-khadas-edge-v.dtb
	arch/arm64/boot/dts/rockchip/rk3399-kobol-helios64.dtb
	arch/arm64/boot/dts/rockchip/rk3399-leez-p710.dtb
	arch/arm64/boot/dts/rockchip/rk3399-nanopc-t4.dtb
	arch/arm64/boot/dts/rockchip/rk3399-nanopi-m4b.dtb
	arch/arm64/boot/dts/rockchip/rk3399-nanopi-m4.dtb
	arch/arm64/boot/dts/rockchip/rk3399-nanopi-neo4.dtb
	arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dtb
	arch/arm64/boot/dts/rockchip/rk3399-orangepi.dtb
	arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dtb
	arch/arm64/boot/dts/rockchip/rk3399pro-rock-pi-n10.dtb
	arch/arm64/boot/dts/rockchip/rk3399-puma-haikou.dtb
	arch/arm64/boot/dts/rockchip/rk3399-rock960.dtb
	arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4a.dtb
	arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4a-plus.dtb
	arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4b.dtb
	arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4b-plus.dtb
	arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4c.dtb
	arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dtb
	arch/arm64/boot/dts/rockchip/rk3399-rockpro64-v2.dtb
	arch/arm64/boot/dts/rockchip/rk3399-roc-pc.dtb
	arch/arm64/boot/dts/rockchip/rk3399-roc-pc-mezzanine.dtb
	arch/arm64/boot/dts/rockchip/rk3399-roc-pc-plus.dtb
	arch/arm64/boot/dts/rockchip/rk3399-sapphire.dtb
	arch/arm64/boot/dts/rockchip/rk3399-sapphire-excavator.dtb


  reply	other threads:[~2022-09-10 14:54 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220909212543.17428-1-jbx6244@gmail.com>
2022-09-09 22:01 ` [PATCH v1 11/11] dt-bindings: mtd: rockchip: add rockchip,rk3128-nfc Johan Jonker
2022-09-10  7:46   ` Krzysztof Kozlowski
2022-09-09 22:01 ` [PATCH v1 01/11] dt-bindings: serial: rockchip: add rockchip,rk3128-uart Johan Jonker
2022-09-10 15:42   ` (subset) " Mark Brown
2022-09-13 14:05   ` Rob Herring
2022-09-13 14:37   ` Jamie Iles
2022-09-14  8:52   ` (subset) " Heiko Stuebner
2022-09-09 22:01 ` [PATCH v1 10/11] dt-bindings: soc: rockchip: grf: add rockchip,rk3128-grf Johan Jonker
2022-09-13 14:06   ` Rob Herring
2022-09-09 22:01 ` [PATCH v1 09/11] dt-bindings: phy: phy-rockchip-inno-usb2: add rockchip,rk3128-usb2phy Johan Jonker
2022-09-13 14:06   ` Rob Herring
2022-09-13 16:42   ` Vinod Koul
2022-09-09 22:01 ` [PATCH v1 08/11] dt-bindings: arm: rockchip: pmu: add rockchip,rk3128-pmu Johan Jonker
2022-09-13 14:06   ` Rob Herring
2022-09-09 22:01 ` [PATCH v1 07/11] dt-bindings: watchdog: rockchip: add rockchip,rk3128-wdt Johan Jonker
2022-09-10 14:30   ` Guenter Roeck
2022-09-13 14:06   ` Rob Herring
2022-09-09 22:02 ` [PATCH v1 06/11] dt-bindings: usb: dwc2: rockchip: add rockchip,rk3128-usb Johan Jonker
2022-09-13 14:06   ` Rob Herring
2022-09-09 22:02 ` [PATCH v1 05/11] dt-bindings: spi: rockchip: add rockchip,rk3128-spi Johan Jonker
2022-09-10 14:53   ` Rob Herring [this message]
2022-09-09 22:02 ` [PATCH v1 04/11] dt-bindings: mmc: rockchip: add rockchip,rk3128-dw-mshc Johan Jonker
2022-09-13 14:15   ` Rob Herring
2022-09-14 14:00   ` Ulf Hansson
2022-09-09 22:02 ` [PATCH v1 03/11] dt-bindings: pwm: rockchip: add rockchip,rk3128-pwm Johan Jonker
2022-09-10 14:53   ` Rob Herring
2022-09-12  8:35   ` Uwe Kleine-König
2022-09-13 14:26   ` Rob Herring
2022-09-20  6:21   ` Uwe Kleine-König
2022-09-23 10:22     ` Heiko Stuebner
2022-09-09 22:02 ` [PATCH v1 02/11] dt-bindings: i2c: rockchip: add rockchip,rk3128-i2c Johan Jonker
2022-09-13 14:26   ` Rob Herring
2022-09-16 19:57   ` Wolfram Sang

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=1662821635.172121.34698.nullmailer@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=heiko@sntech.de \
    --cc=jamie@jamieiles.com \
    --cc=jbx6244@gmail.com \
    --cc=kever.yang@rock-chips.com \
    --cc=kishon@ti.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=miquel.raynal@bootlin.com \
    --cc=philipp.tomsich@vrull.eu \
    --cc=richard@nod.at \
    --cc=robh+dt@kernel.org \
    --cc=sjg@chromium.org \
    --cc=thierry.reding@gmail.com \
    --cc=u.kleine-koenig@pengutronix.de \
    --cc=ulf.hansson@linaro.org \
    --cc=vigneshr@ti.com \
    --cc=vkoul@kernel.org \
    --cc=wim@linux-watchdog.org \
    --cc=zhangqing@rock-chips.com \
    /path/to/YOUR_REPLY

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

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