From: Iiro Valkonen <iiro.valkonen@atmel.com>
To: linux-input@vger.kernel.org, Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: RFC: User-space interface to read/write touchscreen controller registers (atmel_mxt_ts.c)
Date: Fri, 22 Jul 2011 15:11:25 +0300 [thread overview]
Message-ID: <4E2968ED.4030708@atmel.com> (raw)
Hello,
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.
My question is, what kind of approach would be recommended, and what would be acceptable to include in the mainline version? Currently there exists a patch which adds a character device and few IOCTLs (very similar to maXTouch driver here: http://gitorious.org/maxtouch), but my understanding is that is not the best way to do this. Would a sysfs-based system be better suited? Are there any good examples in the mainline drivers how something like this should be implemented?
Best Regards,
--
Iiro Valkonen
next reply other threads:[~2011-07-22 12:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 12:11 Iiro Valkonen [this message]
2011-07-27 12:49 ` RFC: User-space interface to read/write touchscreen controller registers (atmel_mxt_ts.c) 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=4E2968ED.4030708@atmel.com \
--to=iiro.valkonen@atmel.com \
--cc=dmitry.torokhov@gmail.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).