linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: sergk sergk2mail <sergk.admin@gmail.com>
To: Gregor Riepl <onitake@gmail.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>, linux-input@vger.kernel.org
Subject: Re: How to use ACPI for touchscreen
Date: Wed, 2 Mar 2016 19:00:01 +0000	[thread overview]
Message-ID: <CA+V1Lzr4pOJs1VG3V1MzAR4bEr1gjoJKfU9hAzVxpLwNErMv4Q@mail.gmail.com> (raw)
In-Reply-To: <56D73003.2060606@gmail.com>

Hi Gregor,

Actually if you look for the code of atmel_mxt_ts - all actions are in probe.
Also simple experimental like:
echo maxtouch 0x48 > /sys/bus/i2c/i2c-4/new_device
you got the same as in my case with modified your driver:

Mar 02 18:51:39 archiso kernel: device: '4-0048': device_add
Mar 02 18:51:39 archiso kernel: bus: 'i2c': add device 4-0048
Mar 02 18:51:39 archiso kernel: PM: Adding info for i2c:4-0048
Mar 02 18:51:39 archiso kernel: i2c i2c-4: new_device: Instantiated
device maxtouch at 0x48
Mar 02 18:51:39 archiso kernel: bus: 'i2c': add driver atmel_mxt_ts
Mar 02 18:51:39 archiso kernel: bus: 'i2c': driver_probe_device:
matched device 4-0048 with driver atmel_mxt_ts
Mar 02 18:51:39 archiso kernel: bus: 'i2c': really_probe: probing
driver atmel_mxt_ts with device 4-0048
Mar 02 18:51:39 archiso kernel: atmel_mxt_ts 4-0048: no default pinctrl state
Mar 02 18:51:39 archiso kernel: devices_kset: Moving 4-0048 to end of list
Mar 02 18:51:39 archiso kernel: atmel_mxt_ts 4-0048: No platform data specified
Mar 02 18:51:39 archiso kernel: atmel_mxt_ts: probe of 4-0048 faile

Regards,
                 Serge Kolotylo.

PS: it will be really good if here will be someone who is fluent in
Chinese and could directly read spec for Chipone and translate it to
us.

  reply	other threads:[~2016-03-02 19:00 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
2016-03-02 19:00             ` sergk sergk2mail [this message]
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=CA+V1Lzr4pOJs1VG3V1MzAR4bEr1gjoJKfU9hAzVxpLwNErMv4Q@mail.gmail.com \
    --to=sergk.admin@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=onitake@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).