From: T Pratham <t-pratham@ti.com>
To: Ovidiu Panait <ovidiu.panait.oss@gmail.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>
Cc: <linux-kernel@vger.kernel.org>, <linux-crypto@vger.kernel.org>,
Kamlesh Gurudasani <kamlesh@ti.com>,
Manorit Chawdhry <m-chawdhry@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Praneeth Bajjuri <praneeth@ti.com>,
Vishal Mahaveer <vishalm@ti.com>,
Kavitha Malarvizhi <k-malarvizhi@ti.com>
Subject: Re: [PATCH v6 2/2] crypto: ti: Add driver for DTHE V2 AES Engine (ECB, CBC)
Date: Wed, 20 Aug 2025 14:28:35 +0530 [thread overview]
Message-ID: <d1d70f62-fb3d-4af5-936e-b59491ee1c34@ti.com> (raw)
In-Reply-To: <e40d056b-731d-4e33-9347-20c0a7665ede@gmail.com>
On 19/08/25 15:26, Ovidiu Panait wrote:
> Hi,
>
> On 8/19/25 9:12 AM, T Pratham wrote:
>> Add support for ECB and CBC modes in the AES Engine of the DTHE V2
>> hardware cryptography engine.
>>
>> Signed-off-by: T Pratham <t-pratham@ti.com>
>> ---
>> MAINTAINERS | 1 +
>> drivers/crypto/Kconfig | 1 +
>> drivers/crypto/Makefile | 1 +
>> drivers/crypto/ti/Kconfig | 14 +
>> drivers/crypto/ti/Makefile | 3 +
>> drivers/crypto/ti/dthev2-aes.c | 411 ++++++++++++++++++++++++++++++
>> drivers/crypto/ti/dthev2-common.c | 220 ++++++++++++++++
>> drivers/crypto/ti/dthev2-common.h | 101 ++++++++
>> 8 files changed, 752 insertions(+)
>> create mode 100644 drivers/crypto/ti/Kconfig
>> create mode 100644 drivers/crypto/ti/Makefile
>> create mode 100644 drivers/crypto/ti/dthev2-aes.c
>> create mode 100644 drivers/crypto/ti/dthev2-common.c
>> create mode 100644 drivers/crypto/ti/dthev2-common.h
>>
>
> [...]
>
[...]
>> +
>> +probe_reg_err:
>> + crypto_engine_stop(dev_data->engine);
>> +probe_engine_start_err:
>> + crypto_engine_exit(dev_data->engine);
>
> crypto_engine_exit() calls crypto_engine_stop() internally, so there is
> no need to call both functions here. Just use crypto_engine_exit().
>
> /**
> * crypto_engine_exit - free the resources of hardware engine when exit
> * @engine: the hardware engine need to be freed
> */
> void crypto_engine_exit(struct crypto_engine *engine)
> {
> int ret;
>
> ret = crypto_engine_stop(engine);
> if (ret)
> return;
>
> kthread_destroy_worker(engine->kworker);
> }
>
Thanks for this insight! Will correct this.
[...]
>
> Ovidiu
Regards
T Pratham
prev parent reply other threads:[~2025-08-20 8:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 6:12 [PATCH v6 0/2] Add support for Texas Instruments DTHEv2 Crypto Engine T Pratham
2025-08-19 6:12 ` [PATCH v6 1/2] dt-bindings: crypto: Add binding for TI DTHE V2 T Pratham
2025-08-20 7:43 ` Krzysztof Kozlowski
2025-08-20 8:52 ` T Pratham
2025-08-19 6:12 ` [PATCH v6 2/2] crypto: ti: Add driver for DTHE V2 AES Engine (ECB, CBC) T Pratham
2025-08-19 9:56 ` Ovidiu Panait
2025-08-20 8:58 ` T Pratham [this message]
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=d1d70f62-fb3d-4af5-936e-b59491ee1c34@ti.com \
--to=t-pratham@ti.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=k-malarvizhi@ti.com \
--cc=kamlesh@ti.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-chawdhry@ti.com \
--cc=ovidiu.panait.oss@gmail.com \
--cc=praneeth@ti.com \
--cc=vigneshr@ti.com \
--cc=vishalm@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).