From: Gregor Riepl <onitake@gmail.com>
To: sergk sergk2mail <sergk.admin@gmail.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: How to use ACPI for touchscreen
Date: Wed, 2 Mar 2016 19:25:07 +0100 [thread overview]
Message-ID: <56D73003.2060606@gmail.com> (raw)
In-Reply-To: <CA+V1LzoiheCTZRv9xS=f_aTLkb27vw0aha=otYy=eiwOPB52+Q@mail.gmail.com>
> When you rmmod atmel_mxt_ts the touch still continues to work! I guess
> someone just used atmel_mxt_ts probably as prototype for detecting
> (wake uping) chip and loading its firmware and after - no need in any
It may simply be that the pin assignments are the same for these devices, i.e.
they use the same physical pin for controller wakeup. This wouldn't surprise
me at all.
And since the wakeup sequence is sent before actually communicating with the
device over I2C, it seems logical that the ChipOne wakes up and stays on after
the atmel_probe function has been called - even if probe fails afterwards.
next prev parent reply other threads:[~2016-03-02 18:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-28 22:30 How to use ACPI for touchscreen sergk sergk2mail
2016-03-01 10:02 ` Gregor Riepl
2016-03-01 16:30 ` sergk sergk2mail
2016-03-01 16:55 ` sergk sergk2mail
2016-03-02 17:52 ` Dmitry Torokhov
2016-03-02 18:13 ` sergk sergk2mail
2016-03-02 18:25 ` Gregor Riepl [this message]
2016-03-02 19:00 ` sergk sergk2mail
2016-03-02 19:01 ` sergk sergk2mail
2016-03-02 19:11 ` sergk sergk2mail
2016-03-02 21:19 ` Dmitry Torokhov
2016-03-02 23:01 ` sergk sergk2mail
2016-03-13 0:15 ` sergk sergk2mail
2016-03-01 22:32 ` sergk sergk2mail
2016-03-01 22:56 ` Gregor Riepl
2016-03-02 12:50 ` sergk sergk2mail
2016-03-02 13:07 ` Gregor Riepl
2016-03-02 15:17 ` sergk sergk2mail
2016-03-02 16:49 ` Gregor Riepl
2016-03-02 15:56 ` sergk sergk2mail
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=56D73003.2060606@gmail.com \
--to=onitake@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=sergk.admin@gmail.com \
/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).