From: "Henrik Rydberg" <rydberg@euromail.se>
To: Oliver Neukum <oliver@neukum.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Matthew Garrett <mjg@redhat.com>
Subject: Re: [PATCH v2] Input: bcm5974 - Fix USB autosuspend
Date: Mon, 19 Dec 2011 21:30:59 +0100 [thread overview]
Message-ID: <20111219203059.GA6749@polaris.bitmath.org> (raw)
In-Reply-To: <201112191842.08635.oliver@neukum.org>
On Mon, Dec 19, 2011 at 06:42:08PM +0100, Oliver Neukum wrote:
> Am Montag, 19. Dezember 2011, 18:02:03 schrieb Henrik Rydberg:
> > static int bcm5974_suspend(struct usb_interface *iface, pm_message_t message)
> > @@ -870,6 +884,9 @@ static int bcm5974_probe(struct usb_interface *iface,
> > dev->tp_data, dev->cfg.tp_datalen,
> > bcm5974_irq_trackpad, dev, 1);
> >
> > + /* Required for autosuspend */
> > + iface->needs_remote_wakeup = 1;
> > +
> > /* create bcm5974 device */
> > usb_make_path(udev, dev->phys, sizeof(dev->phys));
> > strlcat(dev->phys, "/input0", sizeof(dev->phys));
>
> It is not nice to set needs_remote_wakeup on suspend() because
> it influences the decision of usbcore to suspend at all, in particular
> manually set quirks will not be fully honored if you do it this way.
> In addition it will never be reset, even as the device is closed.
>
> Please set it in open() and clear it in close()
Oliver: thanks for the advice, and thanks for the review.
Matthew: There seems to be a problem with the hardware wake-up in
response to short taps on the trackpad. Too much of a regression to be
acceptable, I am afraid. Unless this laptop (MBA 3.1) turns out to be
a special case, I think we will have to let this patch rest.
Thanks,
Henrik
next prev parent reply other threads:[~2011-12-19 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 17:02 [PATCH v2] Input: bcm5974 - Fix USB autosuspend Henrik Rydberg
2011-12-19 17:42 ` Oliver Neukum
2011-12-19 20:30 ` Henrik Rydberg [this message]
2011-12-20 8:47 ` Oliver Neukum
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=20111219203059.GA6749@polaris.bitmath.org \
--to=rydberg@euromail.se \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--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).