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.20] Please pull platform-qcom-camss-6.20
Date: Tue, 13 Jan 2026 01:22:15 +0000 [thread overview]
Message-ID: <20260113012230.5907-1-bod@kernel.org> (raw)
From: Bryan O'Donoghue <bod@kernel.org>
The following changes since commit 3aa9296a23ec41a8424e9a2346eea59fb6cb7d8c:
media: i2c: add os05b10 image sensor driver (2026-01-12 08:43:11 +0100)
are available in the Git repository at:
https://gitlab.freedesktop.org/linux-media/users/bodonoghue.git tags/platform-qcom-camss-6.20
for you to fetch changes up to 17bce0a2ae9674b707ed6ed2171f1b59cab8f05b:
media: qcom: camss: add support for SM6150 camss (2026-01-13 01:10:35 +0000)
----------------------------------------------------------------
This tag includes
- Support for a new SoC sm6150
- Support for setting CSIPHY regulator loads
- fwnode changes to simplify remote-endpoint parsing
- A nice bugcatch fixing inappropriate array indexing
in an ISR
- Two further minor fixes for clock-enable and an unused variable
- A final yaml fix tightening up PHY supply descriptions
----------------------------------------------------------------
Alper Ak (1):
media: qcom: camss: vfe: Fix out-of-bounds access in vfe_isr_reg_update()
David Heidelberg (1):
dt-bindings: media: Correct camss supply description
Hangxiang Ma (1):
media: camss: csiphy: Make CSIPHY status macro cross-platform
Loic Poulain (1):
media: qcom: camss: csid-340: Fix unused variables
Vikram Sharma (1):
dt-bindings: media: qcom,qcs8300-camss: Add missing power supplies
Vladimir Zapolskiy (3):
media: qcom: camss: Do not enable cpas fast ahb clock for SM8550 VFE lite
media: qcom: camss: change internals of endpoint parsing to fwnode handling
media: qcom: camss: use a handy v4l2_async_nf_add_fwnode_remote() function
Wenmeng Liu (3):
media: qcom: camss: Add support for regulator init_load_uA in CSIPHY
dt-bindings: media: Add qcom,sm6150-camss
media: qcom: camss: add support for SM6150 camss
.../bindings/media/qcom,qcs8300-camss.yaml | 13 +
.../bindings/media/qcom,sa8775p-camss.yaml | 4 +-
.../bindings/media/qcom,sc7280-camss.yaml | 4 +-
.../bindings/media/qcom,sc8280xp-camss.yaml | 4 +-
.../bindings/media/qcom,sdm670-camss.yaml | 4 +-
.../bindings/media/qcom,sdm845-camss.yaml | 4 +-
.../bindings/media/qcom,sm6150-camss.yaml | 439 +++++++++++++++
.../bindings/media/qcom,sm8250-camss.yaml | 4 +-
.../bindings/media/qcom,sm8550-camss.yaml | 4 +-
.../bindings/media/qcom,x1e80100-camss.yaml | 4 +-
drivers/media/platform/qcom/camss/camss-csid-340.c | 10 +-
drivers/media/platform/qcom/camss/camss-csid.c | 18 +-
.../platform/qcom/camss/camss-csiphy-3ph-1-0.c | 21 +-
drivers/media/platform/qcom/camss/camss-csiphy.c | 19 +-
drivers/media/platform/qcom/camss/camss-csiphy.h | 1 +
drivers/media/platform/qcom/camss/camss-vfe-480.c | 6 +-
drivers/media/platform/qcom/camss/camss-vfe.c | 2 +
drivers/media/platform/qcom/camss/camss.c | 586 +++++++++++++++++----
drivers/media/platform/qcom/camss/camss.h | 3 +-
19 files changed, 980 insertions(+), 170 deletions(-)
create mode 100644 Documentation/devicetree/bindings/media/qcom,sm6150-camss.yaml
reply other threads:[~2026-01-13 1:22 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=20260113012230.5907-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 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.