From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Aaron Ma <aaron.ma@canonical.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Cheiny@synaptics.com, aduggan@synaptics.com,
benjamin.tissoires@redhat.com
Subject: Re: [PATCH 1/2] Input: synaptics-rmi4 - clear irqs before set irqs
Date: Tue, 11 Jun 2019 10:35:45 -0700 [thread overview]
Message-ID: <20190611173545.GE143729@dtor-ws> (raw)
In-Reply-To: <7da443d0-f433-c5a5-5194-707362eb2ee5@canonical.com>
On Tue, Jun 11, 2019 at 12:55:58AM +0800, Aaron Ma wrote:
>
> On 6/10/19 12:55 AM, Dmitry Torokhov wrote:
> > Hi Aaron,
> >
> > On Wed, Feb 20, 2019 at 05:41:59PM +0100, Aaron Ma wrote:
> >> rmi4 got spam data after S3 resume on some ThinkPads.
> >> Then TrackPoint lost when be detected by psmouse.
> >> Clear irqs status before set irqs will make TrackPoint back.
> > Could you please give me an idea as to what this spam data is?
> >
>
> It should be some data 0 during suspend/resume.
> Actually I don't know how these data 0 is produced.
> Not all synaptics touchpads have this issue.
>
> > In F03 probe we clear all pending data before enabling the function,
>
> Yes we did, but not after resume.
Yes, I understand that. The question I was asking: if we add code
consuming all pending data to f03->suspend(), similarly to what we are
doing at probe time, will it fix the issue with trackstick losing
synchronization and attempting disconnect?
>
> > maybe the same needs to be done on resume, instead of changing the way
> > we handle IRQ bits?
>
> This patch is supposed to clear irq status like it in fn probe. Not
> changing IRQ bits.
What I meant is changing how we enable IRQ bits. I would really prefer
we did not lose IRQ state for other functions when we enable interrupts
for given function.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2019-06-11 17:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 16:41 [PATCH 1/2] Input: synaptics-rmi4 - clear irqs before set irqs Aaron Ma
2019-02-20 16:42 ` [PATCH 2/2] Input: synaptics-rmi4 - export nosleep of f01 via sysfs Aaron Ma
2019-06-09 16:53 ` Dmitry Torokhov
2019-03-08 23:13 ` [PATCH 1/2] Input: synaptics-rmi4 - clear irqs before set irqs Christopher Heiny
2019-03-09 8:37 ` Aaron Ma
2019-03-28 6:02 ` Aaron Ma
2019-04-02 16:16 ` Christopher Heiny
2019-04-03 13:58 ` Aaron Ma
2019-06-04 2:45 ` Aaron Ma
2019-06-04 5:19 ` Christopher Heiny
2019-06-07 7:48 ` Aaron Ma
2019-06-09 16:55 ` Dmitry Torokhov
2019-06-10 16:55 ` Aaron Ma
2019-06-11 17:35 ` Dmitry Torokhov [this message]
2019-06-14 4:26 ` Aaron Ma
2019-11-19 5:34 ` 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=20190611173545.GE143729@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=Cheiny@synaptics.com \
--cc=aaron.ma@canonical.com \
--cc=aduggan@synaptics.com \
--cc=benjamin.tissoires@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).