From: Satya Tangirala <satyat@google.com>
To: linux-scsi@vger.kernel.org
Cc: Barani Muthukumaran <bmuthuku@qti.qualcomm.com>,
Kuohong Wang <kuohong.wang@mediatek.com>,
Kim Boojin <boojin.kim@samsung.com>,
Satya Tangirala <satyat@google.com>
Subject: [PATCH v2 0/3] Inline Encryption support for UFS
Date: Thu, 18 Jun 2020 02:47:33 +0000 [thread overview]
Message-ID: <20200618024736.97207-1-satyat@google.com> (raw)
This patch series adds support for inline encryption to UFS using
the inline encryption support in the block layer. It follows the JEDEC
UFSHCI v2.1 specification, which defines inline encryption for UFS.
This patch series previously went through a number of iterations as
part of the "Inline Encryption Support" patchset (last version was v13:
https://lkml.kernel.org/r/20200514003727.69001-1-satyat@google.com).
There aren't any significant changes here from that version.
This patch series is based on v5.8-rc1.
Patch 1 introduces the crypto registers and struct definitions defined
in the UFSHCI v2.1 spec.
Patch 2 introduces functions to manipulate the UFS inline encryption
hardware (again in line with the UFSHCI v2.1 spec) via the block
layer keyslot manager. Device specific drivers must set the
UFSHCD_CAP_CRYPTO in hba->caps before ufshcd_hba_init_crypto is called
to opt-in to inline encryption support.
Patch 3 wires up ufshcd.c with the UFS crypto API introduced in Patch 2.
This patch series has been tested on some Qualcomm chipsets (on the
db845c, sm8150-mtp and sm8250-mtp) using some additional patches at
https://lkml.kernel.org/linux-scsi/20200501045111.665881-1-ebiggers@kernel.org/
and on some Mediatek chipsets using the additional patch in
https://lkml.kernel.org/linux-scsi/20200304022101.14165-1-stanley.chu@mediatek.com/.
These additional patches are required because these chipsets need certain
additional behaviour not specified within the UFSHCI v2.1 spec.
Thanks a lot to all the folks who tested this out!
Changes v1 => v2
- handle OCS_DEVICE_FATAL_ERROR explicitly in ufshcd_transfer_rsp_status
Satya Tangirala (3):
scsi: ufs: UFS driver v2.1 spec crypto additions
scsi: ufs: UFS crypto API
scsi: ufs: Add inline encryption support to UFS
drivers/scsi/ufs/Kconfig | 9 ++
drivers/scsi/ufs/Makefile | 1 +
drivers/scsi/ufs/ufshcd-crypto.c | 226 +++++++++++++++++++++++++++++++
drivers/scsi/ufs/ufshcd-crypto.h | 60 ++++++++
drivers/scsi/ufs/ufshcd.c | 47 ++++++-
drivers/scsi/ufs/ufshcd.h | 24 ++++
drivers/scsi/ufs/ufshci.h | 67 ++++++++-
7 files changed, 427 insertions(+), 7 deletions(-)
create mode 100644 drivers/scsi/ufs/ufshcd-crypto.c
create mode 100644 drivers/scsi/ufs/ufshcd-crypto.h
--
2.27.0.290.gba653c62da-goog
next reply other threads:[~2020-06-18 2:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 2:47 Satya Tangirala [this message]
2020-06-18 2:47 ` [PATCH v2 1/3] scsi: ufs: UFS driver v2.1 spec crypto additions Satya Tangirala
2020-06-18 2:47 ` [PATCH v2 2/3] scsi: ufs: UFS crypto API Satya Tangirala
2020-06-18 2:47 ` [PATCH v2 3/3] scsi: ufs: Add inline encryption support to UFS Satya Tangirala
2020-06-23 10:57 ` Alim Akhtar
2020-06-20 3:17 ` [PATCH v2 0/3] Inline Encryption support for UFS Martin K. Petersen
2020-06-20 8:28 ` Avri Altman
2020-06-21 12:35 ` Avri Altman
2020-06-21 12:47 ` Avri Altman
2020-06-21 17:46 ` Eric Biggers
2020-06-21 17:54 ` Alim Akhtar
2020-06-21 19:26 ` Eric Biggers
2020-06-22 7:09 ` Avri Altman
2020-06-21 18:24 ` Satya Tangirala
2020-06-21 18:49 ` Eric Biggers
2020-06-22 7:34 ` [PATCH v2 3/3] scsi: ufs: Add inline encryption support to UFS Avri Altman
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=20200618024736.97207-1-satyat@google.com \
--to=satyat@google.com \
--cc=bmuthuku@qti.qualcomm.com \
--cc=boojin.kim@samsung.com \
--cc=kuohong.wang@mediatek.com \
--cc=linux-scsi@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.