From: Herbert Xu <herbert@gondor.apana.org.au>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Kamlesh Gurudasani <kamlesh@ti.com>,
kristo@kernel.org, will@kernel.org, akpm@linux-foundation.org,
davem@davemloft.net, mcoquelin.stm32@gmail.com,
alexandre.torgue@foss.st.com, robh@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
vigneshr@ti.com, catalin.marinas@arm.com,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 0/6] Add support for MCRC64 engine to calculate 64-bit CRC in Full-CPU mode
Date: Tue, 11 Jun 2024 11:17:24 +0800 [thread overview]
Message-ID: <ZmfBxLB8RC_KNUlx@gondor.apana.org.au> (raw)
In-Reply-To: <20240611031314.GA2557@sol.localdomain>
On Mon, Jun 10, 2024 at 08:13:14PM -0700, Eric Biggers wrote:
>
> I thought the rule is that there needs to be an in-kernel user to add algorithms
> to the crypto API? Is there any precedent for adding new algorithms purely so
> that accelerators that implement them can be accessed from userspace via AF_ALG?
I agree. Perhaps this driver could instead be added as a simple
char device that is then used directly by the intended user without
going through the Crypto API at all.
That would make it a lot simpler.
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
_______________________________________________
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:[~2024-06-11 3:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 12:24 [PATCH v3 0/6] Add support for MCRC64 engine to calculate 64-bit CRC in Full-CPU mode kamlesh
2024-05-30 12:24 ` [PATCH v3 1/6] lib: add ISO 3309 model crc64 kamlesh
2024-06-11 3:14 ` Eric Biggers
2024-05-30 12:24 ` [PATCH v3 2/6] crypto: crc64 - add crc64-iso3309 framework kamlesh
2024-05-30 12:24 ` [PATCH v3 3/6] dt-bindings: crypto: Add Texas Instruments MCRC64 kamlesh
2024-05-31 9:02 ` Krzysztof Kozlowski
2024-05-30 12:24 ` [PATCH v3 4/6] crypto: ti - add driver for MCRC64 engine kamlesh
2024-06-11 12:02 ` Markus Elfring
2024-05-30 12:24 ` [PATCH v3 5/6 DONOTMERGE] arm64: dts: ti: k3-am62: Add dt node, cbass_main ranges for MCRC64 kamlesh
2024-05-30 12:24 ` [PATCH v3 6/6 DONOTMERGE] arm64: defconfig: enable TI MCRC64 module kamlesh
2024-06-10 14:33 ` [PATCH v3 0/6] Add support for MCRC64 engine to calculate 64-bit CRC in Full-CPU mode Kamlesh Gurudasani
2024-06-11 2:31 ` Herbert Xu
2024-06-11 3:13 ` Eric Biggers
2024-06-11 3:17 ` Herbert Xu [this message]
2024-09-06 11:14 ` Kamlesh Gurudasani
2024-09-13 10:35 ` Herbert Xu
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=ZmfBxLB8RC_KNUlx@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=akpm@linux-foundation.org \
--cc=alexandre.torgue@foss.st.com \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=ebiggers@kernel.org \
--cc=kamlesh@ti.com \
--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=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh@kernel.org \
--cc=vigneshr@ti.com \
--cc=will@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