From: Saikiran <bjsaikiran@gmail.com>
To: loic.poulain@oss.qualcomm.com
Cc: rfoss@kernel.org, andi.shyti@kernel.org,
sakari.ailus@linux.intel.com, hansg@kernel.org, bod@kernel.org,
mchehab@kernel.org, vladimir.zapolskiy@linaro.org,
jishnu.prakash@oss.qualcomm.com, birk.skyum@pm.me,
linux-i2c@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: [PATCH v1 0/2] i2c: qcom-cci, media: ov02c10: Fix camera power cycling
Date: Thu, 22 Oct 2026 12:44:16 +0530 [thread overview]
Message-ID: <20261022071418.26895-1-bjsaikiran@gmail.com> (raw)
The OV02C10 camera on the Lenovo Yoga Slim 7x can fail to restart after
streaming stops. The CCI runtime PM callbacks gate the controller clocks
but leave the bus pins in their default state while suspended. The X1E80100
device tree already defines a CCI sleep state with pull-downs for the bus
pins, so select that state before suspending the controller and restore the
default state on resume.
The OV02C10 driver also enables the sensor supplies before MCLK and disables
MCLK before the supplies, with the required reset and startup timing. This
series fixes the power transitions without adding a regulator-off delay or
runtime autosuspend workaround.
Tested on Lenovo Yoga Slim 7x (Snapdragon X Elite): 20 consecutive Kamoso
camera open/close cycles. The sensor entered runtime-active on each open and
returned to runtime-suspended on each close. Both modified driver objects
build cleanly against the running kernel configuration.
Saikiran (2):
i2c: qcom-cci: Select pinctrl states during runtime PM
media: ov02c10: Fix sensor power sequencing
drivers/i2c/busses/i2c-qcom-cci.c | 14 +++++++++++++-
drivers/media/i2c/ov02c10.c | 20 +++++++++++---------
2 files changed, 24 insertions(+), 10 deletions(-)
--
2.56.0
next reply other threads:[~2026-10-22 7:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 7:14 Saikiran [this message]
2026-10-22 7:14 ` [PATCH v1 1/2] i2c: qcom-cci: Select pinctrl states during runtime PM Saikiran
2026-10-22 7:14 ` [PATCH v1 2/2] media: ov02c10: Fix sensor power sequencing Saikiran
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=20261022071418.26895-1-bjsaikiran@gmail.com \
--to=bjsaikiran@gmail.com \
--cc=andi.shyti@kernel.org \
--cc=birk.skyum@pm.me \
--cc=bod@kernel.org \
--cc=hansg@kernel.org \
--cc=jishnu.prakash@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=mchehab@kernel.org \
--cc=rfoss@kernel.org \
--cc=sakari.ailus@linux.intel.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
all inboxes | Powered by JetHome®