From: Gregor Riepl <onitake@gmail.com>
To: sergk sergk2mail <sergk.admin@gmail.com>, linux-input@vger.kernel.org
Subject: Re: How to use ACPI for touchscreen
Date: Wed, 2 Mar 2016 14:07:44 +0100 [thread overview]
Message-ID: <56D6E5A0.9080509@gmail.com> (raw)
In-Reply-To: <CA+V1Lzr09-GU8yS9RHU=qO=200DiCTCXEqc3zP0953uLOWaoKQ@mail.gmail.com>
> echo icn8528 0x48 > /sys/bus/i2c/devices/i2c-4/newdevice
> After this kernel automatically loads myicn_ts_acpi.ko module.
>
> ...
>
> gsl_ts_probe: got a device named icn8528 at address 0x48, IRQ 0, flags
> 0x0
> Mar 02 12:07:31 archiso kernel: icn8528 4-0048: gsl_ts_probe: missing
> IRQ configuration
> Mar 02 12:07:31 archiso kernel: icn8528: probe of 4-0048 rejects match -19
>
> So, based on main line output: archiso kernel: CHPN0001 4-0048: probe
> info: gsl_ts_probe: got a device named CHPN0001 at address 0x48, IRQ
> 0, flags 0x0
>
> It looks that via ACPI no info is provided? No IRQ, no flags?
Umm... Ok, this seems a bit weird. Normally, you wouldn't create devices from
user space, as the kernel should automatically instantiate them when parsing
the DSDT or DT.
However, you got an ACPI name (CHPN0001), which leads me to conclude that some
interaction was going on.
Ok, now about the interrupt. The DSDT you posted previously contained this:
Interrupt (ResourceConsumer, Level, ActiveHigh, Exclusive, ,, )
{
0x00000044,
}
So the irq field should have been set. I don't really understand why this
wasn't the case, sorry.
I recommend you try to load the module without creating a device from user
space first. Either install the module and reboot or load the module manually.
next prev parent reply other threads:[~2016-03-02 13:07 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
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 [this message]
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=56D6E5A0.9080509@gmail.com \
--to=onitake@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).