From: Kai Heng Feng <kai.heng.feng@canonical.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
hotwater438@tutanota.com, Jiri Kosina <jikos@kernel.org>,
Stephen Boyd <swboyd@chromium.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Dmitry Torokhov <dtor@chromium.org>,
"open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ELAN touchpad i2c_hid bugs fix
Date: Thu, 21 Mar 2019 17:28:15 +0800 [thread overview]
Message-ID: <DDBA2E60-2658-413B-969A-59DD1AFB0536@canonical.com> (raw)
In-Reply-To: <CAHp75VeavkzZDYK4CWAC62GciynQ3KYgmPpPRwsd3RcLFw4jxA@mail.gmail.com>
> On Mar 21, 2019, at 4:55 PM, Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
>
> On Thu, Mar 21, 2019 at 6:08 AM Kai-Heng Feng
> <kai.heng.feng@canonical.com> wrote:
>> at 01:18, Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
>>> On Wed, Mar 20, 2019 at 6:55 PM Kai-Heng Feng
>>> <kai.heng.feng@canonical.com> wrote:
>>>> at 23:39, Hans de Goede <hdegoede@redhat.com> wrote:
>>>>> On 3/20/19 3:37 PM, Benjamin Tissoires wrote:
>
>>>> Recently we found that Elan touchpad doesn’t like GpioInt() from its _CRS.
>>>> Once the Interrupt() is used instead, the issue goes away.
>>>
>>> IIRC i2c core tries to get interrupt from Interrupt() resource and
>>> then falls back to GpioInt().
>>> See i2c_acpi_get_info() and i2c_device_probe().
>>
>> Here’s its ASL:
>
>> Name (SBFB, ResourceTemplate ()
>> {
>> I2cSerialBusV2 (0x002C, ControllerInitiated, 0x00061A80,
>> AddressingMode7Bit, "\\_SB.PCI0.I2C4",
>> 0x00, ResourceConsumer, , Exclusive,
>> )
>> })
>> Name (SBFG, ResourceTemplate ()
>> {
>> GpioInt (Level, ActiveLow, ExclusiveAndWake, PullUp, 0x0000,
>> "\\_SB.GPO1", 0x00, ResourceConsumer, ,
>> )
>> { // Pin list
>> 0x0012
>> }
>> })
>> Name (SBFI, ResourceTemplate ()
>> {
>> Interrupt (ResourceConsumer, Level, ActiveLow, ExclusiveAndWake, ,, )
>> {
>> 0x0000003C,
>> }
>> })
>
>> Method (_CRS, 0, NotSerialized) // _CRS: Current Resource Settings
>> {
>
>> If ((OSYS < 0x07DC))
>> {
>> Return (SBFI) /* \_SB_.PCI0.I2C4.TPD0.SBFI */
>> }
>
> This will return only Interrupt() resource
>
>>
>> Return (ConcatenateResTemplate (SBFB, SBFG))
>
> This one I2cSerialBus() and GpioInt().
>
>> }
>
>
>> }
>> }
>>
>> Change SBFG to SBFI in its _CRS can workaround the issue.
>> Is ASL in this form possible to do the flow you described?
>
> Since it's enumerated in Linux as I2C device, it means it gets I2C and
> GPIO resources.
> So, no, it's not possible.
>
> What are you describing might tell us about one of the following:
> - touchpad should be switched to PS/2 mode in order to get working
> - GPIO resource is not correct / bug in GPIO driver
>
> I don't believe the first one is a case here.
> If GPIO resource is not correct and main OS has some quirks, we need
> to do similar in Linux.
How do I check quirks on Windows?
> Otherwise, debugging GPIO driver, starting from what exactly (pin
> number, pin settings, etc) gets i2c-hid module.
Ok, please let me know where should I start looking into.
>
> Note, ACPICA and related stuff is done in order to be Windows compatible.
> If you have settings in BIOS that defines OS to boot, it should be
> chosen Windows.
Yes, it’s Windows.
Kai-Heng
>
> --
> With Best Regards,
> Andy Shevchenko
next prev parent reply other threads:[~2019-03-21 9:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <LaQHUFs--3-1@tutanota.com>
2019-03-20 14:37 ` [PATCH] ELAN touchpad i2c_hid bugs fix Benjamin Tissoires
2019-03-20 15:39 ` Hans de Goede
2019-03-20 16:53 ` Kai-Heng Feng
2019-03-20 17:18 ` Andy Shevchenko
2019-03-21 4:08 ` Kai-Heng Feng
2019-03-21 8:55 ` Andy Shevchenko
2019-03-21 9:28 ` Kai Heng Feng [this message]
2019-03-21 8:57 ` Hans de Goede
2019-03-21 9:48 ` Andy Shevchenko
2019-04-01 21:37 ` Mario.Limonciello
2019-04-02 4:18 ` Kai Heng Feng
2019-04-02 14:08 ` Mario.Limonciello
2019-04-03 9:24 ` Kai-Heng Feng
2019-03-20 17:11 ` Andy Shevchenko
[not found] ` <LaUpAlT--3-1@tutanota.com>
[not found] ` <LaeGPSe--3-1@tutanota.com>
2019-03-24 12:27 ` Hans de Goede
[not found] ` <LakgsCJ--3-1@tutanota.com>
2019-03-24 18:37 ` Hans de Goede
2019-03-24 19:10 Vladislav Dalechyn
2019-03-25 9:23 ` Benjamin Tissoires
2019-03-25 12:57 Vladislav Dalechyn
2019-03-25 16:02 ` Dmitry Torokhov
2019-03-25 16:38 ` Hans de Goede
2019-03-25 16:56 ` Dmitry Torokhov
[not found] ` <Laq4ykv--3-1@tutanota.com>
2019-03-25 18:30 ` Dmitry Torokhov
2019-03-29 12:18 ` Hans de Goede
2019-03-29 18:23 ` Dmitry Torokhov
2019-04-01 12:26 ` 廖崇榮
[not found] ` <LbI7kio--3-1@tutanota.com>
2019-04-03 11:18 ` Hans de Goede
[not found] ` <LbZjy9p--3-1@tutanota.com>
2019-04-11 16:17 ` Kai-Heng Feng
[not found] ` <LcKqhgD--3-1@tutanota.com>
2019-04-13 8:42 ` Kai-Heng Feng
[not found] ` <LcVmBjG--3-1@tutanota.com>
2019-04-15 11:42 ` Hans de Goede
2019-04-16 3:59 ` Kai-Heng Feng
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=DDBA2E60-2658-413B-969A-59DD1AFB0536@canonical.com \
--to=kai.heng.feng@canonical.com \
--cc=andy.shevchenko@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=dtor@chromium.org \
--cc=hdegoede@redhat.com \
--cc=hotwater438@tutanota.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swboyd@chromium.org \
/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).