linux-kernel - Re: [PATCH 2/2] media: ov5675: Elongate reset to first transaction minimum gap

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <b30e10b3-6916-45a3-81c8-182d81d4a34e@linaro.org>
Date: Thu, 11 Jul 2024 13:25:27 +0100
From: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
To: Quentin Schulz <quentin.schulz@...rry.de>,
 Sakari Ailus <sakari.ailus@...ux.intel.com>,
 Mauro Carvalho Chehab <mchehab@...nel.org>,
 Quentin Schulz <quentin.schulz@...obroma-systems.com>,
 Jacopo Mondi <jacopo@...ndi.org>
Cc: Johan Hovold <johan@...nel.org>,
 Kieran Bingham <kieran.bingham@...asonboard.com>,
 linux-media@...r.kernel.org, linux-kernel@...r.kernel.org,
 stable@...r.kernel.org, dave.stevenson@...pberrypi.com
Subject: Re: [PATCH 2/2] media: ov5675: Elongate reset to first transaction
 minimum gap

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