Messages in this thread | | | Date | Fri, 28 Oct 2022 11:57:32 +0800 | From | Herbert Xu <> | Subject | Re: [PATCH] crypto/hisilicon: Add null judgment to the callback interface |
| |
On Fri, Sep 30, 2022 at 11:48:02AM +0800, liulongfang wrote: > > Even if the task is sent in synchronous mode, when using the hardware > driver, the hardware still informs the driver software through an > interrupt after completing the task, and the workqueue in the driver > software will call this callback function. > > And I found that the device drivers of other manufacturers under the > crypto subsystem are also in this asynchronous mode, and this problem > is also encountered when using the synchronous mode.
This still makes no sense to me.
Who is making an async request with no callback?
Cheers, -- Email: Herbert Xu <herbert@gondor.apana.org.au> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
| |