From: Frans Klaver <fransklaver@gmail.com>
To: Hn Chen <hn.chen@weidahitech.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
dmitry.torokhov@gmail.com
Subject: Re: [PATCH v5] Fix the resolution issue in ChromeOS
Date: Mon, 1 Jun 2015 20:18:29 +0200 [thread overview]
Message-ID: <20150601181829.GB4469@bugger.home> (raw)
In-Reply-To: <1A63A1423E772B419A9D2E882CBCF6C401F3DB61@mail>
On Tue, Jun 02, 2015 at 12:39:13AM +0800, Hn Chen wrote:
> Hi, Klaver,
>
> Sorry for replying late and thanks for your opinion !
>
> About the patch descrition, I will follow your suggestion and
Ok. More on this is in Documentation/SubmittingPatches.
> maybe add more commemts between codes to be easy to read.
Only where really necessary. If you do, explain _why_ you do stuff,
rather than how. The how is already in the code. If how isn't clear
enough, clear up the code instead.
> >Are these (and other) delay times based on datasheet values?
> The time consuming is about the computing power of WDT87xx's controller.
> The value is from the algorithm/firmware engineer of wdt87xx.
> They think it is reasonable value to wait the controller to finish the computing.
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?
> For the rest parts, I'll just follow your opinion to modify them.
>
> Best Regards,
> hn.chen
>
Thanks,
Frans
next prev parent reply other threads:[~2015-06-01 18:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 4:27 [PATCH v5] Fix the resolution issue in ChromeOS HungNien Chen
2015-05-29 6:56 ` Frans Klaver
[not found] ` <1A63A1423E772B419A9D2E882CBCF6C401F3DB61@mail>
2015-06-01 18:18 ` Frans Klaver [this message]
2015-06-10 14:51 ` Hn Chen
2015-06-12 10:02 ` Frans Klaver
2015-06-13 7:04 ` Hn Chen
2015-06-08 5:56 ` Dmitry Torokhov
2015-06-10 14:41 ` Hn Chen
2015-06-12 0:41 ` Dmitry Torokhov
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=20150601181829.GB4469@bugger.home \
--to=fransklaver@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hn.chen@weidahitech.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).