From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Eric Millbrandt <emillbrandt@dekaresearch.com>
Cc: Liam Girdwood <lrg@slimlogic.co.uk>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: [RFC] Input: wm97xx-core - Remove save state from wm97xx_read_aux_adc()
Date: Wed, 1 Sep 2010 19:46:50 +0100 [thread overview]
Message-ID: <20100901184650.GH22444@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <0A40042D85E7C84DB443060EC44B3FD3254AA09E7F@dekaexchange07.deka.local>
On Wed, Sep 01, 2010 at 02:46:59PM -0400, Eric Millbrandt wrote:
> On Wed, 1 Sep 2010 at 13:19:25 Mark Brown wrote:
[Reflowed your mail into 80 columns for legibility - you might want to
look at your MUA configuration]
> > You need to explain how this interacts with both polling and continuous
> > touchscreen modes - saying that it seems unneeded feels a little fuzzy.
> > Note that this will also clear the current digitiser configuration before
> > it starts the AUXADC so it's not a simple save of the values.
> You are right; the current digitizer settings do need to be cleared.
> I was testing in the polling touchscreen mode and overlooked that fact.
> But do we want to restore the POLL bit if it happened to be set?
> Continuous mode does not need it and it looks like wm9712_poll_*() will
> set the POLL bit again when it needs a touchscreen measurement.
I've got a feeling that at least some machine-specific semi accelerated
drivers make use of this but can't quite remember. If it just causes an
extra sample sometimes I'm inclined to feel it's safer to leave things
as-is.
next prev parent reply other threads:[~2010-09-01 18:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 14:52 [RFC] Input: wm97xx-core - Remove save state from wm97xx_read_aux_adc() Eric Millbrandt
2010-09-01 17:19 ` Mark Brown
2010-09-01 18:46 ` Eric Millbrandt
2010-09-01 18:46 ` Mark Brown [this message]
2010-09-01 19:17 ` Eric Millbrandt
2010-09-02 14:40 ` Mark Brown
2010-09-02 15:32 ` Eric Millbrandt
2010-09-02 16:16 ` Mark Brown
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=20100901184650.GH22444@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=emillbrandt@dekaresearch.com \
--cc=linux-input@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
/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.