From: Saikiran <bjsaikiran@gmail.com>
To: linux-media@vger.kernel.org
Cc: linux-arm-msm@vger.kernel.org, rfoss@kernel.org,
todor.too@gmail.com, bryan.odonoghue@linaro.org, bod@kernel.org,
vladimir.zapolskiy@linaro.org, hansg@kernel.org,
sakari.ailus@linux.intel.com, mchehab@kernel.org,
Saikiran <bjsaikiran@gmail.com>
Subject: [PATCH v2 0/2] Fix OV02C10 camera pipeline lock issues
Date: Sun, 25 Jan 2026 22:47:43 +0530 [thread overview]
Message-ID: <20260125171745.484806-1-bjsaikiran@gmail.com> (raw)
This series fixes critical pipeline lock leaks that permanently lock the
camera on Snapdragon X Elite systems when applications close unexpectedly
or subdevices fail to stop cleanly.
Changes in v2:
- Patch 1: Added Fixes tag and Cc: stable as requested by Bryan O'Donoghue
Fixed code style (moved opening brace)
Simplified commit message
- Patch 2: Added Fixes tag and Cc: stable
Removed unnecessary multi-line comment from code
Removed invalid commit reference from commit message
Note: The brownout prevention patch (originally patch 3/3) is being reworked
based on maintainer feedback to improve power sequencing timings. It will be
submitted separately after testing the suggested approach.
Testing: All patches tested on Lenovo Yoga Slim 7x (Snapdragon X Elite,
ov02c10 camera) with libcamera/qcam, browser WebRTC, and PipeWire.
Saikiran (2):
media: qcom: camss: Fix pipeline lock leak in stop_streaming
media: i2c: ov02c10: Check for errors in disable_streams
drivers/media/i2c/ov02c10.c | 6 +++++-
drivers/media/platform/qcom/camss/camss-video.c | 10 ++++++++--
2 files changed, 13 insertions(+), 3 deletions(-)
--
2.51.0
next reply other threads:[~2026-01-25 17:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-25 17:17 Saikiran [this message]
2026-01-25 17:17 ` [PATCH v2 1/2] media: qcom: camss: Fix pipeline lock leak in stop_streaming Saikiran
2026-01-25 17:17 ` [PATCH v2 2/2] media: i2c: ov02c10: Check for errors in disable_streams Saikiran
2026-01-26 10:13 ` Konrad Dybcio
2026-01-26 10:21 ` Hans de Goede
2026-01-26 6:15 ` [PATCH v2 0/1] media: i2c: ov02c10: Keep power on and use reset for power management Saikiran
2026-01-26 6:15 ` [PATCH v2 1/1] " Saikiran
2026-01-26 10:32 ` Hans de Goede
2026-01-26 10:59 ` Saikiran B
2026-01-26 11:09 ` Bryan O'Donoghue
2026-01-26 11:23 ` Saikiran B
2026-01-26 11:41 ` Bryan O'Donoghue
2026-01-26 11:58 ` Saikiran B
2026-01-26 12:06 ` Bryan O'Donoghue
2026-01-26 12:24 ` Saikiran B
2026-01-26 12:41 ` Bryan O'Donoghue
2026-01-26 12:48 ` Saikiran B
2026-01-26 13:31 ` Hans de Goede
[not found] ` <I-1OPz69QKXF-LDqvufQARvv_3TIYaLyZIETdiGvSj_JSYhnJNeqiLERDUH2R0kclFyo6MqMRsaiZaS3RKmdZA==@protonmail.internalid>
[not found] ` <CAAFDt1ufYyM4_xTy+AZTdXBB0cGNk+nFQHD5+5U7tUMQqZ+o=g@mail.gmail.com>
2026-01-26 15:04 ` Bryan O'Donoghue
2026-01-26 15:40 ` Saikiran B
2026-01-26 16:00 ` Bryan O'Donoghue
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=20260125171745.484806-1-bjsaikiran@gmail.com \
--to=bjsaikiran@gmail.com \
--cc=bod@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=hansg@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rfoss@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=todor.too@gmail.com \
--cc=vladimir.zapolskiy@linaro.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