[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <ee65851c-4149-4927-a2e7-356cdce2ba25@app.fastmail.com>
Date: Tue, 14 Jan 2025 11:17:45 +0100
From: "Arnd Bergmann" <arnd@...db.de>
To: "Qunqin Zhao" <zhaoqunqin@...ngson.cn>, "Lee Jones" <lee@...nel.org>,
"Herbert Xu" <herbert@...dor.apana.org.au>,
"Greg Kroah-Hartman" <gregkh@...uxfoundation.org>
Cc: linux-kernel@...r.kernel.org, loongarch@...ts.linux.dev,
"David S . Miller" <davem@...emloft.net>, linux-crypto@...r.kernel.org,
"derek.kiernan@....com" <derek.kiernan@....com>,
"dragan.cvetic@....com" <dragan.cvetic@....com>,
"Yinggang Gu" <guyinggang@...ngson.cn>
Subject: Re: [PATCH v1 3/3] misc: ls6000se-sdf: Add driver for Loongson 6000SE SDF
On Tue, Jan 14, 2025, at 10:55, Qunqin Zhao wrote:
> Loongson Secure Device Function device supports the functions specified
> in "GB/T 36322-2018". This driver is only responsible for sending user
> data to SDF devices or returning SDF device data to users.
I haven't been able to find a public version of the standard, but
from the table of contents it sounds like this is a standard for
cryptographic functions that would otherwise be implemented by a
driver in drivers/crypto/ so it can use the normal abstractions
for both userspace and in-kernel users.
Is there some reason this doesn't work?
Arnd
Powered by blists - more mailing lists