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,
Arnd Bergmann <arnd@arndb.de>,
Viken Dadhaniya <viken.dadhaniya@oss.qualcomm.com>,
Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>
Subject: [GIT PULL] More Qualcomm device driver updates for v6.18
Date: Sat, 20 Sep 2025 21:02:24 -0500 [thread overview]
Message-ID: <20250921020225.595403-1-andersson@kernel.org> (raw)
The following changes since commit 3cc9a8cadaf66e1a53e5fee48f8bcdb0a3fd5075:
firmware: qcom: tzmem: disable sc7180 platform (2025-09-11 16:38:33 -0500)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git tags/qcom-drivers-for-6.18-2
for you to fetch changes up to 3f1707306b79cafc5a11350befd5a4081b807760:
serial: qcom-geni: Load UART qup Firmware from linux side (2025-09-17 13:51:08 -0500)
----------------------------------------------------------------
More Qualcomm device driver updates for v6.18
Introduce support for loading firmware into the QUP serial engines from
Linux, which allows deferring selection of which protocol (uart, i2c,
spi, etc) a given SE should have until the OS loads.
Also introduce the "object invoke" interface in the SCM driver, to
provide interface to the Qualcomm TEE driver.
----------------------------------------------------------------
Amirreza Zarrabi (2):
firmware: qcom: tzmem: export shm_bridge create/delete
firmware: qcom: scm: add support for object invocation
Bjorn Andersson (1):
Merge branch '20250911-qcom-tee-using-tee-ss-without-mem-obj-v12-2-17f07a942b8d@oss.qualcomm.com' into drivers-for-6.18
Viken Dadhaniya (6):
dt-bindings: qcom: se-common: Add QUP Peripheral-specific properties for I2C, SPI, and SERIAL bus
soc: qcom: geni-se: Cleanup register defines and update copyright
soc: qcom: geni-se: Add support to load QUP SE Firmware via Linux subsystem
i2c: qcom-geni: Load i2c qup Firmware from linux side
spi: geni-qcom: Load spi qup Firmware from linux side
serial: qcom-geni: Load UART qup Firmware from linux side
.../bindings/i2c/qcom,i2c-geni-qcom.yaml | 1 +
.../bindings/serial/qcom,serial-geni-qcom.yaml | 1 +
.../bindings/soc/qcom/qcom,se-common-props.yaml | 26 ++
.../bindings/spi/qcom,spi-geni-qcom.yaml | 1 +
drivers/firmware/qcom/qcom_scm.c | 119 +++++
drivers/firmware/qcom/qcom_scm.h | 7 +
drivers/firmware/qcom/qcom_tzmem.c | 63 ++-
drivers/i2c/busses/i2c-qcom-geni.c | 8 +-
drivers/soc/qcom/qcom-geni-se.c | 506 ++++++++++++++++++++-
drivers/spi/spi-geni-qcom.c | 6 +
drivers/tty/serial/qcom_geni_serial.c | 8 +-
include/linux/firmware/qcom/qcom_scm.h | 6 +
include/linux/firmware/qcom/qcom_tzmem.h | 15 +
include/linux/soc/qcom/geni-se.h | 4 +
14 files changed, 739 insertions(+), 32 deletions(-)
create mode 100644 Documentation/devicetree/bindings/soc/qcom/qcom,se-common-props.yaml
next reply other threads:[~2025-09-21 2:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-21 2:02 Bjorn Andersson [this message]
2025-09-23 21:21 ` [GIT PULL] More Qualcomm device driver updates for v6.18 patchwork-bot+linux-soc
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=20250921020225.595403-1-andersson@kernel.org \
--to=andersson@kernel.org \
--cc=amirreza.zarrabi@oss.qualcomm.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=soc@kernel.org \
--cc=viken.dadhaniya@oss.qualcomm.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.