From: Rob Herring <robh@kernel.org>
To: Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-imx@nxp.com, Jonathan Cameron <jic23@kernel.org>,
linux-iio@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>,
Haibo Chen <haibo.chen@nxp.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: iio: adc: Add imx6ul & imx6sx compatibles
Date: Fri, 17 Jun 2022 16:44:48 -0600 [thread overview]
Message-ID: <20220617224448.GA2574775-robh@kernel.org> (raw)
In-Reply-To: <1655141687.002668.3951189.nullmailer@robh.at.kernel.org>
On Mon, Jun 13, 2022 at 11:34:46AM -0600, Rob Herring wrote:
> On Mon, 13 Jun 2022 14:35:29 +0200, Alexander Stein wrote:
> > Both are already using the vf610 compatible.
> >
> > Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> > ---
> > .../devicetree/bindings/iio/adc/fsl,vf610-adc.yaml | 9 ++++++++-
> > 1 file changed, 8 insertions(+), 1 deletion(-)
> >
>
> 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/
>
>
> adc@2198000: 'num-channels' does not match any of the regexes: 'pinctrl-[0-9]+'
Looks like you need to add 'num-channels'?
> arch/arm/boot/dts/imx6ul-14x14-evk.dtb
> arch/arm/boot/dts/imx6ul-ccimx6ulsbcexpress.dtb
> arch/arm/boot/dts/imx6ul-ccimx6ulsbcpro.dtb
> arch/arm/boot/dts/imx6ul-geam.dtb
> arch/arm/boot/dts/imx6ul-isiot-emmc.dtb
> arch/arm/boot/dts/imx6ul-isiot-nand.dtb
> arch/arm/boot/dts/imx6ul-kontron-n6310-s-43.dtb
> arch/arm/boot/dts/imx6ul-kontron-n6310-s.dtb
> arch/arm/boot/dts/imx6ull-14x14-evk.dtb
> arch/arm/boot/dts/imx6ull-colibri-aster.dtb
> arch/arm/boot/dts/imx6ull-colibri-emmc-aster.dtb
> arch/arm/boot/dts/imx6ull-colibri-emmc-eval-v3.dtb
> arch/arm/boot/dts/imx6ull-colibri-emmc-iris.dtb
> arch/arm/boot/dts/imx6ull-colibri-emmc-iris-v2.dtb
> arch/arm/boot/dts/imx6ull-colibri-eval-v3.dtb
> arch/arm/boot/dts/imx6ull-colibri-iris.dtb
> arch/arm/boot/dts/imx6ull-colibri-iris-v2.dtb
> arch/arm/boot/dts/imx6ull-colibri-wifi-aster.dtb
> arch/arm/boot/dts/imx6ull-colibri-wifi-eval-v3.dtb
> arch/arm/boot/dts/imx6ull-colibri-wifi-iris.dtb
> arch/arm/boot/dts/imx6ull-colibri-wifi-iris-v2.dtb
> arch/arm/boot/dts/imx6ul-liteboard.dtb
> arch/arm/boot/dts/imx6ull-jozacp.dtb
> arch/arm/boot/dts/imx6ull-myir-mys-6ulx-eval.dtb
> arch/arm/boot/dts/imx6ull-opos6uldev.dtb
> arch/arm/boot/dts/imx6ull-phytec-segin-ff-rdk-emmc.dtb
> arch/arm/boot/dts/imx6ull-phytec-segin-ff-rdk-nand.dtb
> arch/arm/boot/dts/imx6ull-phytec-segin-lc-rdk-nand.dtb
> arch/arm/boot/dts/imx6ull-phytec-tauri-emmc.dtb
> arch/arm/boot/dts/imx6ull-phytec-tauri-nand.dtb
> arch/arm/boot/dts/imx6ull-tqma6ull2l-mba6ulx.dtb
> arch/arm/boot/dts/imx6ull-tqma6ull2-mba6ulx.dtb
> arch/arm/boot/dts/imx6ul-opos6uldev.dtb
> arch/arm/boot/dts/imx6ul-phytec-segin-ff-rdk-emmc.dtb
> arch/arm/boot/dts/imx6ul-phytec-segin-ff-rdk-nand.dtb
> arch/arm/boot/dts/imx6ul-pico-dwarf.dtb
> arch/arm/boot/dts/imx6ul-pico-hobbit.dtb
> arch/arm/boot/dts/imx6ul-pico-pi.dtb
> arch/arm/boot/dts/imx6ul-prti6g.dtb
> arch/arm/boot/dts/imx6ul-tqma6ul1-mba6ulx.dtb
> arch/arm/boot/dts/imx6ul-tqma6ul2l-mba6ulx.dtb
> arch/arm/boot/dts/imx6ul-tqma6ul2-mba6ulx.dtb
> arch/arm/boot/dts/imx6ul-tx6ul-0010.dtb
> arch/arm/boot/dts/imx6ul-tx6ul-0011.dtb
> arch/arm/boot/dts/imx6ul-tx6ul-mainboard.dtb
>
>
next prev parent reply other threads:[~2022-06-17 22:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 12:35 [PATCH] dt-bindings: iio: adc: Add imx6ul & imx6sx compatibles Alexander Stein
2022-06-13 17:34 ` Rob Herring
2022-06-17 22:44 ` Rob Herring [this message]
2022-06-18 17:01 ` Jonathan Cameron
2022-06-20 8:12 ` (EXT) " Alexander Stein
2022-06-28 21:09 ` Rob Herring
2022-07-15 7:56 ` Alexander Stein
2022-07-16 14:52 ` Jonathan Cameron
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=20220617224448.GA2574775-robh@kernel.org \
--to=robh@kernel.org \
--cc=alexander.stein@ew.tq-group.com \
--cc=devicetree@vger.kernel.org \
--cc=haibo.chen@nxp.com \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-imx@nxp.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).