From: Todd E Brandt <todd.e.brandt@linux.intel.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
Alan Stern <stern@rowland.harvard.edu>,
todd.e.brandt@intel.com
Subject: Re: [PATCH] serio: delay resume error handling til PM complete
Date: Wed, 25 Nov 2015 09:55:26 -0800 [thread overview]
Message-ID: <20151125175526.GA19683@linux.intel.com> (raw)
In-Reply-To: <20151125175112.GB23632@dtor-ws>
On Wed, Nov 25, 2015 at 09:51:12AM -0800, Dmitry Torokhov wrote:
> On Wed, Nov 25, 2015 at 09:25:59AM -0800, Todd E Brandt wrote:
> > On Tue, Nov 24, 2015 at 05:26:15PM -0800, Dmitry Torokhov wrote:
> > > On Tue, Nov 24, 2015 at 4:58 PM, Todd Brandt
> > > <todd.e.brandt@linux.intel.com> wrote:
> > > > Delay the error rescan for serio devices until the PM
> > > > complete phase. PM complete requires locking each device
> > > > before checking for and executing the complete callbacks.
> > > > Serio rescan also locks the device in order to reinit on
> > > > error, so this can cause a conflict which will result in
> > > > unnecessary delay.
> > > >
> > > > History:
> > > >
> > > > The issue was discovered on an ivy bridge platform with
> > > > i8042 keyboard/mouse. The mouse resume fails
> > >
> > > I'd first try to figure out why reconnect failed. What kind of
> > > mouse/touchpad is that?
> >
> > It's an Alps PS/2 glidepoint touchpad. The actual error appears to be
> > a failure in alps_identify as it attempts to get the EC report using
> > alps_rpt_cmd. However, I don't think this is too important since
> > the psmouse driver is just doing what it's supposed to. It's the
> > fact that the error was mitigated right in the middle of the system
> > resume that caused the delay.
> >
> > I expect that errors in input drivers will happen quite a lot. Users
>
> I do not expect that. If device is still there then we should be able to
> communicate with it. Failure to do so indicates that there is some issue
> (resume order?) and I would like to know what it is.
OK, I'll track it down. It's an off the shelf laptop so I don't expect
it's a hardware issue.
>
> >
> > don't typically care as long as the device eventually rights itself
> > and they don't notice.
>
> Theoretically you lose settings that you done manually through sysfs.
> Suspend/resume cycle is not supposed to lose your settings.
Agreed, but I think in most cases errors like these would go unnoticed.
But I understand your point.
>
> Thanks.
>
> --
> Dmitry
> --
> To unsubscribe from this list: send the line "unsubscribe linux-input" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-11-25 17:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1448068686.git.todd.e.brandt@linux.intel.com>
2015-11-25 0:58 ` [PATCH] serio: delay resume error handling til PM complete Todd Brandt
2015-11-25 1:26 ` Dmitry Torokhov
2015-11-25 15:24 ` Alan Stern
2015-11-25 17:39 ` Dmitry Torokhov
2015-11-25 17:25 ` Todd E Brandt
2015-11-25 17:51 ` Dmitry Torokhov
2015-11-25 17:55 ` Todd E Brandt [this message]
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=20151125175526.GA19683@linux.intel.com \
--to=todd.e.brandt@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=todd.e.brandt@intel.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).