From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Iiro Valkonen <iiro.valkonen@atmel.com>
Cc: linux-input@vger.kernel.org, Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: RFC: User-space interface to read/write touchscreen controller registers (atmel_mxt_ts.c)
Date: Wed, 27 Jul 2011 13:49:20 +0100 [thread overview]
Message-ID: <20110727124920.GF300@sirena.org.uk> (raw)
In-Reply-To: <4E2968ED.4030708@atmel.com>
On Fri, Jul 22, 2011 at 03:11:25PM +0300, Iiro Valkonen wrote:
Please fix your mail client to word wrap within paragraphs. I've
reformatted your text for legibility.
> we have a need to access the configuration registers/register blocks
> of the touchscreen controller from the user space. There are several
> reasons for this, and while some of them are related to debugging,
> some can be valuable in normal use cases. For example, a configuration
> parameter might need to be semi-permanently changed to improve
> performance, or some parameter could even be updated for different
> usage modes of the device. This interface would make it very easy.
> Currently, a change in the board file and kernel recompile is needed
> to change the settings.
For diagnostic access the regmap API was merged during this merge
window, it provides debugfs access to the register map. That doesn't
help with the coefficient data but it should be enough for debugging.
prev parent reply other threads:[~2011-07-27 12:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 12:11 RFC: User-space interface to read/write touchscreen controller registers (atmel_mxt_ts.c) Iiro Valkonen
2011-07-27 12:49 ` Mark Brown [this message]
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=20110727124920.GF300@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=dmitry.torokhov@gmail.com \
--cc=iiro.valkonen@atmel.com \
--cc=linux-input@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).