[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e7ad2dd5-78a5-618d-f450-ef0eed430adf@huawei.com>
Date: Mon, 19 May 2025 20:54:18 +0800
From: liulongfang <liulongfang@...wei.com>
To: Herbert Xu <herbert@...dor.apana.org.au>, Qunqin Zhao
<zhaoqunqin@...ngson.cn>
CC: <lee@...nel.org>, <davem@...emloft.net>, <peterhuewe@....de>,
<jarkko@...nel.org>, <linux-kernel@...r.kernel.org>,
<loongarch@...ts.linux.dev>, <linux-crypto@...r.kernel.org>, <jgg@...pe.ca>,
<linux-integrity@...r.kernel.org>, <pmenzel@...gen.mpg.de>, Yinggang Gu
<guyinggang@...ngson.cn>, Huacai Chen <chenhuacai@...ngson.cn>
Subject: Re: [PATCH v9 2/5] crypto: loongson - add Loongson RNG driver support
On 2025/5/19 16:22, Herbert Xu wrote:
> On Mon, May 19, 2025 at 04:13:14PM +0800, Qunqin Zhao wrote:
>>
>> Then the HISI TRNG driver isn't a right demo?
>
> Yes the hisi trng looks wrong too.
>
We are currently updating and plan to create software TFM for users when
they unable to apply for hardware device queues, ensuring that users' tasks
can continue to be completed.
Thanks,
Longfang.
>> This can also avoid concurrent access to a device, otherwise i need to
>>
>> add mutex_lock/unlock in generate and seed callback.
>
> Randomly failing the tfm allocation is not a solution to resource
> control :)
>
> Cheers,
>
Powered by blists - more mailing lists