From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Saikiran B <bjsaikiran@gmail.com>
Cc: linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
bod@kernel.org, rfoss@kernel.org, todor.too@gmail.com,
vladimir.zapolskiy@linaro.org, hansg@kernel.org,
sakari.ailus@linux.intel.com, mchehab@kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2 1/1] media: i2c: ov02c10: Keep power on and use reset for power management
Date: Mon, 26 Jan 2026 11:41:25 +0000 [thread overview]
Message-ID: <b699fcf5-5cb0-41eb-b9de-e5c6e98aefaa@linaro.org> (raw)
In-Reply-To: <CAAFDt1spRkj7kySCa8P=jehQHbYVT2j+nxLira1vwYkiCJ7LDw@mail.gmail.com>
On 26/01/2026 11:23, Saikiran B wrote:
> "Where do you get this conclusion from ? Are you inferring it from
> what you see on the platform or can you point to some known
> data-source for this ?"
>
> This is determined on the Lenovo Yoga Slim 7x (X1E80100). I tested
> extensively and found that if I attempt to power-on the sensor less
> than ~2.3 seconds after power-off, it fails to identify or times out
> on I2C (brownout behavior). If we wait >2.3s, it works reliably 100%
> of the time.
I don't think we've established the regulator is at fault. That's the
feedback I'm giving you here.
I think it is far, far, far more likely the power-on sequence of the
sensor needs tweaking.
>
> "2 seconds to discharge ? These regulators are PM8010 anyway - so
> you're saying the PMIC takes two seconds to discharge ?"
>
> Yes. I checked the regulator driver
> (drivers/regulator/qcom-rpmh-regulator.c) and found that unlike other
> Qualcomm regulator drivers (e.g., spmi/glink), it currently lacks
> active_discharge / pull-down support. Without active discharge, the
> voltage rails float and decay very slowly via leakage current when the
> load (sensor) is in reset/high-Z.
Right so looking at the power for this part we have:
&cci1_i2c1 {
camera@36 {
compatible = "ovti,ov02c10";
reg = <0x36>;
reset-gpios = <&tlmm 237 GPIO_ACTIVE_LOW>;
pinctrl-names = "default";
pinctrl-0 = <&cam_rgb_default>;
clocks = <&camcc CAM_CC_MCLK4_CLK>;
assigned-clocks = <&camcc CAM_CC_MCLK4_CLK>;
assigned-clock-rates = <19200000>;
orientation = <0>; /* front facing */
avdd-supply = <&vreg_l7b_2p8>;
dvdd-supply = <&vreg_l7b_2p8>;
dovdd-supply = <&vreg_cam_1p8>;
port {
ov02e10_ep: endpoint {
data-lanes = <1 2>;
link-frequencies = /bits/ 64 <400000000>;
remote-endpoint = <&csiphy4_ep>;
};
};
};
};
// qcom standard RPMh -> PMIC LDO regulators
// these are not the droids you are looking for
vreg_l7b_2p8: ldo7 {
regulator-name = "vreg_l7b_2p8";
regulator-min-microvolt = <2800000>;
regulator-max-microvolt = <2800000>;
regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
};
// this OTOH
vreg_cam_1p8: regulator-cam-1p8 {
compatible = "regulator-fixed";
regulator-name = "VREG_CAM_1P8";
regulator-min-microvolt = <1800000>;
regulator-max-microvolt = <1800000>;
gpio = <&tlmm 91 GPIO_ACTIVE_HIGH>;
enable-active-high;
pinctrl-0 = <&cam_ldo_en>;
pinctrl-names = "default";
};
Dell has used - likely reused - part of the x86 design in the qcom
implementation - and toggles 1v8 via a GPIO directly.
If your theory about brown-out is correct then
vreg_cam_1p8: regulator-cam-1p8 {
// add this
off-on-delay-us = <20000>;
};
Then please let us know how she goes.
---
bod
next prev parent reply other threads:[~2026-01-26 11:41 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
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 [this message]
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=b699fcf5-5cb0-41eb-b9de-e5c6e98aefaa@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=bjsaikiran@gmail.com \
--cc=bod@kernel.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