From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Quentin Schulz <quentin.schulz@cherry.de>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Quentin Schulz <quentin.schulz@theobroma-systems.com>,
Jacopo Mondi <jacopo@jmondi.org>
Cc: Johan Hovold <johan@kernel.org>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, dave.stevenson@raspberrypi.com
Subject: Re: [PATCH 2/2] media: ov5675: Elongate reset to first transaction minimum gap
Date: Thu, 11 Jul 2024 13:25:27 +0100 [thread overview]
Message-ID: <b30e10b3-6916-45a3-81c8-182d81d4a34e@linaro.org> (raw)
In-Reply-To: <3646cd1f-09f1-4e80-8d55-a9ac25cbf81d@cherry.de>
On 11/07/2024 13:22, Quentin Schulz wrote:
> Hi Bryan,
>
> On 7/11/24 2:07 PM, Bryan O'Donoghue wrote:
>> On 11/07/2024 12:41, Quentin Schulz wrote:
>> Worst case XVCLK period is 1.365 milliseconds.
>>
>> If your theory on the GPIO is correct, its still difficult to see how
>> @ 6MHz - which we don't yet support and probably never will, that 1.5
>> milliseconds would be insufficient.
>>
>> So - I'm happy enough to throw out the first patch and give a range of
>> 1.5 to 1.6 milliseconds instead.
>>
>
> Works for me.
Great.
Just for record, I'll update power_off() too to match the logic we are
applying @ power_on since we've decided the calculation based on XVCLK
is overkill.
---
bod
prev parent reply other threads:[~2024-07-11 12:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 10:20 [PATCH 0/2] media: ov5675: Fixup ov5675 reset failures Bryan O'Donoghue
2024-07-11 10:20 ` [PATCH 1/2] media: ov5675: Derive delay cycles from the clock rate reported Bryan O'Donoghue
2024-07-11 10:32 ` Quentin Schulz
2024-07-11 10:20 ` [PATCH 2/2] media: ov5675: Elongate reset to first transaction minimum gap Bryan O'Donoghue
2024-07-11 10:40 ` Quentin Schulz
2024-07-11 11:17 ` Dave Stevenson
2024-07-11 11:24 ` Bryan O'Donoghue
2024-07-11 11:22 ` Bryan O'Donoghue
2024-07-11 11:28 ` Bryan O'Donoghue
2024-07-11 11:41 ` Quentin Schulz
2024-07-11 12:07 ` Bryan O'Donoghue
2024-07-11 12:22 ` Quentin Schulz
2024-07-11 12:25 ` Bryan O'Donoghue [this message]
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=b30e10b3-6916-45a3-81c8-182d81d4a34e@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=dave.stevenson@raspberrypi.com \
--cc=jacopo@jmondi.org \
--cc=johan@kernel.org \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=quentin.schulz@cherry.de \
--cc=quentin.schulz@theobroma-systems.com \
--cc=sakari.ailus@linux.intel.com \
--cc=stable@vger.kernel.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®