From: Md Sadre Alam <quic_mdalam@quicinc.com>
To: Ulf Hansson <ulf.hansson@linaro.org>,
Eric Biggers <ebiggers@google.com>,
Abel Vesa <abel.vesa@linaro.org>
Cc: <adrian.hunter@intel.com>, <linux-mmc@vger.kernel.org>,
<linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<quic_varada@quicinc.com>
Subject: Re: [PATCH v4] mmc: sdhci-msm: Enable ICE support for non-cmdq eMMC devices
Date: Thu, 13 Nov 2025 11:21:24 +0530 [thread overview]
Message-ID: <272f7c21-16d0-25db-4d09-51a987945c3e@quicinc.com> (raw)
In-Reply-To: <CAPDyKFomGKtznQ4wD8O83b6uAKfNkKhERjoivrbmSqtQODDDDA@mail.gmail.com>
Hi,
On 11/11/2025 11:02 PM, Ulf Hansson wrote:
> + Eric, Abel
>
> On Tue, 11 Nov 2025 at 11:46, Md Sadre Alam <quic_mdalam@quicinc.com> wrote:
>>
>> Enable Inline Crypto Engine (ICE) support for eMMC devices that operate
>> without Command Queue Engine (CQE).This allows hardware-accelerated
>> encryption and decryption for standard (non-CMDQ) requests.
>>
>> This patch:
>> - Adds ICE register definitions for non-CMDQ crypto configuration
>> - Implements a per-request crypto setup via sdhci_msm_ice_cfg()
>> - Hooks into the request path via mmc_host_ops.request
>>
>> With this, non-CMDQ eMMC devices can benefit from inline encryption,
>> improving performance for encrypted I/O while maintaining compatibility
>> with existing CQE crypto support.
>>
>> Signed-off-by: Md Sadre Alam <quic_mdalam@quicinc.com>
>> Acked-by: Adrian Hunter <adrian.hunter@intel.com>
>
> Please add Eric/Abel for any future submission of the patch as it's
> for ICE. I don't feel completely confident to apply this without some
> of their acks.
Thank you for the guidance. I completely understand your concern and
will make sure to include Eric and Abel in any future submissions
related to ICE.
Thanks,
Alam.
next prev parent reply other threads:[~2025-11-13 5:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 10:46 [PATCH v4] mmc: sdhci-msm: Enable ICE support for non-cmdq eMMC devices Md Sadre Alam
2025-11-11 17:32 ` Ulf Hansson
2025-11-13 5:51 ` Md Sadre Alam [this message]
2025-11-11 20:52 ` Eric Biggers
2025-11-13 7:11 ` Md Sadre Alam
2025-11-13 17:35 ` Eric Biggers
2025-11-17 7:21 ` Md Sadre Alam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=272f7c21-16d0-25db-4d09-51a987945c3e@quicinc.com \
--to=quic_mdalam@quicinc.com \
--cc=abel.vesa@linaro.org \
--cc=adrian.hunter@intel.com \
--cc=ebiggers@google.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=quic_varada@quicinc.com \
--cc=ulf.hansson@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).