[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aBHc2tT2-Duj3_-A@gondor.apana.org.au>
Date: Wed, 30 Apr 2025 16:18:34 +0800
From: Herbert Xu <herbert@...dor.apana.org.au>
To: Qunqin Zhao <zhaoqunqin@...ngson.cn>
Cc: Huacai Chen <chenhuacai@...nel.org>, davem@...emloft.net,
peterhuewe@....de, jarkko@...nel.org, linux-kernel@...r.kernel.org,
loongarch@...ts.linux.dev, linux-crypto@...r.kernel.org,
jgg@...pe.ca, linux-integrity@...r.kernel.org,
pmenzel@...gen.mpg.de, Lee Jones <lee@...nel.org>
Subject: Re: [PATCH v8 0/5] Add Loongson Security Engine chip driver
On Wed, Apr 30, 2025 at 04:14:40PM +0800, Qunqin Zhao wrote:
>
> Sorry to bother you, may i ask is it fine to move the Security Engine base
> driver[Patch v8 1/5] to drivers/crypto ?
>
> The base driver uses MFD interface to register child device(tpm, rng) , as
> done in
>
> "drivers/iio/common/ssp_sensors/ssp_dev.c" and
> "drivers/firmware/xilinx/zynqmp.c".
>
> Thank you, and I look forward to hearing from you.
I don't mind at this point in time. But if this driver were to
develop features way outside of the Crypto API in future then I
may change my mind.
Thanks,
--
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Powered by blists - more mailing lists