From: Parshuram Thombare <pthombar@cadence.com>
To: <axboe@kernel.dk>, <vinholikatti@gmail.com>,
<jejb@linux.vnet.ibm.com>, <martin.petersen@oracle.com>,
<mchehab+samsung@kernel.org>, <gregkh@linuxfoundation.org>,
<davem@davemloft.net>, <akpm@linux-foundation.org>,
<nicolas.ferre@microchip.com>, <arnd@arndb.de>,
<linux-kernel@vger.kernel.org>, <linux-block@vger.kernel.org>,
<linux-scsi@vger.kernel.org>, <tj@kernel.org>, <jbacik@fb.com>,
<michaelcallahan@fb.com>, <snitzer@redhat.com>, <osandov@fb.com>,
<keith.busch@intel.com>, <ming.lei@redhat.com>, <shli@fb.com>,
<dennisszhou@gmail.com>
Cc: <adouglas@cadence.com>, <jank@cadence.com>, <rafalc@cadence.com>,
<pthombar@cadence.com>
Subject: [PATCH 0/2] scsi: ufs: add real time/inline crypto support to UFS HCD
Date: Tue, 11 Dec 2018 09:49:10 +0000 [thread overview]
Message-ID: <20181211094910.GA28288@lvlogina.cadence.com> (raw)
Hello,
This patch series add inline / real time encryption support to UFS
host controller driver. It include following patches
0001-block-add-bi_crypto_ctx-variable-in-struct-bio.patch
Add 'void *bi_crypto_ctx' variable in 'struct bio' to embded crypto
configuration information, which is used by low level driver when
bio is processed. This field can also be useful to support inline
encryption in other protocols also.
0002-scsi-ufs-add-inline-crypto-support-to-UFS-HCD.patch
This patch depends on patch [0/1] in this series.
Patch include changes regarding UFS controller
crypto support. Inline crypto support is provided by using new
device mapper called 'crypt-ufs'. Inline encryption can be enabled on
UFS device by creating mapping using tool like dmsetup and mapper
'crypt-ufs'. Patch is tested on Cadence UFS controller which currently
support AES-ECB inline encryption.
As part of [PATCH 2/2], MAINTAINERS file is modified to add name as
supporter of ufshcd crypto files.
Regards,
Parshuram Thombare
Parshuram Thombare (2):
block: add bi_crypto_ctx variable in struct bio
scsi: ufs: add inline crypto support to UFS HCD
MAINTAINERS | 7 +
block/Kconfig | 5 +
drivers/scsi/ufs/Kconfig | 12 +
drivers/scsi/ufs/Makefile | 1 +
drivers/scsi/ufs/ufshcd-crypto.c | 453 ++++++++++++++++++++++++++++++++++++++
drivers/scsi/ufs/ufshcd-crypto.h | 102 +++++++++
drivers/scsi/ufs/ufshcd.c | 27 +++-
drivers/scsi/ufs/ufshcd.h | 6 +
drivers/scsi/ufs/ufshci.h | 1 +
include/linux/blk_types.h | 4 +
10 files changed, 617 insertions(+), 1 deletions(-)
create mode 100644 drivers/scsi/ufs/ufshcd-crypto.c
create mode 100644 drivers/scsi/ufs/ufshcd-crypto.h
next reply other threads:[~2018-12-11 9:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 9:49 Parshuram Thombare [this message]
2018-12-11 14:06 ` [PATCH 0/2] scsi: ufs: add real time/inline crypto support to UFS HCD Christoph Hellwig
2018-12-11 18:22 ` Parshuram Raju Thombare
2018-12-12 7:40 ` Christoph Hellwig
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=20181211094910.GA28288@lvlogina.cadence.com \
--to=pthombar@cadence.com \
--cc=adouglas@cadence.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=dennisszhou@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jank@cadence.com \
--cc=jbacik@fb.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mchehab+samsung@kernel.org \
--cc=michaelcallahan@fb.com \
--cc=ming.lei@redhat.com \
--cc=nicolas.ferre@microchip.com \
--cc=osandov@fb.com \
--cc=rafalc@cadence.com \
--cc=shli@fb.com \
--cc=snitzer@redhat.com \
--cc=tj@kernel.org \
--cc=vinholikatti@gmail.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).