From: Bjorn Andersson <andersson@kernel.org>
To: arm@kernel.org, soc@kernel.org
Cc: linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Andy Gross <agross@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Olof Johansson <olof@lixom.net>,
Kevin Hilman <khilman@baylibre.com>,
Abel Vesa <abel.vesa@linaro.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Clark <robdclark@chromium.org>,
Tushar Nimkar <quic_tnimkar@quicinc.com>
Subject: [GIT PULL] A few more Qualcomm driver updates for v6.4
Date: Thu, 13 Apr 2023 19:43:02 -0700 [thread overview]
Message-ID: <20230414024302.2411985-1-andersson@kernel.org> (raw)
The following changes since commit c78ad8597ed961e822bf86ce7f1916dbfba255ef:
dt-bindings: firmware: document Qualcomm SC8180X SCM (2023-04-04 20:23:56 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git qcom-drivers-for-6.4-2
for you to fetch changes up to f6ff91a47ac57cb1118d94020302617b6b22c0d1:
dt-bindings: crypto: Add Qualcomm Inline Crypto Engine (2023-04-07 12:21:27 -0700)
----------------------------------------------------------------
A few more Qualcomm driver updates for v6.4
This introduces a new binding and a dedicated driver for the Qualcomm
Inline-Crypto-Engine (ICE), in order to support a single shared instance
between SDHCI and UFS, found in recent platforms.
RSC version check is updated to support minor revisions of v3 of the ip
block, the SMD-RPM interface is transitioned to GFP_ATOMIC to avoid the
shrinker to kick in underneath the GPU and QCM2290 support is added to
the SCM binding.
----------------------------------------------------------------
Abel Vesa (2):
soc: qcom: Make the Qualcomm UFS/SDCC ICE a dedicated driver
dt-bindings: crypto: Add Qualcomm Inline Crypto Engine
Bjorn Andersson (1):
Merge tag '20230407105029.2274111-4-abel.vesa@linaro.org' into drivers-for-6.4
Konrad Dybcio (1):
dt-bindings: firmware: document Qualcomm QCM2290 SCM
Rob Clark (1):
soc: qcom: smd-rpm: Use GFP_ATOMIC in write path
Tushar Nimkar (1):
soc: qcom: rpmh-rsc: Support RSC v3 minor versions
.../bindings/crypto/qcom,inline-crypto-engine.yaml | 42 +++
.../devicetree/bindings/firmware/qcom,scm.yaml | 3 +
drivers/soc/qcom/Kconfig | 4 +
drivers/soc/qcom/Makefile | 1 +
drivers/soc/qcom/ice.c | 366 +++++++++++++++++++++
drivers/soc/qcom/rpmh-rsc.c | 2 +-
drivers/soc/qcom/smd-rpm.c | 2 +-
include/soc/qcom/ice.h | 37 +++
8 files changed, 455 insertions(+), 2 deletions(-)
create mode 100644 Documentation/devicetree/bindings/crypto/qcom,inline-crypto-engine.yaml
create mode 100644 drivers/soc/qcom/ice.c
create mode 100644 include/soc/qcom/ice.h
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2023-04-14 2:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230414024302.2411985-1-andersson@kernel.org \
--to=andersson@kernel.org \
--cc=abel.vesa@linaro.org \
--cc=agross@kernel.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=khilman@baylibre.com \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=olof@lixom.net \
--cc=quic_tnimkar@quicinc.com \
--cc=robdclark@chromium.org \
--cc=soc@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 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).