From: Thara Gopinath <thara.gopinath@linaro.org>
To: Eric Biggers <ebiggers@kernel.org>,
linux-scsi@vger.kernel.org, linux-arm-msm@vger.kernel.org
Cc: linux-block@vger.kernel.org, linux-fscrypt@vger.kernel.org,
Alim Akhtar <alim.akhtar@samsung.com>,
Andy Gross <agross@kernel.org>, Avri Altman <avri.altman@wdc.com>,
Barani Muthukumaran <bmuthuku@qti.qualcomm.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Can Guo <cang@codeaurora.org>,
Elliot Berman <eberman@codeaurora.org>,
John Stultz <john.stultz@linaro.org>,
Satya Tangirala <satyat@google.com>
Subject: Re: [RFC PATCH v4 1/4] firmware: qcom_scm: Add support for programming inline crypto keys
Date: Thu, 7 May 2020 08:39:08 -0400 [thread overview]
Message-ID: <1dc13593-9ee9-aa61-978e-1e6a1d9cec0f@linaro.org> (raw)
In-Reply-To: <20200501045111.665881-2-ebiggers@kernel.org>
On 5/1/20 12:51 AM, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> Add support for the Inline Crypto Engine (ICE) key programming interface
> that's needed for the ufs-qcom driver to use inline encryption on
> Snapdragon SoCs. This interface consists of two SCM calls: one to
> program a key into a keyslot, and one to invalidate a keyslot.
>
> Although the UFS specification defines a standard way to do this, on
> these SoCs the Linux kernel isn't permitted to access the needed crypto
> configuration registers directly; these SCM calls must be used instead.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
> drivers/firmware/qcom_scm.c | 101 ++++++++++++++++++++++++++++++++++++
> drivers/firmware/qcom_scm.h | 4 ++
> include/linux/qcom_scm.h | 19 +++++++
> 3 files changed, 124 insertions(+)
>
> diff --git a/drivers/firmware/qcom_scm.c b/drivers/firmware/qcom_scm.c
> index 059bb0fbae9e5b..646f9613393612 100644
> --- a/drivers/firmware/qcom_scm.c
> +++ b/drivers/firmware/qcom_scm.c
> @@ -926,6 +926,107 @@ int qcom_scm_ocmem_unlock(enum qcom_scm_ocmem_client id, u32 offset, u32 size)
> }
> EXPORT_SYMBOL(qcom_scm_ocmem_unlock);
>
> +/**
> + * qcom_scm_ice_available() - Is the ICE key programming interface available?
> + *
> + * Return: true iff the SCM calls wrapped by qcom_scm_ice_invalidate_key() and/s/iff/if
--
Warm Regards
Thara
next prev parent reply other threads:[~2020-05-07 12:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 4:51 [RFC PATCH v4 0/4] Inline crypto support on DragonBoard 845c Eric Biggers
2020-05-01 4:51 ` [RFC PATCH v4 1/4] firmware: qcom_scm: Add support for programming inline crypto keys Eric Biggers
2020-05-07 12:39 ` Thara Gopinath [this message]
2020-06-17 6:48 ` Bjorn Andersson
2020-05-01 4:51 ` [RFC PATCH v4 2/4] arm64: dts: sdm845: add Inline Crypto Engine registers and clock Eric Biggers
2020-05-01 4:51 ` [RFC PATCH v4 3/4] scsi: ufs: add program_key() variant op Eric Biggers
2020-05-01 4:51 ` [RFC PATCH v4 4/4] scsi: ufs-qcom: add Inline Crypto Engine support Eric Biggers
2020-05-07 12:36 ` Thara Gopinath
2020-05-07 18:04 ` Eric Biggers
2020-05-07 18:08 ` Eric Biggers
2020-05-08 20:18 ` Steev Klimaszewski
2020-05-08 20:25 ` Eric Biggers
2020-05-08 20:29 ` Satya Tangirala
2020-06-12 18:04 ` Steev Klimaszewski
2020-06-15 18:58 ` Eric Biggers
2020-06-15 19:07 ` Steev Klimaszewski
2020-05-29 15:54 ` Thara Gopinath
2020-05-29 17:13 ` Eric Biggers
2020-05-29 21:25 ` Thara Gopinath
2020-05-29 21:38 ` Eric Biggers
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=1dc13593-9ee9-aa61-978e-1e6a1d9cec0f@linaro.org \
--to=thara.gopinath@linaro.org \
--cc=agross@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=bjorn.andersson@linaro.org \
--cc=bmuthuku@qti.qualcomm.com \
--cc=cang@codeaurora.org \
--cc=eberman@codeaurora.org \
--cc=ebiggers@kernel.org \
--cc=john.stultz@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--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 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).