RE: [PATCH v5] Fix the resolution issue in ChromeOS

[Hn Chen]

Hi, Frans,

It can only be delay for the firmware implementation now.

Hn.chen

-----Original Message-----
From: Frans Klaver [mailto:fransklaver@xxxxxxxxx] 
Sent: Friday, June 12, 2015 6:02 PM
To: Hn Chen
Cc: linux-input@xxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; Dmitry Torokhov
Subject: Re: [PATCH v5] Fix the resolution issue in ChromeOS

On Wed, Jun 10, 2015 at 4:51 PM, Hn Chen <hn.chen@xxxxxxxxxxxxxxx> wrote:
> Hi, Frans,
>
>> Alright, I was just wondering. Seems like a waste to be waiting for something that's already finished ;-).
>> There's of course a risk that times may fluctuate between firmware versions. Did you take that into account in the code?
>> Or is there a hard maximum time for these operations defined for the firmware?
> Thanks for your reminding.
> After I check with the firmware guy, I will change the value of delay.
> What we do here is to read the data from flash and calculate their 
> checksum and will cost about 6ms for 1024 bytes. So there is a delay for 10 ms per 1024 bytes.
> But in some situation, the controller will change it's running 
> frequency(like do noise immunity), 10ms could be too margin.

Any chance this sort of thing could be detected?
N‹§²æ¸›yú²X¬¶ÇvØ–)Þ{.nlj·¥Š{±‘êX§¶›¡Ü}©ž²ÆzÚj:+v‰¨¾«‘êZ+€Êzf£¢·hšˆ§~†­†Ûÿû®w¥¢¸?™¨è&¢)ßf”ùy§m…á«a¶Úÿ0¶ìå