From: Simon Budig <simon.budig@kernelconcepts.de>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: Olivier Sobrie <olivier@sobrie.be>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org,
Jan Paesmans <jan.paesmans@gmail.com>,
Anatolij Gustshin <agust@denx.de>, Ilya Yanok <yanok@emcraft.com>
Subject: Re: [PATCH] input: edt-ft5x06 - Touchscreen driver for FT5x06 based EDT displays
Date: Wed, 20 Jun 2012 23:27:00 +0200 [thread overview]
Message-ID: <4FE24024.9010807@kernelconcepts.de> (raw)
In-Reply-To: <20120620184015.GA5390@polaris.bitmath.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Henrik
On 06/20/2012 08:40 PM, Henrik Rydberg wrote:
>> +/* + * Part of this code is inspired from a first version of a
>> driver for + * this chip sent by Simon Budig to the linux-input
>> mailing list + */
>
> Replacing the above with the standard GPL header with both of your
> names ought to resolve any eventual issues, no?
Not sure. Olivier looked at an ancient version of my code, missing
multiple review spins and tests I did in the meantime with Dmitry and
Anatolij.
I obviously would prefer to see my driver in the kernel. Of course I
am open to improvement suggestions, but I am not really enthusiastic
about reviewing a driver that basically ditches most of my work.
>> +ft5x06_setting(threshold, W_REGISTER_THRESHOLD, 20, 80);
>> +ft5x06_setting(gain, W_REGISTER_GAIN, 0, 31);
>> +ft5x06_setting(offset, W_REGISTER_OFFSET, 0, 31);
>
> Question: will the driver work without fiddling with these
> settings? If so, are they really necessary? Maybe some part could
> be moved to debugfs instead?
Well, these are there in my driver as well (plus the "report rate"
setting of the sensor).
There are some parameters (gain/threshold/offset) which need tweaking
depending on the panel glass thickness and other device-specific
things. At least in the development phase it is necessary to tweak
with these to figure out good settings.
Dunno if sysfs is the best place for this, but I suspect that this is
a parameter that needs to be available at runtime as well, moving it
e.g. to platform data might not cut it.
Anyway. I have reviewed the changes Dmitry suggested and will test
them on real hardware tomorrow.
Bye,
Simon
- --
Simon Budig kernel concepts GmbH
simon.budig@kernelconcepts.de Sieghuetter Hauptweg 48
+49-271-771091-17 D-57072 Siegen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk/iQCQACgkQO2O/RXesiHCmyACeN4cFK2KEkPT83TqrO7f00YBZ
Vl4AoIBuoHqw6AZzoi24dGT0uepi+7Vx
=D8UO
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-06-20 21:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 11:01 [PATCH] input: edt-ft5x06 - Touchscreen driver for FT5x06 based EDT displays Olivier Sobrie
2012-06-14 12:05 ` Simon Budig
2012-06-14 12:48 ` Olivier Sobrie
2012-06-20 18:40 ` Henrik Rydberg
2012-06-20 21:27 ` Simon Budig [this message]
2012-06-21 8:39 ` Dmitry Torokhov
2012-06-21 9:39 ` Simon Budig
2012-06-21 10:04 ` Dmitry Torokhov
2012-06-21 14:53 ` Simon Budig
2012-06-25 7:23 ` Dmitry Torokhov
2012-06-21 6:35 ` Olivier Sobrie
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=4FE24024.9010807@kernelconcepts.de \
--to=simon.budig@kernelconcepts.de \
--cc=agust@denx.de \
--cc=dmitry.torokhov@gmail.com \
--cc=jan.paesmans@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=olivier@sobrie.be \
--cc=rydberg@euromail.se \
--cc=yanok@emcraft.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.