public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Stanley Chu <stanley.chu@mediatek.com>
To: <linux-scsi@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<robh+dt@kernel.org>, <robh@kernel.org>, <mark.rutland@arm.com>,
	<chunfeng.yun@mediatek.com>, <yingjoe.chen@mediatek.com>,
	<kishon@ti.com>, <martin.petersen@oracle.com>,
	<avri.altman@wdc.com>, <alim.akhtar@samsung.com>,
	<pedrom.sousa@synopsys.com>
Cc: <vivek.gautam@codeaurora.org>, <liwei213@huawei.com>,
	<linux-mediatek@lists.infradead.org>, <matthias.bgg@gmail.com>,
	<kuohong.wang@mediatek.com>, <peter.wang@mediatek.com>,
	<chun-hung.wu@mediatek.com>, <andy.teng@mediatek.com>,
	<chaotian.jing@mediatek.com>, <cc.chou@mediatek.com>,
	<jiajie.hao@mediatek.com>, <arvin.wang@mediatek.com>,
	<henryc.chen@mediatek.com>,
	Stanley Chu <stanley.chu@mediatek.com>
Subject: [PATCH v3 0/2] scsi: ufs-mediatek: Support performance mode for inline encryption engine
Date: Mon, 14 Sep 2020 13:00:50 +0800	[thread overview]
Message-ID: <20200914050052.3974-1-stanley.chu@mediatek.com> (raw)

Hi Martin, Rob, Avri,

This series adds high-performance mode support for MediaTek UFS inline encryption engine.
This feature is only required in specific platforms, i.e., MT8192 series.

Please help consider this patch set in kernel v5.10.

Thanks.

Changes since v2:
	- Specify required minimum vcore voltage in device tree instead of hard-coded.

Changes since v1:
	- Remove unnecessary printf.

Stanley Chu (2):
  scsi: ufs-mediatek: Support performance mode for inline encryption
    engine
  dt-bindings: ufs-mediatek: Add mt8192-ufshci compatible string

 .../devicetree/bindings/ufs/ufs-mediatek.txt  |   4 +-
 drivers/scsi/ufs/ufs-mediatek.c               | 176 +++++++++++++++++-
 drivers/scsi/ufs/ufs-mediatek.h               |  22 +++
 3 files changed, 195 insertions(+), 7 deletions(-)

-- 
2.18.0

             reply	other threads:[~2020-09-14  5:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14  5:00 Stanley Chu [this message]
2020-09-14  5:00 ` [PATCH v3 1/2] scsi: ufs-mediatek: Support performance mode for inline encryption engine Stanley Chu
2020-09-14  5:00 ` [PATCH v3 2/2] dt-bindings: ufs-mediatek: Add mt8192-ufshci compatible string Stanley Chu
2020-09-22 23:15   ` Rob Herring
2020-09-23  0:38 ` [PATCH v3 0/2] scsi: ufs-mediatek: Support performance mode for inline encryption engine Martin K. Petersen
2020-09-30  3:34 ` Martin K. Petersen

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=20200914050052.3974-1-stanley.chu@mediatek.com \
    --to=stanley.chu@mediatek.com \
    --cc=alim.akhtar@samsung.com \
    --cc=andy.teng@mediatek.com \
    --cc=arvin.wang@mediatek.com \
    --cc=avri.altman@wdc.com \
    --cc=cc.chou@mediatek.com \
    --cc=chaotian.jing@mediatek.com \
    --cc=chun-hung.wu@mediatek.com \
    --cc=chunfeng.yun@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=henryc.chen@mediatek.com \
    --cc=jiajie.hao@mediatek.com \
    --cc=kishon@ti.com \
    --cc=kuohong.wang@mediatek.com \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=liwei213@huawei.com \
    --cc=mark.rutland@arm.com \
    --cc=martin.petersen@oracle.com \
    --cc=matthias.bgg@gmail.com \
    --cc=pedrom.sousa@synopsys.com \
    --cc=peter.wang@mediatek.com \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=vivek.gautam@codeaurora.org \
    --cc=yingjoe.chen@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