From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Saikiran <bjsaikiran@gmail.com>, 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,
stable@vger.kernel.org
Subject: Re: [PATCH v2 2/2] media: i2c: ov02c10: Check for errors in disable_streams
Date: Mon, 26 Jan 2026 11:13:23 +0100 [thread overview]
Message-ID: <95b29cb9-540c-42ac-bcf9-21327322d7ec@oss.qualcomm.com> (raw)
In-Reply-To: <20260125171745.484806-3-bjsaikiran@gmail.com>
On 1/25/26 6:17 PM, Saikiran wrote:
> The ov02c10_disable_streams() function ignores the return value from
> cci_write() when stopping the sensor. If the I2C write fails (e.g.,
> due to CCI timeout, power management race, or device removal), the
^ CCI -> I2C
CCI is a name for a small camera-subsystem-adjacent I2C host on
Qualcomm hardware specifically
Konrad
next prev parent reply other threads:[~2026-01-26 10:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-25 17:17 [PATCH v2 0/2] Fix OV02C10 camera pipeline lock issues Saikiran
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 [this message]
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=95b29cb9-540c-42ac-bcf9-21327322d7ec@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=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=stable@vger.kernel.org \
--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