linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Dmitry Mastykin <mastichi@gmail.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Bastien Nocera <hadess@hadess.net>,
	linux-input@vger.kernel.org
Subject: Re: вопрос по suspend/resume в goodix
Date: Wed, 18 Dec 2019 07:16:38 +0100	[thread overview]
Message-ID: <bceaca05-bec1-4fcf-9f52-3a9a2a3318c7@redhat.com> (raw)
In-Reply-To: <CALieaecDVVO0GMySV8ge4ecsyPziRxKpCo=RTdWX266vzdNyBw@mail.gmail.com>

Hi,

On 13-12-2019 09:17, Dmitry Mastykin wrote:
> Hi guys!
> Thank you very much for your answers, it's always surprising how fast
> the community reacts!
> 
>> We have reports of the touchscreen no longer working after suspend/resume
>> on some GPD pocket devices, but not combined with these errors.
>>
> I copied my error messages precisely from gpd support site, because I
> have the same:
> https://gpdsupport.com/t/touchscreen-issue-resolved/132/84
> But seems that rmmod/insmod helps in their case.
> I noticed that the problem is not repeatable. But happens very often.

Interesting I did not realize the same errors are showing on the GPD pocket.

I have the feeling this might have something todo with us not putting the
touchscreen controller to sleep on ACPI devices because we cannot use
the IRQ pin as GPIO which is necessary for wakeup.

On most newer devices (such as the GPD) the IRQ pin is actually declared
as a GpioInt in the ACPI tables, so we should be able to use it as a GPIO
with some extra work.

I plan to write a patch to make us do this sometime in the near future
(no idea when I will get around to this though). I will put you
(Dmitry Mastykin) in the Cc of the patch when I get around to writing it.

Note I do not know if this patch will actually help.

Regards,

Hans


> 
> 
>> When this happens, are these messages appear constantly, or only in
>> response to actual touch? Can you still interact with the device?
>>
> Constantly with 25Hz frequency.
> 
>> The fact that you can talk to the controller like that is interesting.
>> Just to confirm, does it return sane data, or garbage?
>>
> root@or212:/home/u# i2cset -y 6 0x5d 0x81 0x4e 0x00 i
> root@or212:/home/u# i2cset -y 6 0x5d 0x81 0x4e i
> root@or212:/home/u# i2cget -y 6 0x5d
> 0x83
> root@or212:/home/u# i2cset -y 6 0x5d 0x81 0x4e 0x00 i
> root@or212:/home/u# i2cset -y 6 0x5d 0x81 0x4e i
> root@or212:/home/u# i2cget -y 6 0x5d
> 0x81
> First I touch with 3 fingers, then with one.
> 
>> What is the model of the tablet?
>>
> Not sure about model, seems that it's this one:
> http://logic-instrument.com/en/fieldbook-k122.php
> 
> Dmesg is attached
> 
> Thank you!
> Kind regards,
> Dmitry Mastykin
> 
> On Thu, Dec 12, 2019 at 11:51 PM Hans de Goede <hdegoede@redhat.com> wrote:
>>
>> Hi,
>>
>> On 12-12-2019 20:20, Dmitry Torokhov wrote:
>>> Hi Dmitry,
>>>
>>> On Thu, Dec 12, 2019 at 06:34:46PM +0300, Dmitry Mastykin wrote:
>>>> Здравствуйте, Дмитрий.
>>>> Простите, что отвлекаю, если что - не отвечайте и в лучшем случае
>>>> пошлите в mail-list)
>>>> У меня есть планшет с x86, вариантом Debian с ядром 4.15 и
>>>> контроллером тач-скрина gt928.
>>>
>>> What is the model of the tablet?
>>>
>>>> После suspend/resume не всегда, но очень часто тачскрин перестает
>>>> работать и постоянно выводит:
>>>> [ 3276.729412] Goodix-TS i2c-GDIX1002:00: I2C write end_cmd error
>>>> [ 3276.770153] Goodix-TS i2c-GDIX1002:00: I2C transfer error: -121
>>>
>>> When this happens, are these messages appear constantly, or only in
>>> response to actual touch? Can you still interact with the device?
>>>
>>> Could you please send the full dmesg so we know more about the device.
>>>
>>> Hans, Bastien, have you seen such issues with Goodix occasionally
>>> misbehaving on resume?
>>
>> We have reports of the touchscreen no longer working after suspend/resume
>> on some GPD pocket devices, but not combined with these errors.
>>
>> Regards,
>>
>> Hans
>>
>>
>>>
>>>> По i2cget/i2cset контроллер успешно отвечает.
>>>
>>> The fact that you can talk to the controller like that is interesting.
>>> Just to confirm, does it return sane data, or garbage?
>>>
>>> Thanks.
>>>
>>


  parent reply	other threads:[~2019-12-18  6:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CALieaefYFFBaFAo4E7hsESrxhN7N_tbWbeG_C6WHzwDpFiLqeQ@mail.gmail.com>
2019-12-12 19:20 ` вопрос по suspend/resume в goodix Dmitry Torokhov
2019-12-12 20:51   ` Hans de Goede
     [not found]     ` <CALieaecDVVO0GMySV8ge4ecsyPziRxKpCo=RTdWX266vzdNyBw@mail.gmail.com>
2019-12-18  6:16       ` Hans de Goede [this message]
2019-12-18 14:50         ` Dmitry Mastykin
2019-12-18 15:07           ` Hans de Goede
     [not found]             ` <CALieaecwpcimMDos5QWz-MP1ZW+16HPcTc0rnX4GCYnRqoxR4g@mail.gmail.com>
2019-12-20 10:45               ` Hans de Goede
2019-12-20 15:40                 ` Dmitry Mastykin
2019-12-25 12:24                   ` Hans de Goede
2019-12-19  9:33   ` Bastien Nocera

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=bceaca05-bec1-4fcf-9f52-3a9a2a3318c7@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hadess@hadess.net \
    --cc=linux-input@vger.kernel.org \
    --cc=mastichi@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).