mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Qunqin Zhao <zhaoqunqin@loongson.cn>
To: Lee Jones <lee@kernel.org>, Huacai Chen <chenhuacai@kernel.org>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	jarkko@kernel.org
Cc: davem@davemloft.net, peterhuewe@gmx.de,
	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
Subject: Re: [PATCH v8 0/5] Add Loongson Security Engine chip driver
Date: Wed, 30 Apr 2025 17:10:04 +0800	[thread overview]
Message-ID: <0f2a34ce-3e4b-7dda-4835-34bfd0ef60fc@loongson.cn> (raw)
In-Reply-To: <20250430085809.GD1567507@google.com>


在 2025/4/30 下午4:58, Lee Jones 写道:
> On Wed, 30 Apr 2025, Huacai Chen wrote:
>
>> On Wed, Apr 30, 2025 at 4:47 PM Qunqin Zhao <zhaoqunqin@loongson.cn> wrote:
>>>
>>> 在 2025/4/30 下午4:18, Herbert Xu 写道:
>>>> 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.
>>> Hi, Herbert, thanks for your reply.
>>>
>>> In future it just add child platform devices  name(sm2, sm3, sm4) to
>>> "struct  mfd_cell engines".
>>>
>>>
>>> Hi, Huaci
>>>
>>> Let's go via Herbert's crypto tree for the base driver patch under
>>> drivers/crypto/loongson/,
>>>
>>> What do you think of it?
>> In my opinion drivers/mfd is better, because another user is in
>> drivers/char rather than drivers/crypto.
>>
>> But if moving to drivers/crypto is what Lee Jones wants, then everything is OK.
> You can move the driver, but then you must not reference or use the MFD API.

Then looks like i should move it back to drivers/mfd,  will do that in 
next revision.

Thank you very much for everyone's replies.

BR, Qunqin.

>


  reply	other threads:[~2025-04-30  9:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-18  9:35 Qunqin Zhao
2025-04-20  7:17 ` Huacai Chen
2025-04-30  8:14   ` Qunqin Zhao
2025-04-30  8:18     ` Herbert Xu
2025-04-30  8:45       ` Qunqin Zhao
2025-04-30  8:53         ` Huacai Chen
2025-04-30  8:58           ` Lee Jones
2025-04-30  9:10             ` Qunqin Zhao [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-18  9:34 Qunqin Zhao

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=0f2a34ce-3e4b-7dda-4835-34bfd0ef60fc@loongson.cn \
    --to=zhaoqunqin@loongson.cn \
    --cc=chenhuacai@kernel.org \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=jarkko@kernel.org \
    --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=pmenzel@molgen.mpg.de \
    /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®