public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: "Peng.Zhou" <peng.zhou@mediatek.com>
Cc: linux-mmc@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	devicetree@vger.kernel.org, linux-fscrypt@vger.kernel.org,
	Satya Tangirala <satyat@google.com>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Asutosh Das <asutoshd@codeaurora.org>,
	Rob Herring <robh+dt@kernel.org>,
	Neeraj Soni <neersoni@codeaurora.org>,
	Barani Muthukumaran <bmuthuku@codeaurora.org>,
	Stanley Chu <stanley.chu@mediatek.com>,
	Konrad Dybcio <konradybcio@gmail.com>
Subject: Re: [PATCH v3 0/9] eMMC inline encryption support
Date: Tue, 15 Dec 2020 09:52:51 -0800	[thread overview]
Message-ID: <X9j38+54HGOEK7C/@sol.localdomain> (raw)
In-Reply-To: <1608019654.31445.8.camel@mbjsdccf07>

On Tue, Dec 15, 2020 at 04:07:34PM +0800, Peng.Zhou wrote:
> > 
> I had verified this patchset in MT6853 (A 5G mobile smartphone platform
> of Mediatek which meets eMMC v5.2 specification) and they work normally
> in Android environment.
> Reviewed and Tested by: Peng Zhou<peng.zhou@mediatek.com>

Thanks Peng.  Is your Reviewed-and-tested-by for the whole patchset, or just for
patches 1-5?  Patches 6-9 only affect Qualcomm hardware.

Also, were many changes to mtk-sd.c required to get the crypto support working
on your hardware, or was it just a matter of making a SMC call and setting the
crypto capability flag, like it was for ufs-mediatek (commit 46426552e74f)?
If you could send your patch for mtk-sd.c on top of this patchset, that would be
helpful for people to see.

- Eric

      parent reply	other threads:[~2020-12-15 17:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09  4:42 [PATCH v3 0/9] eMMC inline encryption support Eric Biggers
2020-12-09  4:42 ` [PATCH v3 1/9] mmc: add basic support for inline encryption Eric Biggers
2020-12-09  4:42 ` [PATCH v3 2/9] mmc: cqhci: rename cqhci.c to cqhci-core.c Eric Biggers
2020-12-09  4:42 ` [PATCH v3 3/9] mmc: cqhci: initialize upper 64 bits of 128-bit task descriptors Eric Biggers
2020-12-09  4:42 ` [PATCH v3 4/9] mmc: cqhci: add support for inline encryption Eric Biggers
2020-12-09  4:42 ` [PATCH v3 5/9] mmc: cqhci: add cqhci_host_ops::program_key Eric Biggers
2020-12-09  4:42 ` [PATCH v3 6/9] firmware: qcom_scm: update comment for ICE-related functions Eric Biggers
2020-12-09  4:42 ` [PATCH v3 7/9] dt-bindings: mmc: sdhci-msm: add ICE registers and clock Eric Biggers
2020-12-10 15:18   ` Rob Herring
2020-12-09  4:42 ` [PATCH v3 8/9] arm64: dts: qcom: sdm630: add ICE registers and clocks Eric Biggers
2020-12-09  4:42 ` [PATCH v3 9/9] mmc: sdhci-msm: add Inline Crypto Engine support Eric Biggers
     [not found] ` <1608019654.31445.8.camel@mbjsdccf07>
2020-12-15 17:52   ` Eric Biggers [this message]

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=X9j38+54HGOEK7C/@sol.localdomain \
    --to=ebiggers@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=agross@kernel.org \
    --cc=asutoshd@codeaurora.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=bmuthuku@codeaurora.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-fscrypt@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=neersoni@codeaurora.org \
    --cc=peng.zhou@mediatek.com \
    --cc=robh+dt@kernel.org \
    --cc=satyat@google.com \
    --cc=stanley.chu@mediatek.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