From: Rob Herring <robh@kernel.org>
To: Daniel Parks <danielrparks@ti.com>
Cc: linux-crypto@vger.kernel.org, Tero Kristo <kristo@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 2/6] dt-bindings: crypto: add binding for eip29t2 public key accelerator (PKA)
Date: Tue, 09 Aug 2022 17:22:06 -0600 [thread overview]
Message-ID: <1660087326.267606.2675470.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <856cbf3a002b5d400bbbdb7aa914ab5b8681a96e.1659985696.git.danielrparks@ti.com>
On Mon, 08 Aug 2022 14:12:51 -0500, Daniel Parks wrote:
> The PKA is a mmio-only asymmetric crypto accelerator available on
> certain K3 devices.
>
> Signed-off-by: Daniel Parks <danielrparks@ti.com>
> ---
> .../inside-secure,safexcel-eip29t2.yaml | 49 +++++++++++++++++++
> 1 file changed, 49 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/crypto/inside-secure,safexcel-eip29t2.yaml
>
My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
on your patch (DT_CHECKER_FLAGS is new in v5.13):
yamllint warnings/errors:
dtschema/dtc warnings/errors:
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/crypto/inside-secure,safexcel-eip29t2.example.dtb: pka@40920000: reg: [[0, 1083310080], [0, 8192], [0, 1083326464], [0, 32768]] is too long
From schema: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/crypto/inside-secure,safexcel-eip29t2.yaml
doc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/patch/
This check can fail if there are any dependencies. The base for a patch
series is generally the most recent rc1.
If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure 'yamllint' is installed and dt-schema is up to
date:
pip3 install dtschema --upgrade
Please check and re-submit.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-08-09 23:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 19:12 [RFC PATCH 0/6] Add SA2UL Public Key Accelerator driver Daniel Parks
2022-08-08 19:12 ` [RFC PATCH 1/6] dt-bindings: crypto: ti,sa2ul: add pka subdevice Daniel Parks
2022-08-09 5:44 ` Krzysztof Kozlowski
2022-08-09 23:22 ` Rob Herring
2022-08-08 19:12 ` [RFC PATCH 2/6] dt-bindings: crypto: add binding for eip29t2 public key accelerator (PKA) Daniel Parks
2022-08-09 5:47 ` Krzysztof Kozlowski
2022-08-09 23:22 ` Rob Herring [this message]
2022-08-08 19:12 ` [RFC PATCH 3/6] arm64: dts: ti: k3-am64-main: add SA2UL public key accelerator subdevice Daniel Parks
2022-08-08 19:12 ` [RFC PATCH 4/6] arm64: dts: ti: k3-j721e-main: " Daniel Parks
2022-08-08 19:12 ` [RFC PATCH 5/6] crypto: sa2ul: turn on PKA engine Daniel Parks
2022-08-08 19:12 ` [RFC PATCH 6/6] crypto: sa2ul_pka: Add SA2UL PKA driver Daniel Parks
2022-08-08 21:52 ` Randy Dunlap
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=1660087326.267606.2675470.nullmailer@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=danielrparks@ti.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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).