From: LABBE Corentin <clabbe@baylibre.com>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, heiko@sntech.de,
linux-crypto@vger.kernel.org, herbert@gondor.apana.org.au,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
john@metanate.com, robh+dt@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 17/18] dt-bindings: crypto: convert rockchip-crypto to yaml
Date: Thu, 3 Mar 2022 20:40:49 +0100 [thread overview]
Message-ID: <YiEZwetOpRhZ4iCa@Red> (raw)
In-Reply-To: <1646315078.991896.1495435.nullmailer@robh.at.kernel.org>
Le Thu, Mar 03, 2022 at 07:44:38AM -0600, Rob Herring a écrit :
> On Wed, 02 Mar 2022 21:11:12 +0000, Corentin Labbe wrote:
> > convert rockchip-crypto to yaml
> >
> > Signed-off-by: Corentin Labbe <clabbe@baylibre.com>
> > ---
> > .../crypto/rockchip,rk3288-crypto.yaml | 64 +++++++++++++++++++
> > .../bindings/crypto/rockchip-crypto.txt | 28 --------
> > 2 files changed, 64 insertions(+), 28 deletions(-)
> > create mode 100644 Documentation/devicetree/bindings/crypto/rockchip,rk3288-crypto.yaml
> > delete mode 100644 Documentation/devicetree/bindings/crypto/rockchip-crypto.txt
> >
>
> 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/1600075
>
>
> cypto-controller@ff8a0000: clock-names: ['aclk', 'hclk', 'sclk', 'apb_pclk'] is too long
> arch/arm/boot/dts/rk3288-evb-act8846.dt.yaml
> arch/arm/boot/dts/rk3288-evb-rk808.dt.yaml
> arch/arm/boot/dts/rk3288-firefly-beta.dt.yaml
> arch/arm/boot/dts/rk3288-firefly.dt.yaml
> arch/arm/boot/dts/rk3288-firefly-reload.dt.yaml
> arch/arm/boot/dts/rk3288-miqi.dt.yaml
> arch/arm/boot/dts/rk3288-phycore-rdk.dt.yaml
> arch/arm/boot/dts/rk3288-popmetal.dt.yaml
> arch/arm/boot/dts/rk3288-r89.dt.yaml
> arch/arm/boot/dts/rk3288-rock2-square.dt.yaml
> arch/arm/boot/dts/rk3288-rock-pi-n8.dt.yaml
> arch/arm/boot/dts/rk3288-tinker.dt.yaml
> arch/arm/boot/dts/rk3288-tinker-s.dt.yaml
> arch/arm/boot/dts/rk3288-veyron-brain.dt.yaml
> arch/arm/boot/dts/rk3288-veyron-fievel.dt.yaml
> arch/arm/boot/dts/rk3288-veyron-jaq.dt.yaml
> arch/arm/boot/dts/rk3288-veyron-jerry.dt.yaml
> arch/arm/boot/dts/rk3288-veyron-mickey.dt.yaml
> arch/arm/boot/dts/rk3288-veyron-mighty.dt.yaml
> arch/arm/boot/dts/rk3288-veyron-minnie.dt.yaml
> arch/arm/boot/dts/rk3288-veyron-pinky.dt.yaml
> arch/arm/boot/dts/rk3288-veyron-speedy.dt.yaml
> arch/arm/boot/dts/rk3288-veyron-tiger.dt.yaml
> arch/arm/boot/dts/rk3288-vyasa.dt.yaml
>
> cypto-controller@ff8a0000: clocks: [[7, 199], [7, 461], [7, 125], [7, 193]] is too long
> arch/arm/boot/dts/rk3288-evb-act8846.dt.yaml
> arch/arm/boot/dts/rk3288-evb-rk808.dt.yaml
> arch/arm/boot/dts/rk3288-firefly-beta.dt.yaml
> arch/arm/boot/dts/rk3288-firefly.dt.yaml
> arch/arm/boot/dts/rk3288-firefly-reload.dt.yaml
> arch/arm/boot/dts/rk3288-miqi.dt.yaml
> arch/arm/boot/dts/rk3288-phycore-rdk.dt.yaml
> arch/arm/boot/dts/rk3288-popmetal.dt.yaml
> arch/arm/boot/dts/rk3288-r89.dt.yaml
> arch/arm/boot/dts/rk3288-rock2-square.dt.yaml
> arch/arm/boot/dts/rk3288-rock-pi-n8.dt.yaml
> arch/arm/boot/dts/rk3288-tinker.dt.yaml
> arch/arm/boot/dts/rk3288-tinker-s.dt.yaml
> arch/arm/boot/dts/rk3288-veyron-brain.dt.yaml
> arch/arm/boot/dts/rk3288-veyron-fievel.dt.yaml
> arch/arm/boot/dts/rk3288-veyron-jaq.dt.yaml
> arch/arm/boot/dts/rk3288-veyron-jerry.dt.yaml
> arch/arm/boot/dts/rk3288-veyron-mickey.dt.yaml
> arch/arm/boot/dts/rk3288-veyron-mighty.dt.yaml
> arch/arm/boot/dts/rk3288-veyron-minnie.dt.yaml
> arch/arm/boot/dts/rk3288-veyron-pinky.dt.yaml
> arch/arm/boot/dts/rk3288-veyron-speedy.dt.yaml
> arch/arm/boot/dts/rk3288-veyron-tiger.dt.yaml
> arch/arm/boot/dts/rk3288-vyasa.dt.yaml
>
The patch fixing thoses warning is in the serie.
Regards
next prev parent reply other threads:[~2022-03-03 19:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 21:10 [PATCH v2 00/18] crypto: rockchip: permit to pass self-tests Corentin Labbe
2022-03-02 21:10 ` [PATCH v2 01/18] crypto: rockchip: use dev_err for error message about interrupt Corentin Labbe
2022-03-02 21:10 ` [PATCH v2 02/18] crypto: rockchip: do not use uninit variable Corentin Labbe
2022-03-02 21:10 ` [PATCH v2 03/18] crypto: rockchip: do not do custom power management Corentin Labbe
2022-03-02 21:10 ` [PATCH v2 04/18] crypto: rockchip: fix privete/private typo Corentin Labbe
2022-03-02 21:11 ` [PATCH v2 05/18] crypto: rockchip: do not store mode globally Corentin Labbe
2022-03-02 21:11 ` [PATCH v2 06/18] crypto: rockchip: add fallback for cipher Corentin Labbe
2022-03-03 14:21 ` John Keeping
2022-03-03 19:54 ` LABBE Corentin
2022-03-02 21:11 ` [PATCH v2 07/18] crypto: rockchip: add fallback for ahash Corentin Labbe
2022-03-02 21:11 ` [PATCH v2 08/18] crypto: rockchip: better handle cipher key Corentin Labbe
2022-03-02 21:11 ` [PATCH v2 09/18] crypto: rockchip: remove non-aligned handling Corentin Labbe
2022-03-02 21:11 ` [PATCH v2 10/18] crypto: rockchip: rework by using crypto_engine Corentin Labbe
2022-03-02 21:11 ` [PATCH v2 11/18] crypto: rockhip: do not handle dma clock Corentin Labbe
2022-03-04 15:01 ` Johan Jonker
2022-03-10 14:45 ` LABBE Corentin
2022-03-10 17:52 ` Johan Jonker
2022-03-15 11:45 ` LABBE Corentin
2022-03-02 21:11 ` [PATCH v2 12/18] ARM: dts: rk3288: crypto do not need " Corentin Labbe
2022-03-02 21:11 ` [PATCH v2 13/18] crypto: rockchip: rewrite type Corentin Labbe
2022-03-02 21:11 ` [PATCH v2 14/18] crypto: rockchip: add debugfs Corentin Labbe
2022-03-02 21:11 ` [PATCH v2 15/18] crypto: rockchip: introduce PM Corentin Labbe
2022-03-03 12:57 ` John Keeping
2022-03-02 21:11 ` [PATCH v2 16/18] arm64: dts: rockchip: add rk3328 crypto node Corentin Labbe
2022-03-02 21:11 ` [PATCH v2 17/18] dt-bindings: crypto: convert rockchip-crypto to yaml Corentin Labbe
2022-03-03 13:44 ` Rob Herring
2022-03-03 19:40 ` LABBE Corentin [this message]
2022-03-08 0:52 ` Rob Herring
2022-03-02 21:11 ` [PATCH v2 18/18] crypto: rockchip: add myself as maintainer Corentin Labbe
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=YiEZwetOpRhZ4iCa@Red \
--to=clabbe@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=herbert@gondor.apana.org.au \
--cc=john@metanate.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
/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).