From: Dirk Behme <dirk.behme@de.bosch.com>
To: Nick Dyer <nick.dyer@itdev.co.uk>
Cc: linux-input@vger.kernel.org
Subject: Input: atmel_mxt_ts - don't always download device config?
Date: Mon, 12 Jan 2015 10:50:11 +0100 [thread overview]
Message-ID: <54B398D3.7010803@de.bosch.com> (raw)
Hi Nick,
being new to the atmel_mxt_ts and starting to work with it, we wonder if
it's really necessary to download the device config [1] at each driver
start up?
I've been told that technically each device config download does mean
the configuration data is flashed to the device. I.e. it's stored
persistently, even at power loss.
This would mean that it would be sufficient to check for the device
config already existing/flashed to the device. And only doing the
download in case this isn't done already.
Is this understanding correct? What do you think?
Many thanks and best regards
Dirk
[1]
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/input/touchscreen/atmel_mxt_ts.c?id=50a77c658b80e7e3303e3bcec195b30e2b62d513
next reply other threads:[~2015-01-12 9:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 9:50 Dirk Behme [this message]
2015-01-12 10:04 ` Input: atmel_mxt_ts - don't always download device config? Nick Dyer
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=54B398D3.7010803@de.bosch.com \
--to=dirk.behme@de.bosch.com \
--cc=linux-input@vger.kernel.org \
--cc=nick.dyer@itdev.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.