linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: davem@davemloft.net, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, Peng Fan <peng.fan@nxp.com>,
	pabeni@redhat.com, krzk+dt@kernel.org,
	linux-arm-kernel@lists.infradead.org, s.hauer@pengutronix.de,
	mkl@pengutronix.de, netdev@vger.kernel.org, robh+dt@kernel.org,
	kuba@kernel.org, linux-imx@nxp.com, shawnguo@kernel.org,
	festevam@gmail.com, linux-can@vger.kernel.org,
	kernel@pengutronix.de, qiangqing.zhang@nxp.com,
	ulf.hansson@linaro.org, linux-mmc@vger.kernel.org,
	wg@grandegger.com
Subject: Re: [PATCH 2/4] dt-bindings: net: fsl,fec: introduce nvmem property
Date: Thu, 24 Mar 2022 09:18:08 -0500	[thread overview]
Message-ID: <1648131488.609060.1995384.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <20220324042024.26813-3-peng.fan@oss.nxp.com>

On Thu, 24 Mar 2022 12:20:22 +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
> 
> To i.MX8M Family variants, fec maybe fused out. Bootloader could use
> this property to read out the fuse value and mark the node status
> at runtime.
> 
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
>  Documentation/devicetree/bindings/net/fsl,fec.yaml | 9 +++++++++
>  1 file changed, 9 insertions(+)
> 

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/1608877


ethernet@2188000: More than one condition true in oneOf schema:
	arch/arm/boot/dts/imx6dl-mba6a.dt.yaml
	arch/arm/boot/dts/imx6dl-nit6xlite.dt.yaml
	arch/arm/boot/dts/imx6dl-nitrogen6x.dt.yaml
	arch/arm/boot/dts/imx6dl-riotboard.dt.yaml
	arch/arm/boot/dts/imx6dl-sabreauto.dt.yaml
	arch/arm/boot/dts/imx6dl-ts7970.dt.yaml
	arch/arm/boot/dts/imx6q-arm2.dt.yaml
	arch/arm/boot/dts/imx6q-evi.dt.yaml
	arch/arm/boot/dts/imx6q-mba6a.dt.yaml
	arch/arm/boot/dts/imx6q-mccmon6.dt.yaml
	arch/arm/boot/dts/imx6q-nitrogen6_max.dt.yaml
	arch/arm/boot/dts/imx6q-nitrogen6_som2.dt.yaml
	arch/arm/boot/dts/imx6q-nitrogen6x.dt.yaml
	arch/arm/boot/dts/imx6qp-nitrogen6_max.dt.yaml
	arch/arm/boot/dts/imx6qp-nitrogen6_som2.dt.yaml
	arch/arm/boot/dts/imx6qp-sabreauto.dt.yaml
	arch/arm/boot/dts/imx6q-sabreauto.dt.yaml
	arch/arm/boot/dts/imx6q-ts7970.dt.yaml

ethernet@30be0000: nvmem-cell-names:0: 'fused' was expected
	arch/arm64/boot/dts/freescale/imx8mm-beacon-kit.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mm-ddr4-evk.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mm-evk.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mm-icore-mx8mm-ctouch2.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mm-icore-mx8mm-edimm2.2.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mm-kontron-n801x-s.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mm-nitrogen-r2.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mm-tqma8mqml-mba8mx.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mm-var-som-symphony.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mm-venice-gw71xx-0x.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mm-venice-gw72xx-0x.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mm-venice-gw73xx-0x.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mm-venice-gw7901.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mm-venice-gw7902.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mn-beacon-kit.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mn-bsh-smm-s2.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mn-bsh-smm-s2pro.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mn-ddr4-evk.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mn-evk.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mn-tqma8mqnl-mba8mx.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mn-var-som-symphony.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mn-venice-gw7902.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mp-evk.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mp-phyboard-pollux-rdk.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mq-evk.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mq-hummingboard-pulse.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mq-kontron-pitx-imx8m.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mq-librem5-devkit.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mq-librem5-r2.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mq-librem5-r3.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mq-librem5-r4.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mq-mnt-reform2.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mq-nitrogen.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mq-phanbell.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mq-pico-pi.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mq-thor96.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mq-tqma8mq-mba8mx.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mq-zii-ultra-rmb3.dt.yaml
	arch/arm64/boot/dts/freescale/imx8mq-zii-ultra-zest.dt.yaml

ethernet@30be0000: 'phy-connection-type' does not match any of the regexes: 'pinctrl-[0-9]+'
	arch/arm64/boot/dts/freescale/imx8mm-kontron-n801x-s.dt.yaml

ethernet@5b040000: 'power-domains' does not match any of the regexes: 'pinctrl-[0-9]+'
	arch/arm64/boot/dts/freescale/imx8qm-mek.dt.yaml
	arch/arm64/boot/dts/freescale/imx8qxp-ai_ml.dt.yaml
	arch/arm64/boot/dts/freescale/imx8qxp-colibri-eval-v3.dt.yaml
	arch/arm64/boot/dts/freescale/imx8qxp-mek.dt.yaml

ethernet@5b050000: 'power-domains' does not match any of the regexes: 'pinctrl-[0-9]+'
	arch/arm64/boot/dts/freescale/imx8qm-mek.dt.yaml
	arch/arm64/boot/dts/freescale/imx8qxp-ai_ml.dt.yaml
	arch/arm64/boot/dts/freescale/imx8qxp-colibri-eval-v3.dt.yaml
	arch/arm64/boot/dts/freescale/imx8qxp-mek.dt.yaml


  reply	other threads:[~2022-03-24 14:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24  4:20 [PATCH 0/4] dt-bindings: imx: add nvmem property Peng Fan (OSS)
2022-03-24  4:20 ` [PATCH 1/4] dt-bindings: can: fsl,flexcan: introduce " Peng Fan (OSS)
2022-03-24  4:20 ` [PATCH 2/4] dt-bindings: net: fsl,fec: " Peng Fan (OSS)
2022-03-24 14:18   ` Rob Herring [this message]
2022-03-24  4:20 ` [PATCH 3/4] dt-bindings: mmc: imx-esdhc: " Peng Fan (OSS)
2022-03-24  4:20 ` [PATCH 4/4] dt-bindings: net: imx-dwmac: " Peng Fan (OSS)
2022-03-24 14:18   ` Rob Herring
2022-03-24 11:11 ` [PATCH 0/4] dt-bindings: imx: add " Uwe Kleine-König
2022-03-24 11:16   ` Ahmad Fatoum
2022-03-24 12:21   ` Peng Fan
2022-04-01  0:15   ` Rob Herring
2022-04-02  1:52     ` Peng Fan
2022-04-04 15:15       ` Rob Herring

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=1648131488.609060.1995384.nullmailer@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=peng.fan@nxp.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=qiangqing.zhang@nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=ulf.hansson@linaro.org \
    --cc=wg@grandegger.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).