From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: sergk sergk2mail <sergk.admin@gmail.com>
Cc: Gregor Riepl <onitake@gmail.com>, linux-input@vger.kernel.org
Subject: Re: How to use ACPI for touchscreen
Date: Wed, 2 Mar 2016 13:19:49 -0800 [thread overview]
Message-ID: <20160302211949.GD4318@dtor-ws> (raw)
In-Reply-To: <CA+V1LzoiheCTZRv9xS=f_aTLkb27vw0aha=otYy=eiwOPB52+Q@mail.gmail.com>
On Wed, Mar 02, 2016 at 06:13:27PM +0000, sergk sergk2mail wrote:
> "Why do you think that mlsfw in modalias string has anything to do with
> loading firmware? I must have misunderstood your statement..."
>
> Hi Dmitriy,
> Its rather guessing based on such disovering: On Chuwi Vi10 rev 11
> under Android the only touch related module that is loaded is
> atmel_mxt_ts while I exactly know (and have firmware too) that in this
> tablet there is Chipone icn8528.h. (drivers from Windows + dmesg
> provs this).
> 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
> module. According specs of Chipone icn85xx it looks that it even has
> corresponding mode - to be initialized from firmware and work after
> with it. It looks weird, but this is the clevest explanation that I
> could provide - I never seen before such behaviour in Android when
> there is no dedicated driver for touch screen.
I find this hard to believe. If you inspect /proc/bus/input/devices you
should be able to see the parent device for the touchscreen (via sysfs
entry) and if you inspect sysfs you should be able to see the driver
that is connected to the device (unless they use i2c dev from userspace
but then they'd have to resort to polling and their battery life would
be abysmal).
>
> In anyway - this is only curiousity, the main goal is simple - to
> create a driver for icn85xx that wakeup it and loads firmware.
> I have specs, I have firmware, there is for arm open source drivers
> (including firmware in .h file):
> https://github.com/bbelos/rk3188-kernel/blob/master/drivers/input/touchscreen/ICN8503/icn85xx.c
Just so we are clear: the driver above is not an open source driver.
Even though it has MODULE_LICENSE("GPL") to circumvent kernel module
loading policies the actual copyright notice in the sources say that the
code is proprietary.
If any code is taken from it the resulting driver should not be
submitted for inclusion in mainline Linux kernel unless it is done by
ChipOne themselves.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2016-03-02 21:19 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 [this message]
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=20160302211949.GD4318@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=onitake@gmail.com \
--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).