From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B7A3B205E02; Wed, 25 Jun 2025 11:46:46 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1750852006; cv=none; b=A8UbSrZ7Pwcoed1sX2EFWRA/F0b97nN5udp1XW1SkYso1+b3wlm9nzX0NjoOHYJ5F0x4uUVQSjwasX1qyx6xvMD3/yarWQC6qnA8PimeqM2qRRfTnld2vNlMUzbmINJxfHkYIhA/jCkFiaWkFpbk/B40GXrjbnkY6KUPcQjR8i0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1750852006; c=relaxed/simple; bh=z0XG3Bw6TLmnXq/PjkcVsBymSm1jVI29doeIVoNJiSw=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=U5AwNPt9d/RftjMoFNXtaW84K8IlkD5Ro7/6BJMoIVSEFlwCIp/28guCp4Dl8SDIZ4luyUJZaFcZcq9W6lpcmc13bEhSbjiTnjgI/1q9Wmwkfx64sStaul6gh0yG8s5dM0YXll1WiJbv8W3UxGyIsd4M6HO8sJRl5qPkV7F94aI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=n8vED+Ix; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="n8vED+Ix" Received: by smtp.kernel.org (Postfix) with ESMTPSA id B55EFC4CEEA; Wed, 25 Jun 2025 11:46:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1750852006; bh=z0XG3Bw6TLmnXq/PjkcVsBymSm1jVI29doeIVoNJiSw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=n8vED+Ixnm6GXHKMbmqqW2ZMWMwnjPrlReJbEoNfv9Y0gj9ADIZmCPB2vvWThRjnD 1M/7AeX/HMARmgPGjA35x7qD8peBoF6O+l9fXQjuocKR2Y2/FmQcSfrPbXUI/R19oX oNKWYHe98z7krpsHN/u/liBM2RzLYDPIK+SGppc2mYx8LFBpCX/TJ2bz2CwsHexGkg LS5Q2N9cCTLYdL3UyXdpdMl/LGDzdG7HW4FHMQmDyMGr3nJ4mKcKYLDf2oKia3VNFa FWvqX3mqqAcNt93zYaj/f3mLrE6/t5iMLmKq2ZUFE66+Ol8EQQA7QoEUSuc5MWsEcq YMXdnWJ/+1d7g== Date: Wed, 25 Jun 2025 14:46:42 +0300 From: Jarkko Sakkinen To: Lee Jones Cc: Qunqin Zhao , herbert@gondor.apana.org.au, linux-kernel@vger.kernel.org, loongarch@lists.linux.dev, davem@davemloft.net, linux-crypto@vger.kernel.org, peterhuewe@gmx.de, jgg@ziepe.ca, linux-integrity@vger.kernel.org, Yinggang Gu , Huacai Chen Subject: Re: [PATCH v11 3/4] tpm: Add a driver for Loongson TPM device Message-ID: References: <20250619025138.2854-1-zhaoqunqin@loongson.cn> <20250619025138.2854-4-zhaoqunqin@loongson.cn> <20250625080527.GN795775@google.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20250625080527.GN795775@google.com> On Wed, Jun 25, 2025 at 09:05:27AM +0100, Lee Jones wrote: > On Wed, 25 Jun 2025, Jarkko Sakkinen wrote: > > > On Thu, Jun 19, 2025 at 10:51:37AM +0800, Qunqin Zhao wrote: > > > Loongson Security Engine supports random number generation, hash, > > > symmetric encryption and asymmetric encryption. Based on these > > > encryption functions, TPM2 have been implemented in the Loongson > > > Security Engine firmware. This driver is responsible for copying data > > > into the memory visible to the firmware and receiving data from the > > > firmware. > > > > > > Co-developed-by: Yinggang Gu > > > Signed-off-by: Yinggang Gu > > > Signed-off-by: Qunqin Zhao > > > Reviewed-by: Huacai Chen > > > --- > > > drivers/char/tpm/Kconfig | 9 ++++ > > > drivers/char/tpm/Makefile | 1 + > > > drivers/char/tpm/tpm_loongson.c | 84 +++++++++++++++++++++++++++++++++ > > > 3 files changed, 94 insertions(+) > > > create mode 100644 drivers/char/tpm/tpm_loongson.c > > > > > > diff --git a/drivers/char/tpm/Kconfig b/drivers/char/tpm/Kconfig > > > index dddd702b2..ba3924eb1 100644 > > > --- a/drivers/char/tpm/Kconfig > > > +++ b/drivers/char/tpm/Kconfig > > > @@ -189,6 +189,15 @@ config TCG_IBMVTPM > > > will be accessible from within Linux. To compile this driver > > > as a module, choose M here; the module will be called tpm_ibmvtpm. > > > > > > +config TCG_LOONGSON > > > + tristate "Loongson TPM Interface" > > > + depends on MFD_LOONGSON_SE > > > + help > > > + If you want to make Loongson TPM support available, say Yes and > > > + it will be accessible from within Linux. To compile this > > > + driver as a module, choose M here; the module will be called > > > + tpm_loongson. > > > + > > > config TCG_XEN > > > tristate "XEN TPM Interface" > > > depends on TCG_TPM && XEN > > > diff --git a/drivers/char/tpm/Makefile b/drivers/char/tpm/Makefile > > > index 9de1b3ea3..5b5cdc0d3 100644 > > > --- a/drivers/char/tpm/Makefile > > > +++ b/drivers/char/tpm/Makefile > > > @@ -46,3 +46,4 @@ obj-$(CONFIG_TCG_ARM_CRB_FFA) += tpm_crb_ffa.o > > > obj-$(CONFIG_TCG_VTPM_PROXY) += tpm_vtpm_proxy.o > > > obj-$(CONFIG_TCG_FTPM_TEE) += tpm_ftpm_tee.o > > > obj-$(CONFIG_TCG_SVSM) += tpm_svsm.o > > > +obj-$(CONFIG_TCG_LOONGSON) += tpm_loongson.o > > > diff --git a/drivers/char/tpm/tpm_loongson.c b/drivers/char/tpm/tpm_loongson.c > > > new file mode 100644 > > > index 000000000..5cbdb37f8 > > > --- /dev/null > > > +++ b/drivers/char/tpm/tpm_loongson.c > > > @@ -0,0 +1,84 @@ > > > +// SPDX-License-Identifier: GPL-2.0 > > > +/* Copyright (c) 2025 Loongson Technology Corporation Limited. */ > > > + > > > +#include > > > +#include > > > +#include > > > +#include > > > + > > > +#include "tpm.h" > > > + > > > +struct tpm_loongson_cmd { > > > + u32 cmd_id; > > > + u32 data_off; > > > + u32 data_len; > > > + u32 pad[5]; > > > +}; > > > + > > > +static int tpm_loongson_recv(struct tpm_chip *chip, u8 *buf, size_t count) > > > +{ > > > + struct loongson_se_engine *tpm_engine = dev_get_drvdata(&chip->dev); > > > + struct tpm_loongson_cmd *cmd_ret = tpm_engine->command_ret; > > > + > > > + if (cmd_ret->data_len > count) > > > + return -EIO; > > > + > > > + memcpy(buf, tpm_engine->data_buffer, cmd_ret->data_len); > > > + > > > + return cmd_ret->data_len; > > > +} > > > + > > > +static int tpm_loongson_send(struct tpm_chip *chip, u8 *buf, size_t count) > > > +{ > > > + struct loongson_se_engine *tpm_engine = dev_get_drvdata(&chip->dev); > > > + struct tpm_loongson_cmd *cmd = tpm_engine->command; > > > + > > > + if (count > tpm_engine->buffer_size) > > > + return -E2BIG; > > > + > > > + cmd->data_len = count; > > > + memcpy(tpm_engine->data_buffer, buf, count); > > > + > > > + return loongson_se_send_engine_cmd(tpm_engine); > > > +} > > > + > > > +static const struct tpm_class_ops tpm_loongson_ops = { > > > + .flags = TPM_OPS_AUTO_STARTUP, > > > + .recv = tpm_loongson_recv, > > > + .send = tpm_loongson_send, > > > +}; > > > + > > > +static int tpm_loongson_probe(struct platform_device *pdev) > > > +{ > > > + struct loongson_se_engine *tpm_engine; > > > + struct device *dev = &pdev->dev; > > > + struct tpm_loongson_cmd *cmd; > > > + struct tpm_chip *chip; > > > + > > > + tpm_engine = loongson_se_init_engine(dev->parent, SE_ENGINE_TPM); > > > + if (!tpm_engine) > > > + return -ENODEV; > > > + cmd = tpm_engine->command; > > > + cmd->cmd_id = SE_CMD_TPM; > > > + cmd->data_off = tpm_engine->buffer_off; > > > + > > > + chip = tpmm_chip_alloc(dev, &tpm_loongson_ops); > > > + if (IS_ERR(chip)) > > > + return PTR_ERR(chip); > > > + chip->flags = TPM_CHIP_FLAG_TPM2 | TPM_CHIP_FLAG_IRQ; > > > + dev_set_drvdata(&chip->dev, tpm_engine); > > > + > > > + return tpm_chip_register(chip); > > > +} > > > + > > > +static struct platform_driver tpm_loongson = { > > > + .probe = tpm_loongson_probe, > > > + .driver = { > > > + .name = "loongson-tpm", > > > > This patch looks otherwise great but I'd prefer here tho use > > "tpm_loongson_probe" for the value of the name field. > > Where does this stipulation come from? No other driver does this [0]. > driver.name should be a nicely formatted, human readable string > describing the name of the device. Not a function name. What defines "human-readable" here? I see both as somewhat the same level of "readability" ;-) > > [0] git grep -A15 "static struct platform_driver" | grep ".name = .*probe" What I'm getting: $ git grep -l -e platform_driver_register --or -e module_platform_driver drivers/char/tpm | xargs git grep "\.name" drivers/char/tpm/tpm_atmel.c: .name = "tpm_atmel", drivers/char/tpm/tpm_ftpm_tee.c: .name = "ftpm-tee", drivers/char/tpm/tpm_ftpm_tee.c: .name = "optee-ftpm", drivers/char/tpm/tpm_nsc.c: .name = "tpm_nsc", drivers/char/tpm/tpm_svsm.c: .name = "tpm-svsm", drivers/char/tpm/tpm_tis.c: .name = "tpm_tis", drivers/char/tpm/tpm_tis.c: .name = "tpm_tis", drivers/char/tpm/tpm_tis_synquacer.c: .name = "tpm_tis_synquacer", Do you consider e.g, "tpm_tis" as "less human-readable". I don't necessarily fight against the name chosen. Your arguments just plain no make sense, so I just merely want to understand this. That's all. > > -- > Lee Jones [李琼斯] BR, Jarkko