[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241005191555.GA10813@sol.localdomain>
Date: Sat, 5 Oct 2024 12:15:55 -0700
From: Eric Biggers <ebiggers@...nel.org>
To: Ram Kumar Dwivedi <quic_rdwivedi@...cinc.com>
Cc: manivannan.sadhasivam@...aro.org, alim.akhtar@...sung.com,
avri.altman@....com, bvanassche@....org, robh@...nel.org,
krzk+dt@...nel.org, conor+dt@...nel.org, andersson@...nel.org,
konrad.dybcio@...aro.org, James.Bottomley@...senpartnership.com,
martin.petersen@...cle.com, agross@...nel.org,
linux-arm-msm@...r.kernel.org, linux-scsi@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
quic_narepall@...cinc.com, quic_nitirawa@...cinc.com
Subject: Re: [PATCH V1 1/3] dt-bindings: ufs: qcom: Document ice
configuration table
On Sat, Oct 05, 2024 at 12:13:05PM +0530, Ram Kumar Dwivedi wrote:
> There are three algorithms supported for inline crypto engine:
> Floor based, Static and Instantaneous algorithm.
No. The algorithms supported by ICE are AES-XTS, AES-ECB, AES-CBC, etc. So I'm
afraid this terminology is already taken.
This new thing seems to be about how work is distributed among different
hardware cores, so calling these "ICE schedulers" or something might make sense.
- Eric
Powered by blists - more mailing lists