From: bod@kernel.org
To: bod@kernel.org, linux-media@vger.kernel.org, hans@jjverkuil.nl
Cc: bryan.odonoghue@linaro.org
Subject: [GIT PULL FOR 6.19] Please pull platform-qcom-camss-for-6.19
Date: Thu, 6 Nov 2025 00:08:23 +0000 [thread overview]
Message-ID: <20251106000828.6446-1-bod@kernel.org> (raw)
From: Bryan O'Donoghue <bod@kernel.org>
The following changes since commit 8efac3545ac7b90234863214a4f4e13d86a70b0a:
Merge branch media-committers:next into next (2025-11-05 16:22:03 +0000)
are available in the Git repository at:
https://gitlab.freedesktop.org/linux-media/users/bodonoghue.git tags/platform-qcom-camss-for-6.19
for you to fetch changes up to e672f18d3e6e2e1e53bf37b3be3faca971f2fb67:
media: qcom: camss: Add support for MSM8939 (2025-11-05 16:23:42 +0000)
----------------------------------------------------------------
This CAMSS tag contains:
- Adds support for MSM8939 - Vincent Knecht, André Apitzsch
- Adds support for SM8650 - Vladimir Zapolskiy
- Adds an additional clock as prep work for a new SoC - Hangxiang
- Various fixes and code improvements
Johan, Hangxiang, Krsysztof
----------------------------------------------------------------
Hangxiang Ma (2):
media: qcom: camss: Use a macro to specify the initial buffer count
media: qcom: camss: Enable setting the rate to camnoc_rt_axi clock
Johan Hovold (1):
media: qcom: camss: drop unused module alias
Krzysztof Kozlowski (1):
media: dt-bindings: qcom,x1e80100-camss: Fix typo in CSIPHY supply description
Vincent Knecht (3):
media: dt-bindings: Add qcom,msm8939-camss
media: qcom: camss: vfe: Add VBIF setting support
media: qcom: camss: Add support for MSM8939
Vladimir Zapolskiy (3):
dt-bindings: media: Describe Qualcomm SM8650 CAMSS IP
media: qcom: camss: Add Qualcomm SM8650 CAMSS support
media: qcom: camss: Add CSIPHY 2.2.0 lane configuration for SM8650
.../bindings/media/qcom,msm8939-camss.yaml | 254 +++++++++++
.../bindings/media/qcom,sm8650-camss.yaml | 375 ++++++++++++++++
.../bindings/media/qcom,x1e80100-camss.yaml | 2 +-
drivers/media/platform/qcom/camss/Makefile | 1 +
.../platform/qcom/camss/camss-csiphy-3ph-1-0.c | 102 +++++
drivers/media/platform/qcom/camss/camss-csiphy.c | 1 +
drivers/media/platform/qcom/camss/camss-ispif.c | 8 +-
drivers/media/platform/qcom/camss/camss-vfe-4-1.c | 12 +
drivers/media/platform/qcom/camss/camss-vfe-vbif.c | 31 ++
drivers/media/platform/qcom/camss/camss-vfe-vbif.h | 19 +
drivers/media/platform/qcom/camss/camss-vfe.c | 17 +-
drivers/media/platform/qcom/camss/camss-vfe.h | 3 +
drivers/media/platform/qcom/camss/camss.c | 483 ++++++++++++++++++++-
drivers/media/platform/qcom/camss/camss.h | 3 +
14 files changed, 1305 insertions(+), 6 deletions(-)
create mode 100644 Documentation/devicetree/bindings/media/qcom,msm8939-camss.yaml
create mode 100644 Documentation/devicetree/bindings/media/qcom,sm8650-camss.yaml
create mode 100644 drivers/media/platform/qcom/camss/camss-vfe-vbif.c
create mode 100644 drivers/media/platform/qcom/camss/camss-vfe-vbif.h
reply other threads:[~2025-11-06 0:08 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=20251106000828.6446-1-bod@kernel.org \
--to=bod@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=hans@jjverkuil.nl \
--cc=linux-media@vger.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).