From: LABBE Corentin <clabbe@baylibre.com>
To: Johan Jonker <jbx6244@gmail.com>
Cc: davem@davemloft.net, heiko@sntech.de,
herbert@gondor.apana.org.au, krzysztof.kozlowski@canonical.com,
robh+dt@kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v3] dt-bindings: crypto: convert rockchip-crypto to yaml
Date: Fri, 11 Feb 2022 20:48:07 +0100 [thread overview]
Message-ID: <Yga9d5C2f1ubOok8@Red> (raw)
In-Reply-To: <dba5684a-1e5f-a4d4-604b-651751636cf3@gmail.com>
Le Fri, Feb 11, 2022 at 02:13:00PM +0100, Johan Jonker a écrit :
>
>
> On 2/11/22 12:59, Corentin Labbe wrote:
> > Convert rockchip-crypto to yaml
> >
> > Signed-off-by: Corentin Labbe <clabbe@baylibre.com>
> > ---
> > Changes since v1:
> > - fixed example
> > - renamed to a new name
> > - fixed some maxItems
> >
> > Change since v2:
> > - Fixed maintainers section
> >
> > .../crypto/rockchip,rk3288-crypto.yaml | 66 +++++++++++++++++++
> > .../bindings/crypto/rockchip-crypto.txt | 28 --------
> > 2 files changed, 66 insertions(+), 28 deletions(-)
>
> > create mode 100644 Documentation/devicetree/bindings/crypto/rockchip,rk3288-crypto.yaml
> > delete mode 100644 Documentation/devicetree/bindings/crypto/rockchip-crypto.txt
>
> There's more possible to this document:
>
> dt-bindings: crypto: rockchip: add support for px30
> https://github.com/rockchip-linux/kernel/commit/3655df1bc6114bda2a6417f39772a3cb008084ea
>
> crypto: rockchip - add px30 crypto aes/des support
> https://github.com/rockchip-linux/kernel/commit/ee082ae4f609f3b48f768420b31d8600448bd35a
>
Hello
The great advantage of out of tree code is that we can ignore it.
Anyway, if one day this code goes upstream, I think the new compatible should be in a new driver/module, both v1 and v2 are too different for me to be shared in the same driver.
But before upstreaming this code, the one in mainline should be fixed first, it fail self tests. (I have some patch partialy fixing it in progress)
Regards
next prev parent reply other threads:[~2022-02-11 19:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 11:59 [PATCH v3] dt-bindings: crypto: convert rockchip-crypto to yaml Corentin Labbe
2022-02-11 13:13 ` Johan Jonker
2022-02-11 19:48 ` LABBE Corentin [this message]
2022-02-13 22:37 ` Johan Jonker
2022-02-12 16:02 ` Krzysztof Kozlowski
2022-02-15 14:07 ` Johan Jonker
2022-02-23 13:05 ` LABBE Corentin
2022-02-23 13:14 ` Krzysztof Kozlowski
2022-03-18 10:20 ` LABBE Corentin
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=Yga9d5C2f1ubOok8@Red \
--to=clabbe@baylibre.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=herbert@gondor.apana.org.au \
--cc=jbx6244@gmail.com \
--cc=krzysztof.kozlowski@canonical.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 \
/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).