devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peng Zhou <peng.zhou@mediatek.com>
To: Eric Biggers <ebiggers@kernel.org>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Chaotian Jing <chaotian.jing@mediatek.com>,
	<linux-mmc@vger.kernel.org>
Cc: <devicetree@vger.kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Satya Tangirala <satyat@google.com>,
	Wulin Li <wulin.li@mediatek.com>,
	Peng Zhou <peng.zhou@mediatek.com>,
	Peng Zhou <Peng.Zhou@mediatek.com>
Subject: [PATCH v2 0/4] MediaTek eMMC inline encryption support
Date: Tue, 9 Mar 2021 09:53:32 +0800	[thread overview]
Message-ID: <20210309015331.10457-1-peng.zhou@mediatek.com> (raw)

From: Peng Zhou <Peng.Zhou@mediatek.com>

Hello,

Mediatek eMMC hardware IP has Inline Crypto Engine (ICE),
we support inline encryption now.

For Inline Crypto Engine (ICE), see:
- https://lore.kernel.org/linux-arm-msm/20210126001456.382989-2-ebiggers@kernel.org/T/

Changed in v2:
- fix email format
- change some description

Peng Zhou (4):
  mmc: Mediatek: add Inline Crypto Engine support
  mmc: Mediatek: enable crypto hardware engine
  arm64: dts: Mediatek: MT6779: add mmc node with ICE setting
  dt-bingdings: mmc: Mediatek: add ICE clock

 .../devicetree/bindings/mmc/mtk-sd.yaml       |  6 ++-
 arch/arm64/boot/dts/mediatek/mt6779.dtsi      | 14 +++++++
 drivers/mmc/host/mtk-sd.c                     | 42 ++++++++++++++++++-
 3 files changed, 59 insertions(+), 3 deletions(-)

-- 
2.18.0

             reply	other threads:[~2021-03-09  2:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09  1:53 Peng Zhou [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-03-09  1:42 [PATCH v2 0/4] MediaTek eMMC inline encryption support Peng Zhou
     [not found] <20210308080855.30459-1-peng.zhou@mediatek.com>
2021-03-08 23:02 ` Eric Biggers
2021-03-08  8:33 Mason Zhang
2021-03-08  7:39 Mason Zhang

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=20210309015331.10457-1-peng.zhou@mediatek.com \
    --to=peng.zhou@mediatek.com \
    --cc=adrian.hunter@intel.com \
    --cc=chaotian.jing@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=ebiggers@kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=satyat@google.com \
    --cc=ulf.hansson@linaro.org \
    --cc=wulin.li@mediatek.com \
    /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).