Subject: Re: [PATCH 1/2] crypto: Delete Qualcomm crypto engine driver

From: Demi Marie Obenour <[email-masked]>
Date: Mon, 25 May 2026 03:49:30 -0400

On 5/25/26 02:29, Kuldeep Singh wrote:
>> This driver is more than an order of magnitude slower than the CPU for
>> both encryption and hashing.  See:
>>
>>     https://lore.kernel.org/r/[email-masked]/
>>     https://lore.kernel.org/r/20250615031807.GA81869@sol/
>>
>> There are many examples of it having bugs as well, for example see the
>> second link above.
>>
>> That's why it had to be disabled via the cra_priority system.  This
>> driver was actively making Linux worse.
>>
>> This isn't particularly unique to drivers/crypto/, of course.  This one
>> we just have data on, so it's a bit clearer.
>>
>> I've yet to see any real reason to keep this driver.
> 
> https://lore.kernel.org/all/[email-masked]/
> Kindly check my latest reply to the thread. There are numerous usecases
> like DRM(Digital rights management) coming up and qce driver is required
> for secure content.

1. This content is restricted.  It's no more secure.

2. General purpose (desktop, laptop) systems won't be able to display
   restricted content.  To the best of my knowledge, the only Wayland
   compositors that support restricted content are Weston and Chromium
   OS's compositor.

3. Will this code be useful without out of tree drivers?

4. Does this use the existing crypto APIs or a separate API?
-- 
Sincerely,
Demi Marie Obenour (she/her/hers)