From: Michael Hennerich <michael.hennerich@analog.com>
To: Markus Niebel <list-09_linux_input@tqsc.de>
Cc: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"dmitry.torokhov@gmail.com" <dmitry.torokhov@gmail.com>
Subject: Re: Input: ads7846 - sampling logic issues with AD7873
Date: Tue, 29 May 2012 14:25:38 +0200 [thread overview]
Message-ID: <4FC4C042.5060100@analog.com> (raw)
In-Reply-To: <4FC4A93E.9040305@tqsc.de>
On 05/29/2012 12:47 PM, Markus Niebel wrote:
> Hi,
>
> we use the AD7873 controller with internal reference. The current implementation for AD7873 in the ads7846 driver forces the vref to switch off after every sample. So measurements especially in the edge of the screen become unreliable due to the settling time for the internal reference (I guess). Is there a special reason to override the "keep_vref_of" setting of the platform data for the AD7873 in ads7846_setup_spi_msg?
>
> We did already some tests and found out, that leaving vref on makes out system usable with AD7873.
>
> Markus
>
>
Hi Markus,
from top of my head - I don't remember why I forced Vref OFF for the AD7873.
Looking at the datasheet doesn't refresh my memory either.
I know there are some minor differences with respect to the PENIRQ
behavior in one
PD bits combination - but that doesn't explain why we force it off.
From a power savings aspect Vref should be turned off, but if
settling time worsens your results, then leaving Vref ON is the way to go.
Feel free to submit a patch.
--
Greetings,
Michael
--
Analog Devices GmbH Wilhelm-Wagenfeld-Str. 6 80807 Muenchen
Sitz der Gesellschaft: Muenchen; Registergericht: Muenchen HRB 40368;
Geschaeftsfuehrer:Dr.Carsten Suckrow, Thomas Wessel, William A. Martin,
Margaret Seif
next prev parent reply other threads:[~2012-05-29 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 10:47 Input: ads7846 - sampling logic issues with AD7873 Markus Niebel
2012-05-29 12:25 ` Michael Hennerich [this message]
2012-05-30 17:53 ` Markus Niebel
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=4FC4C042.5060100@analog.com \
--to=michael.hennerich@analog.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=list-09_linux_input@tqsc.de \
/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.