From: Jan-Matthias Braun <jan_braun@gmx.net>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Jiri Kosina <jkosina@suse.cz>,
Benjamin Tissoires <benjamin.tissoires@gmail.com>,
Greg Kroah-Hartman <greg@kroah.com>,
linux-input@vger.kernel.org
Subject: Re: hid-multitouch: eGalax Touchscreen not resuming after suspend
Date: Thu, 29 Nov 2012 15:03:04 +0100 [thread overview]
Message-ID: <3334839.0y63iIARTX@orthese> (raw)
In-Reply-To: <1655801.HZ7A866RlZ@vostro.rjw.lan>
Hi Rafael,
thanks for looking into this.
Am Donnerstag, 29. November 2012, 01:20:04 schrieb Rafael J. Wysocki:
> On Tuesday, November 27, 2012 09:26:11 PM Jiri Kosina wrote:
> > On Sun, 25 Nov 2012, Jan-Matthias Braun wrote:
> > > I have now done a git bisection from 3.0 to 3.1 and have found commit
> > > 1e2ef05bb8cf851a694d38e9170c89e7ff052741 PM: Limit race conditions between runtime PM and system sleep (v2)
> > > to be the first one to introduce the necessity of a module reload after resume.
>
> So with that commit your device doesn't work after resume from system suspend
> unless you reload the driver?
Yes. Additionally, with later kernel revisions even this won't help, but I could imagine this to be a consequence of the same problem.
> > > I hope that this helps in finding a solution. As I (again) don't immediatly
> > > know how to go on, I kindly ask you to give me some hints for testing/patching
> > > or even a possible solution. :-)
>
> Can you apply the patch below to the current mainline kernel and see if it makes any
> difference, please?
It does: Current mainline kernel (version >3.7.0-rc7 from git) is not showing the problem, if the patch is applied.
Cheers,
Jan
> ---
> drivers/base/power/main.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> Index: linux/drivers/base/power/main.c
> ===================================================================
> --- linux.orig/drivers/base/power/main.c
> +++ linux/drivers/base/power/main.c
> @@ -589,8 +589,6 @@ static int device_resume(struct device *
> if (!dev->power.is_suspended)
> goto Unlock;
>
> - pm_runtime_enable(dev);
> -
> if (dev->pm_domain) {
> info = "power domain ";
> callback = pm_op(&dev->pm_domain->ops, state);
> @@ -1136,8 +1134,6 @@ static int __device_suspend(struct devic
>
> if (error)
> async_error = error;
> - else if (dev->power.is_suspended)
> - __pm_runtime_disable(dev, false);
>
> return error;
> }
>
>
>
next prev parent reply other threads:[~2012-11-29 14:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 11:58 hid-multitouch: eGalax Touchscreen not resuming after suspend Jan-Matthias Braun
2012-11-20 12:47 ` Benjamin Tissoires
2012-11-21 9:33 ` Jan-Matthias Braun
2012-11-21 13:36 ` Benjamin Tissoires
2012-11-22 19:00 ` Jan-Matthias Braun
2012-11-24 18:01 ` Jan-Matthias Braun
2012-11-24 19:27 ` Benjamin Tissoires
2012-11-25 11:23 ` Jan-Matthias Braun
2012-11-27 20:26 ` Jiri Kosina
2012-11-28 1:01 ` Rafael J. Wysocki
2012-11-29 0:20 ` Rafael J. Wysocki
2012-11-29 14:03 ` Jan-Matthias Braun [this message]
2012-11-29 22:28 ` Rafael J. Wysocki
2012-12-04 22:11 ` Jan-Matthias Braun
2012-12-05 0:28 ` Rafael J. Wysocki
2012-12-05 9:12 ` Jan-Matthias Braun
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=3334839.0y63iIARTX@orthese \
--to=jan_braun@gmx.net \
--cc=benjamin.tissoires@gmail.com \
--cc=greg@kroah.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=rjw@sisk.pl \
/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).