All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Qunqin Zhao <zhaoqunqin@loongson.cn>
Cc: Huacai Chen <chenhuacai@kernel.org>, Lee Jones <lee@kernel.org>,
	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 <guyinggang@loongson.cn>,
	Huacai Chen <chenhuacai@loongson.cn>
Subject: Re: [PATCH v11 3/4] tpm: Add a driver for Loongson TPM device
Date: Thu, 3 Jul 2025 01:25:43 +0300	[thread overview]
Message-ID: <aGWx5-XvdhpLdXEC@kernel.org> (raw)
In-Reply-To: <86b5e396-54d4-7b36-8848-06f41083ba59@loongson.cn>

On Fri, Jun 27, 2025 at 02:46:11PM +0800, Qunqin Zhao wrote:
> 
> 在 2025/6/27 上午2:29, Jarkko Sakkinen 写道:
> > On Thu, Jun 26, 2025 at 08:48:35PM +0800, Huacai Chen wrote:
> > > But there is another coherency, you can see this in the 1st patch:
> > > 
> > > +static const struct mfd_cell engines[] = {
> > > + { .name = "loongson-rng" },
> > > + { .name = "loongson-tpm" },
> > > +};
> > I thought already after ffa driver from ARM that I need to fix up
> > the naming a bit before it explodes. Thus, I'll stick to this.
> > 
> > And e.g., I could easily find DRM driver with opposite order.
> Next revision:
> 
> +static const struct mfd_cell engines[] = {
> +	{ .name = "loongson-rng" },
> +	{ .name = "tpm_loongson" },
> +};
> Then
> "loongson-rng" can match MFD and Crypto subsystem naming convention.
> "tpm_loongson" can match TPM subsystem naming convention.

Great, this works for me. Thank you, appreciate it!

> 
> 
> Thanks,
> Qunqin
> 
> > > Huacai
> > BR, Jarkko
> 

BR, Jarkko

  parent reply	other threads:[~2025-07-02 22:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19  2:51 [PATCH v11 0/4] dd Loongson Security Engine chip driver Qunqin Zhao
2025-06-19  2:51 ` [PATCH v11 1/4] mfd: Add support for Loongson Security Engine chip controller Qunqin Zhao
2025-07-02 15:18   ` Lee Jones
2025-06-19  2:51 ` [PATCH v11 2/4] crypto: loongson - add Loongson RNG driver support Qunqin Zhao
2025-06-19  2:51 ` [PATCH v11 3/4] tpm: Add a driver for Loongson TPM device Qunqin Zhao
2025-06-24 23:35   ` Jarkko Sakkinen
2025-06-25  8:05     ` Lee Jones
2025-06-25 11:46       ` Jarkko Sakkinen
2025-06-25 13:40         ` Lee Jones
2025-06-25 17:04           ` Jarkko Sakkinen
2025-06-26 10:30             ` Lee Jones
2025-06-26 10:59               ` Jarkko Sakkinen
2025-06-26 12:48                 ` Huacai Chen
2025-06-26 18:29                   ` Jarkko Sakkinen
2025-06-27  6:46                     ` Qunqin Zhao
2025-06-27 10:15                       ` Huacai Chen
2025-07-02 22:25                       ` Jarkko Sakkinen [this message]
2025-06-19  2:51 ` [PATCH v11 4/4] MAINTAINERS: Add entry for Loongson Security Engine drivers Qunqin Zhao
2025-06-19 15:22   ` 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=aGWx5-XvdhpLdXEC@kernel.org \
    --to=jarkko@kernel.org \
    --cc=chenhuacai@kernel.org \
    --cc=chenhuacai@loongson.cn \
    --cc=davem@davemloft.net \
    --cc=guyinggang@loongson.cn \
    --cc=herbert@gondor.apana.org.au \
    --cc=jgg@ziepe.ca \
    --cc=lee@kernel.org \
    --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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.