From: Hans de Goede <hansg@kernel.org>
To: Saikiran B <bjsaikiran@gmail.com>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: Bryan O'Donoghue <bod@kernel.org>,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
rfoss@kernel.org, todor.too@gmail.com,
vladimir.zapolskiy@linaro.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 14:31:13 +0100 [thread overview]
Message-ID: <2084a247-053b-41c0-84ef-c56af640aa74@kernel.org> (raw)
In-Reply-To: <CAAFDt1tgFf5MQcHm3s5DJEDHDtbTfj56_0-=fTz0ekDjSqY3CA@mail.gmail.com>
Hi,
On 26-Jan-26 13:48, Saikiran B wrote:
> I used a 2ms delay for the initial reset assertion.
I think that what Bryan means is you need a 5ms delay between
asserting reset/xshutdown and enabling the regulators to make
sure that the sensor sees the reset signal high before
the regulators are enabled.
Regards,
Hans
> On Mon, Jan 26, 2026 at 6:11 PM Bryan O'Donoghue
> <bryan.odonoghue@linaro.org> wrote:
>>
>> On 26/01/2026 12:24, Saikiran B wrote:
>>> Yes, I implemented your suggested sequence in power_on():
>>>
>>> Assert XSHUTDOWN (Reset GPIO = 1)
>>
>> +5 milliseconds
>>
>>> Enable Regulators
>>> Enable Clock
>>> Wait 2ms+
>>> Release XSHUTDOWN (Reset GPIO = 0)
>>>
>>> Even with this sequence, the brownout prevents detection if the
>>> off-time was ~2.3s (I got this 2.3s number by conducting extensive
>>> stress tests on the platform starting from 50ms to 3s. At 2.3s the
>>> success rate was 100%. Anything below 2.3s, the sensor entered a
>>> brownout state atleast once.)
>>>
>>> Thanks & Regards,
>>> Saikiran
>>
>> ?
>>
>> ---
>> bod
next prev parent reply other threads:[~2026-01-26 13:31 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
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 [this message]
[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=2084a247-053b-41c0-84ef-c56af640aa74@kernel.org \
--to=hansg@kernel.org \
--cc=bjsaikiran@gmail.com \
--cc=bod@kernel.org \
--cc=bryan.odonoghue@linaro.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