From: Mengqi Zhang <mengqi.zhang@mediatek.com>
To: <chaotian.jing@mediatek.com>, <ulf.hansson@linaro.org>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<matthias.bgg@gmail.com>, <wenbin.mei@mediatek.com>,
<angelogioacchino.delregno@collabora.com>
Cc: <linux-mmc@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH v2 0/2] Mediatek eMMC Inline Crypto Engine support
Date: Fri, 4 Nov 2022 17:58:46 +0800 [thread overview]
Message-ID: <20221104095848.27444-1-mengqi.zhang@mediatek.com> (raw)
Change in v2
- change patch 1 commit title
- change patch 2 commit title, and correct commit message
- add crypto clock description base on new code base
Mediatek eMMC hardware IP has Inline Crypto Engine (ICE), we support inline encryption now.
This patchset supports Mediatek eMMC inline encryption which meets the upcoming version of the eMMC specification such as v5.1 or v5.2.
Patch 1, add crypto clock control flow in mtk-sd driver, patch 2, document the device tree description about crypto clock.
Mengqi Zhang (2):
mmc: mtk-sd: add Inline Crypto Engine clock control
dt-bindings: mmc: mtk-sd: add Inline Crypto Engine clock
.../devicetree/bindings/mmc/mtk-sd.yaml | 22 +++++++++++++++++++
drivers/mmc/host/mtk-sd.c | 12 ++++++++++
2 files changed, 34 insertions(+)
--
2.25.1
next reply other threads:[~2022-11-04 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 9:58 Mengqi Zhang [this message]
2022-11-04 15:19 ` [PATCH v2 0/2] Mediatek eMMC Inline Crypto Engine support Krzysztof Kozlowski
-- strict thread matches above, loose matches on Subject: below --
2022-11-04 9:51 Mengqi 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=20221104095848.27444-1-mengqi.zhang@mediatek.com \
--to=mengqi.zhang@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chaotian.jing@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=wenbin.mei@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).