mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Qunqin Zhao <zhaoqunqin@loongson.cn>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
	peterhuewe@gmx.de, jarkko@kernel.org,
	linux-kernel@vger.kernel.org, loongarch@lists.linux.dev,
	linux-crypto@vger.kernel.org, jgg@ziepe.ca,
	linux-integrity@vger.kernel.org, pmenzel@molgen.mpg.de,
	Yinggang Gu <guyinggang@loongson.cn>
Subject: Re: [PATCH v4 1/6] mfd: Add support for Loongson Security Module
Date: Wed, 12 Mar 2025 08:08:05 +0000	[thread overview]
Message-ID: <20250307200031.GG8350@google.com> (raw)
In-Reply-To: <20250226030358.15924-2-zhaoqunqin@loongson.cn>

On Wed, 26 Feb 2025, Qunqin Zhao wrote:

> This driver supports Loongson Security Module, which provides the control
> for it's hardware encryption acceleration child devices.
> 
> Co-developed-by: Yinggang Gu <guyinggang@loongson.cn>
> Signed-off-by: Yinggang Gu <guyinggang@loongson.cn>
> Signed-off-by: Qunqin Zhao <zhaoqunqin@loongson.cn>
> ---
> v3-v4: None
> 
> v2: Removed "ls6000se-sdf" device, added "ls6000se-tpm" device.
>     Passed dmamem size to SE firmware in se_init_hw() function.
> 
>  drivers/mfd/Kconfig          |  10 +
>  drivers/mfd/Makefile         |   2 +
>  drivers/mfd/ls6000se.c       | 374 +++++++++++++++++++++++++++++++++++
>  include/linux/mfd/ls6000se.h |  75 +++++++
>  4 files changed, 461 insertions(+)
>  create mode 100644 drivers/mfd/ls6000se.c
>  create mode 100644 include/linux/mfd/ls6000se.h
> 
> diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
> index d44c69bb3d..318fb113c1 100644
> --- a/drivers/mfd/Kconfig
> +++ b/drivers/mfd/Kconfig
> @@ -2439,5 +2439,15 @@ config MFD_UPBOARD_FPGA
>  	  To compile this driver as a module, choose M here: the module will be
>  	  called upboard-fpga.
>  
> +config MFD_LS6000SE
> +	tristate "Loongson Security Module Interface"
> +	depends on LOONGARCH && ACPI
> +	select MFD_CORE
> +	help
> +	  The Loongson security module provides the control for hardware
> +	  encryption acceleration devices. Each device uses at least one
> +	  channel to interact with security module, and each channel may
> +	  have its own buffer provided by security module.
> +
>  endmenu
>  endif
> diff --git a/drivers/mfd/Makefile b/drivers/mfd/Makefile
> index 9220eaf7cf..9556de7715 100644
> --- a/drivers/mfd/Makefile
> +++ b/drivers/mfd/Makefile
> @@ -294,3 +294,5 @@ obj-$(CONFIG_MFD_RSMU_I2C)	+= rsmu_i2c.o rsmu_core.o
>  obj-$(CONFIG_MFD_RSMU_SPI)	+= rsmu_spi.o rsmu_core.o
>  
>  obj-$(CONFIG_MFD_UPBOARD_FPGA)	+= upboard-fpga.o
> +
> +obj-$(CONFIG_MFD_LS6000SE)	+= ls6000se.o
> diff --git a/drivers/mfd/ls6000se.c b/drivers/mfd/ls6000se.c
> new file mode 100644
> index 0000000000..24d76c2ffc
> --- /dev/null
> +++ b/drivers/mfd/ls6000se.c

[...]

> +static const struct mfd_cell se_devs[] = {
> +	{ .name = "ls6000se-sdf" },
> +	{ .name = "ls6000se-tpm" },
> +};

Where are the drivers for these devices?  I don't see them anywhere.

I do see ls6000se-rng.  How is that registered?

-- 
Lee Jones [李琼斯]

  reply	other threads:[~2025-03-12  8:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-26  3:03 [PATCH v4 0/6] Drivers for Loongson security engine Qunqin Zhao
2025-02-26  3:03 ` [PATCH v4 1/6] mfd: Add support for Loongson Security Module Qunqin Zhao
2025-03-12  8:08   ` Lee Jones [this message]
2025-03-12  8:38     ` Qunqin Zhao
2025-02-26  3:03 ` [PATCH v4 2/6] MAINTAINERS: Add entry for Loongson Security Module driver Qunqin Zhao
2025-02-26  3:03 ` [PATCH v4 3/6] crypto: loongson - add Loongson RNG driver support Qunqin Zhao
2025-02-26  3:03 ` [PATCH v4 4/6] MAINTAINERS: Add entry for Loongson RNG driver Qunqin Zhao
2025-02-28 14:13 ` [PATCH v4 0/6] Drivers for Loongson security engine Huacai Chen

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=20250307200031.GG8350@google.com \
    --to=lee@kernel.org \
    --cc=davem@davemloft.net \
    --cc=guyinggang@loongson.cn \
    --cc=herbert@gondor.apana.org.au \
    --cc=jarkko@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=peterhuewe@gmx.de \
    --cc=pmenzel@molgen.mpg.de \
    --cc=zhaoqunqin@loongson.cn \
    /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

all inboxes | Powered by JetHome®