From: "Alim Akhtar" <alim.akhtar@samsung.com>
To: "'Avri Altman'" <Avri.Altman@wdc.com>,
"'Martin K. Petersen'" <martin.petersen@oracle.com>,
"'Satya Tangirala'" <satyat@google.com>,
<asutoshd@codeaurora.org>
Cc: <linux-scsi@vger.kernel.org>,
"'Barani Muthukumaran'" <bmuthuku@qti.qualcomm.com>,
"'Kuohong Wang'" <kuohong.wang@mediatek.com>,
"'Kim Boojin'" <boojin.kim@samsung.com>
Subject: RE: [PATCH v2 0/3] Inline Encryption support for UFS
Date: Sun, 21 Jun 2020 23:24:30 +0530 [thread overview]
Message-ID: <000001d647f5$05a494c0$10edbe40$@samsung.com> (raw)
In-Reply-To: <SN6PR04MB4640005BEC3EE690CB904298FC960@SN6PR04MB4640.namprd04.prod.outlook.com>
Thanks Avri for CCing me.
> -----Original Message-----
> From: Avri Altman <Avri.Altman@wdc.com>
> Sent: 21 June 2020 18:05
> To: Martin K. Petersen <martin.petersen@oracle.com>; Satya Tangirala
> <satyat@google.com>; alim.akhtar@samsung.com; asutoshd@codeaurora.org
> Cc: linux-scsi@vger.kernel.org; Barani Muthukumaran
> <bmuthuku@qti.qualcomm.com>; Kuohong Wang
> <kuohong.wang@mediatek.com>; Kim Boojin <boojin.kim@samsung.com>
> Subject: RE: [PATCH v2 0/3] Inline Encryption support for UFS
>
> +Alim & Asutosh
>
> Hi Satya,
>
> >
> > Avri,
> >
> > > 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.
> >
> > I'd appreciate it if you could review this series.
> >
> > Thanks!
> >
> > --
> > Martin K. Petersen Oracle Linux Engineering
> A quick question and a comment:
>
> Does the IE infrastructure that you've added to the block layer invented
for ufs?
> Do you see other devices using it in the future?
>
> Today, chipset vendors are using a different scheme for their IE.
> Need their ack before reviewing your patches.
>
Yes, as of today at least in Samsung HCI, we use additional HW blocks to
handle all the crypto part.
(Though I need to check the status on the recent SoCs).
However given the fact that UFSHCI 2.1 spec does includes Crypto support,
and going by threads that you shared, looks like other
Vendors does uses IE. I am inclined toward getting this reviewed.
> Thanks,
> Avri
next prev parent reply other threads:[~2020-06-21 17:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 2:47 [PATCH v2 0/3] Inline Encryption support for UFS Satya Tangirala
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 [this message]
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='000001d647f5$05a494c0$10edbe40$@samsung.com' \
--to=alim.akhtar@samsung.com \
--cc=Avri.Altman@wdc.com \
--cc=asutoshd@codeaurora.org \
--cc=bmuthuku@qti.qualcomm.com \
--cc=boojin.kim@samsung.com \
--cc=kuohong.wang@mediatek.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=satyat@google.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 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.