[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8e55801a-a46e-58d5-cf84-2ee8a733df9a@loongson.cn>
Date: Tue, 13 May 2025 15:12:05 +0800
From: Qunqin Zhao <zhaoqunqin@...ngson.cn>
To: Huacai Chen <chenhuacai@...nel.org>
Cc: lee@...nel.org, herbert@...dor.apana.org.au, 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
Subject: Re: [PATCH v9 0/5] Add Loongson Security Engine chip driver
在 2025/5/11 下午5:34, Huacai Chen 写道:
> Hi, Qunqin,
>
> Where is the 2nd patch in V7?
Hi, Huacai
I added "loongson se. c" and "loongson se. h" to the LOONGSON CRYPTO
DRIVER entry.
or should i add a separate entry for the mfd driver as done in v7?
Thanks for your comments,
Qunqin.
>
> Huacai
>
> On Tue, May 6, 2025 at 12:33 PM Qunqin Zhao <zhaoqunqin@...ngson.cn> wrote:
>> The Loongson Security Engine chip supports RNG, SM2, SM3 and SM4
>> accelerator engines. Each engine have its own DMA buffer provided
>> by the controller. The kernel cannot directly send commands to the
>> engine and must first send them to the controller, which will
>> forward them to the corresponding engine. Based on these engines,
>> TPM2 have been implemented in the chip, then let's treat TPM2 itself
>> as an engine.
>>
>> v9: Moved the base driver back to drivers/mfd. Cleanned up coding style.
>>
>> v8: Like Lee said, the base driver goes beyond MFD scope. Since these
>> are all encryption related drivers and SM2, SM3, and SM4 drivers
>> will be added to the crypto subsystem in the future, the base driver
>> need to be changed when adding these drivers. Therefore, it may be
>> more appropriate to place the base driver within the crypto
>> subsystem.
>>
>> Removed complete callback in all drivers. Removed the concepts of
>> "channel", "msg" and "request" as they may be confusing. Used the
>> concepts of "egnine" and "command" may be better.
>>
>> v7: Addressed Huacai's comments.
>>
>> v6: mfd :MFD_LS6000SE -> MFD_LOONGSON_SE, ls6000se.c -> loongson-se.c
>>
>> crypto :CRYPTO_DEV_LS6000SE_RNG -> CRYPTO_DEV_LOONGSON_RNG,
>> ls6000se-rng.c ->loongson-rng.c
>>
>> tpm: TCG_LSSE -> TCG_LOONGSON, tpm_lsse.c ->tpm_loongson.c
>>
>> v5: Registered "ls6000se-rng" device in mfd driver
>>
>> Qunqin Zhao (5):
>> mfd: Add support for Loongson Security Engine chip controller
>> crypto: loongson - add Loongson RNG driver support
>> MAINTAINERS: Add entry for Loongson crypto driver
>> tpm: Add a driver for Loongson TPM device
>> MAINTAINERS: Add tpm_loongson.c to LOONGSON CRYPTO DRIVER entry
>>
>> MAINTAINERS | 9 +
>> drivers/char/tpm/Kconfig | 9 +
>> drivers/char/tpm/Makefile | 1 +
>> drivers/char/tpm/tpm_loongson.c | 78 ++++++++
>> drivers/crypto/Kconfig | 1 +
>> drivers/crypto/Makefile | 1 +
>> drivers/crypto/loongson/Kconfig | 5 +
>> drivers/crypto/loongson/Makefile | 1 +
>> drivers/crypto/loongson/loongson-rng.c | 197 +++++++++++++++++++++
>> drivers/mfd/Kconfig | 11 ++
>> drivers/mfd/Makefile | 2 +
>> drivers/mfd/loongson-se.c | 235 +++++++++++++++++++++++++
>> include/linux/mfd/loongson-se.h | 52 ++++++
>> 13 files changed, 602 insertions(+)
>> create mode 100644 drivers/char/tpm/tpm_loongson.c
>> create mode 100644 drivers/crypto/loongson/Kconfig
>> create mode 100644 drivers/crypto/loongson/Makefile
>> create mode 100644 drivers/crypto/loongson/loongson-rng.c
>> create mode 100644 drivers/mfd/loongson-se.c
>> create mode 100644 include/linux/mfd/loongson-se.h
>>
>>
>> base-commit: 92a09c47464d040866cf2b4cd052bc60555185fb
>> --
>> 2.45.2
>>
>>
Powered by blists - more mailing lists