mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: herbert@gondor.apana.org.au, jarkko@kernel.org,
	Qunqin Zhao <zhaoqunqin@loongson.cn>
Cc: 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
Subject: Re: [PATCH v12 0/4] Add Loongson Security Engine chip driver
Date: Tue, 2 Sep 2025 12:33:58 +0100	[thread overview]
Message-ID: <20250902113358.GI2163762@google.com> (raw)
In-Reply-To: <175681275359.2293173.7663755797512449740.b4-ty@kernel.org>

On Tue, 02 Sep 2025, Lee Jones wrote:

> On Sat, 05 Jul 2025 15:20:41 +0800, Qunqin Zhao 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.
> > 
> > [...]
> 
> Applied, thanks!
> 
> [1/4] mfd: Add support for Loongson Security Engine chip controller
>       commit: e551fa3159e3050c26ff010c3b595b45d7eb071a
> [2/4] crypto: loongson - add Loongson RNG driver support
>       commit: 766b2d724c8df071031412eea902b566a0049c31
> [3/4] tpm: Add a driver for Loongson TPM device
>       commit: 5c83b07df9c5a6e063328c5b885de79f8e8f0263
> [4/4] MAINTAINERS: Add entry for Loongson Security Engine drivers
>       commit: 74fddd5fbab879a7d039d9fb49af923927a64811

Submitted for testing.  I'll send out a PR once successful.

Note to self: ib-mfd-char-crypto-6.18

-- 
Lee Jones [李琼斯]

  reply	other threads:[~2025-09-02 11:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-05  7:20 Qunqin Zhao
2025-07-05  7:20 ` [PATCH v12 1/4] mfd: Add support for Loongson Security Engine chip controller Qunqin Zhao
2025-07-05  7:20 ` [PATCH v12 2/4] crypto: loongson - add Loongson RNG driver support Qunqin Zhao
2025-08-19 12:55   ` Lee Jones
2025-08-20  2:33     ` Herbert Xu
2025-07-05  7:20 ` [PATCH v12 3/4] tpm: Add a driver for Loongson TPM device Qunqin Zhao
2025-07-07  9:48   ` Stefano Garzarella
2025-07-26  7:05     ` Qunqin Zhao
2025-07-19 12:09   ` Jarkko Sakkinen
2025-07-20  1:05     ` Huacai Chen
2025-07-05  7:20 ` [PATCH v12 4/4] MAINTAINERS: Add entry for Loongson Security Engine drivers Qunqin Zhao
2025-09-02 11:32 ` [PATCH v12 0/4] Add Loongson Security Engine chip driver Lee Jones
2025-09-02 11:33   ` Lee Jones [this message]
2025-09-02 12:42 ` [GIT PULL] Immutable branch between MFD, Char and Crypto due for the v6.18 merge window Lee Jones
2025-09-12 21:32   ` Nathan Chancellor
2025-09-16  7:58     ` Lee Jones
2025-09-16  8:00       ` Lee Jones
2025-09-16 19:16       ` Nathan Chancellor
2025-09-17  9:38         ` Lee Jones
2025-09-17 17:12           ` Nathan Chancellor

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=20250902113358.GI2163762@google.com \
    --to=lee@kernel.org \
    --cc=davem@davemloft.net \
    --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=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®