From: Rob Herring <robh@kernel.org>
To: Robin Gong <yibin.gong@nxp.com>
Cc: will@kernel.org, festevam@gmail.com, vkoul@kernel.org,
dan.j.williams@intel.com, kernel@pengutronix.de,
catalin.marinas@arm.com, robh+dt@kernel.org, linux-imx@nxp.com,
dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, angelo@sysam.it,
devicetree@vger.kernel.org
Subject: Re: [PATCH v1 6/9] dt-bindings: dma: add fsl-edma3 yaml
Date: Thu, 2 Jul 2020 15:01:07 -0600 [thread overview]
Message-ID: <20200702210107.GA1686199@bogus> (raw)
In-Reply-To: <1593702489-21648-7-git-send-email-yibin.gong@nxp.com>
On Thu, 02 Jul 2020 23:08:06 +0800, Robin Gong wrote:
> Add device binding doc for fsl-edma3 driver.
>
> Signed-off-by: Robin Gong <yibin.gong@nxp.com>
> ---
> .../devicetree/bindings/dma/nxp,fsl-edma3.yaml | 129 +++++++++++++++++++++
> 1 file changed, 129 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/dma/nxp,fsl-edma3.yaml
>
My bot found errors running 'make dt_binding_check' on your patch:
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/dma/nxp,fsl-edma3.example.dt.yaml: dma-controller@5a1f0000: 'power-domain-names' does not match any of the regexes: 'pinctrl-[0-9]+'
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/dma/nxp,fsl-edma3.example.dt.yaml: dma-controller@5a1f0000: interrupt-names:1: 'edma2-chan9-tx' does not match '^edma[0-2]-chan[0-31]-tx|rx+$'
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/dma/nxp,fsl-edma3.example.dt.yaml: dma-controller@5a1f0000: interrupt-names:3: 'edma2-chan11-tx' does not match '^edma[0-2]-chan[0-31]-tx|rx+$'
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/dma/nxp,fsl-edma3.example.dt.yaml: dma-controller@5a1f0000: interrupt-names:5: 'edma2-chan13-tx' does not match '^edma[0-2]-chan[0-31]-tx|rx+$'
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/dma/nxp,fsl-edma3.example.dt.yaml: dma-controller@5a1f0000: interrupt-names:7: 'edma2-chan15-tx' does not match '^edma[0-2]-chan[0-31]-tx|rx+$'
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/dma/nxp,fsl-edma3.example.dt.yaml: dma-controller@5a1f0000: reg: [[1512570880, 65536], [1512636416, 65536], [1512701952, 65536], [1512767488, 65536], [1512833024, 65536], [1512898560, 65536], [1512964096, 65536], [1513029632, 65536]] is too long
See https://patchwork.ozlabs.org/patch/1321003
If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure dt-schema is up to date:
pip3 install git+https://github.com/devicetree-org/dt-schema.git@master --upgrade
Please check and re-submit.
next prev parent reply other threads:[~2020-07-02 21:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 15:08 [PATCH v1 0/9] add fsl-edma3 support Robin Gong
2020-07-02 15:08 ` [PATCH v1 1/9] dmaengine: fsl-edma: move edma_request functions into drvdata Robin Gong
2020-07-02 15:08 ` [PATCH v1 2/9] dmaengine: fsl-edma-common: add condition check for fsl_edma_chan_mux Robin Gong
2020-07-02 15:08 ` [PATCH v1 3/9] dmaengine: fsl-edma-common: add fsl_chan into fsl_edma_fill_tcd Robin Gong
2020-07-02 15:08 ` [PATCH v1 4/9] dmaengine: fsl-edma-common: export fsl_edma_set_tcd_regs Robin Gong
2020-07-02 15:08 ` [PATCH v1 5/9] dmaengine: fsl-edma3: add fsl-edma3 driver Robin Gong
2020-07-02 15:08 ` [PATCH v1 6/9] dt-bindings: dma: add fsl-edma3 yaml Robin Gong
2020-07-02 21:01 ` Rob Herring [this message]
2020-07-03 6:47 ` Robin Gong
2020-07-02 15:08 ` [PATCH v1 7/9] firmware: imx: scu-pd: correct dma resource Robin Gong
2020-07-02 15:08 ` [PATCH v1 8/9] arm64: dts: imx8qxp: add edma2 Robin Gong
2020-07-02 15:08 ` [PATCH v1 9/9] arm64: configs: defconfig: add CONFIG_FSL_EDMA3 Robin Gong
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=20200702210107.GA1686199@bogus \
--to=robh@kernel.org \
--cc=angelo@sysam.it \
--cc=catalin.marinas@arm.com \
--cc=dan.j.williams@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=vkoul@kernel.org \
--cc=will@kernel.org \
--cc=yibin.gong@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).