linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Henrik Rydberg" <rydberg@euromail.se>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Oliver Neukum <oliver@neukum.org>,
	linux-input@vger.kernel.org
Subject: Re: [PATCH] input: Fix USB autosuspend on bcm5974
Date: Fri, 7 Oct 2011 20:13:10 +0200	[thread overview]
Message-ID: <20111007181310.GA2762@polaris.bitmath.org> (raw)
In-Reply-To: <20111007173937.GB13468@srcf.ucam.org>

On Fri, Oct 07, 2011 at 06:39:37PM +0100, Matthew Garrett wrote:
> On Fri, Oct 07, 2011 at 07:42:14PM +0200, Henrik Rydberg wrote:
> > On Fri, Oct 07, 2011 at 06:13:25PM +0100, Matthew Garrett wrote:
> > > I've seen the occasional error message on my 3,1, but I haven't seen any 
> > > looping suspend/resume.
> > 
> > You need to sprinkle some outputs in the actual autosuspend machinery to see it.
> 
> Can you describe exactly what you're seeing?

With a corrected version of your patch, which enables autosuspend
while the device file is open, I see the power layer repeatedly
suspending and resuming the usb device in question, even while
constantly moving a finger around on the pad. In conjunction with this
behavior, I see error messages indicating unknown/faulty packets
appearing in the bcm5974 interrupt handler.

For the next version of the patch, please add a) why you want to
change the current behavior, b) what the patch is supposed to do, and
c) what exact devices are known to work with the patch.

If there are any strange error messages appearing as a result of the
patch, mentioning them would be minimum. Better yet, an explanation of
why they appear, or how an improved patch makes them disappear would
be great.

Thanks,
Henrik

  reply	other threads:[~2011-10-07 18:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-06 21:36 [PATCH] input: Fix USB autosuspend on bcm5974 Matthew Garrett
2011-10-06 22:38 ` Dmitry Torokhov
2011-10-06 23:19   ` Matthew Garrett
2011-10-07  6:37     ` Oliver Neukum
2011-10-07 12:36       ` Matthew Garrett
2011-10-07 16:20         ` Dmitry Torokhov
2011-10-07 16:27           ` Matthew Garrett
2011-10-07 17:06             ` Henrik Rydberg
2011-10-07 17:13               ` Matthew Garrett
2011-10-07 17:42                 ` Henrik Rydberg
2011-10-07 17:39                   ` Matthew Garrett
2011-10-07 18:13                     ` Henrik Rydberg [this message]
2011-10-07 19:20                       ` Matthew Garrett

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=20111007181310.GA2762@polaris.bitmath.org \
    --to=rydberg@euromail.se \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=oliver@neukum.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).