From: Jiri Kosina <jkosina@suse.cz>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Adrian Bunk <bunk@stusta.de>,
Andrew Morton <akpm@linux-foundation.org>,
Soeren Sonnenburg <kernel@nn7.de>,
Sergey Vlasov <vsu@altlinux.ru>,
linux-input@atrey.karlin.mff.cuni.cz
Subject: Re: appletouch quirk doesn't run at resume
Date: Sun, 18 Mar 2007 19:45:06 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0703181934530.4195@jikos.suse.cz> (raw)
In-Reply-To: <20070318004240.GO752@stusta.de>
On Sun, 18 Mar 2007, Adrian Bunk wrote:
> > 1.) The quirk added in commit a417a21e10831bca695b4ba9c74f4ddf5a95ac06
> > for the appletouch driver doesn't seem to work after resume.
> Not a regression, but still a bug. Appropriate people added to the Cc.
(trimmed CC a little bit)
Thomas, could you please provide more information? Did it ever work for
you after suspend/resume cycle and it just broke at some point in the
past, or you are not sure whether it ever worked?
Also, what exactly does it mean that it doesn't work? Are both the
interfaces after resume bound to usbhid driver (you can check this in
/sys)? When the quirk works correctly, only the keyboard interface should
be bound to usbhid driver. Please check the binding both before and after
suspend/resume cycle, and let me know.
Thanks,
--
Jiri Kosina
next prev parent reply other threads:[~2007-03-18 18:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0703160925270.26106@woody.linux-foundation.org>
[not found] ` <200703162134.14265.rjw@sisk.pl>
[not found] ` <1174078066.13341.279.camel@localhost.localdomain>
[not found] ` <1174087552.13341.332.camel@localhost.localdomain>
[not found] ` <45FBBDEA.9060708@m3y3r.de>
2007-03-18 0:42 ` appletouch quirk doesn't run at resume Adrian Bunk
2007-03-18 18:45 ` Jiri Kosina [this message]
2007-03-18 19:01 ` Thomas Meyer
2007-03-18 19:22 ` Jiri Kosina
2007-03-27 21:02 ` Thomas Meyer
2007-03-28 12:26 ` Jiri Kosina
2007-03-28 13:24 ` Dmitry Torokhov
2007-03-28 16:51 ` Thomas Meyer
2007-03-28 17:06 ` Jiri Kosina
2007-03-28 17:35 ` Dmitry Torokhov
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=Pine.LNX.4.64.0703181934530.4195@jikos.suse.cz \
--to=jkosina@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=bunk@stusta.de \
--cc=kernel@nn7.de \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@m3y3r.de \
--cc=vsu@altlinux.ru \
/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).