From: Eric Biggers <ebiggers@kernel.org>
To: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-mmc@vger.kernel.org,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Satya Tangirala <satyat@google.com>
Subject: Re: [RFC] how to support ADMA3 and emmc CQ and inline encryption at the same time
Date: Tue, 29 Dec 2020 10:17:43 -0800 [thread overview]
Message-ID: <X+tyxxxjs/pNk85H@sol.localdomain> (raw)
In-Reply-To: <20201229164602.2dd49d28@xhacker.debian>
On Tue, Dec 29, 2020 at 04:46:02PM +0800, Jisheng Zhang wrote:
> Hi,
>
> Two patch series:
>
> *emmc inline encryption
> Recently Eric sent out emmc inline encryption patches, per my understanding
> the emmc inline encryption based on CQ interface:cqhci.
>
> *ADMA3 support
> Baolin send out ADMA3 support patches: https://lkml.org/lkml/2020/4/26/125
> which makes use of the ADMA3 transfer in mmc software queue.
>
> Per my understanding, ADMA3 is focusing on the host side while the emmc CQ
> focuses on emmc card side, they don't conflict with each other. But current
> mmc_blk_cqe_issue_rw_rq() goes through either hsq or cqe code path but not both.
>
> So how can ADMA3 and CQE be used at the same time?
>
Only the hardware CQE provides inline encryption support. In particular, the
hardware interface to program keyslots uses the CQE registers, as does the
hardware interface to assign keyslots and DUNs to particular read/write
requests. So my understanding is that eMMC inline encryption isn't compatible
with eMMC commands being issued in ways other than the hardware CQE, such as via
the HSQ (host software queue) feature, or via "packed requests". So those
features can't be enabled in combination with inline encryption.
- Eric
next prev parent reply other threads:[~2020-12-29 18:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 8:46 [RFC] how to support ADMA3 and emmc CQ and inline encryption at the same time Jisheng Zhang
2020-12-29 18:17 ` Eric Biggers [this message]
2020-12-30 12:26 ` Adrian Hunter
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=X+tyxxxjs/pNk85H@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=Jisheng.Zhang@synaptics.com \
--cc=adrian.hunter@intel.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=linux-mmc@vger.kernel.org \
--cc=satyat@google.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