[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZZ8HP7dJgVaZLMw5@Red>
Date: Wed, 10 Jan 2024 22:08:15 +0100
From: Corentin Labbe <clabbe.montjoie@...il.com>
To: Alexey Romanov <avromanov@...utedevices.com>
Cc: narmstrong@...libre.com, neil.armstrong@...aro.org, clabbe@...libre.com,
herbert@...dor.apana.org.au, davem@...emloft.net,
robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org,
conor+dt@...nel.org, khilman@...libre.com, jbrunet@...libre.com,
artin.blumenstingl@...glemail.com, linux-crypto@...r.kernel.org,
linux-amlogic@...ts.infradead.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
kernel@...utedevices.com
Subject: Re: [PATCH v1 00/24] Support more Amlogic SoC families in crypto
driver
Le Wed, Jan 10, 2024 at 11:11:16PM +0300, Alexey Romanov a écrit :
> Hello!
>
> This patchset expand the funcionality of the Amlogic
> crypto driver by adding support for more SoC families:
> AXG, G12A, G12B, SM1, A1, S4.
>
> Also specify and enable crypto node in device tree
> for reference Amlogic devices.
>
> Tested on AXG, G12A/B, SM1, A1 and S4 devices via
> custom tests and trcypt module.
Hello
Thanks for your patch series.
Unfortunatly, I fail to apply it for testing on top of linux-next.
On top of which tree did you have tested ?
According to patch 01, you used a tree based before "crypto: amlogic - Use new crypto_engine_op interface" so too old.
Regards
Powered by blists - more mailing lists