All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: linux-input@vger.kernel.org, dtor@mail.ru
Subject: Re: [PATCH V3] input: Fix USB autosuspend on bcm5974
Date: Tue, 11 Oct 2011 01:11:03 +0100	[thread overview]
Message-ID: <20111011001102.GA28157@srcf.ucam.org> (raw)
In-Reply-To: <20111010224431.GA2377@polaris.bitmath.org>

On Tue, Oct 11, 2011 at 12:44:31AM +0200, Henrik Rydberg wrote:
> On Mon, Oct 10, 2011 at 10:12:31PM +0100, Matthew Garrett wrote:
> > Is this with the patch I sent for usbhid earlier applied? Right now the 
> > keyboard will fail to suspend after system suspend, which will keep the 
> > entire composite device awake. I'm looking into your other issue now.
> 
> Ahh, yes, the suspend failure was due to the keyboard interface,
> thanks. The loop-on-closed is still present, though (as expected,
> since there is no usb_mark_last_busy() call).

Ah, right, sorry - I wasn't trying to use the device after it had been 
closed. In an ideal world we'd really want to be able to indicate that 
we don't want a remote wakeup in that situation. Otherwise, the patch 
looks good. Thank you!

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2011-10-11  0:11 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-10 15:47 [PATCH V3] input: Fix USB autosuspend on bcm5974 Matthew Garrett
2011-10-10 21:05 ` Henrik Rydberg
2011-10-10 21:12   ` Matthew Garrett
2011-10-10 22:44     ` Henrik Rydberg
2011-10-11  0:11       ` Matthew Garrett [this message]
2011-10-11  4:10         ` Oliver Neukum
2011-10-11 11:04           ` Henrik Rydberg
2011-10-11 11:09             ` Oliver Neukum
2011-10-11 20:42               ` Matthew Garrett
2011-10-12  6:32                 ` Oliver Neukum
2011-10-12 14:33                   ` Alan Stern
2011-10-12 14:37                     ` Oliver Neukum
2011-10-12 15:28                       ` Alan Stern
2011-10-12 16:16                         ` Matthew Garrett
2011-10-12 16:56                           ` Oliver Neukum
2011-10-12 16:59                             ` Matthew Garrett
2011-10-12 17:24                               ` Alan Stern
2011-10-12 17:26                                 ` Matthew Garrett
2011-10-12 17:41                                   ` Alan Stern
2011-10-12 18:33                               ` Henrik Rydberg
2011-10-12 19:21                                 ` Alan Stern
2011-10-13  8:20                                   ` Henrik Rydberg
2011-10-13 15:49                                     ` Alan Stern
2011-10-13 17:21                                       ` Henrik Rydberg
2011-10-12 17:11                         ` Oliver Neukum
2011-10-12 19:18                           ` Alan Stern
2011-10-11 16:05           ` Dmitry Torokhov
2011-10-11 16:43             ` Alan Stern
2011-10-12  7:03               ` Oliver Neukum
2011-10-12 13:54                 ` Matthew Garrett
2011-10-12 14:18                   ` Alan Stern
2011-10-12 14:26                     ` Matthew Garrett
2011-10-12 14:38                       ` Oliver Neukum
2011-10-12 18:50                         ` Henrik Rydberg
2011-10-13  6:47                           ` Oliver Neukum
2011-10-10 21:16   ` 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=20111011001102.GA28157@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=dtor@mail.ru \
    --cc=linux-input@vger.kernel.org \
    --cc=rydberg@euromail.se \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.