From: Greg KH <greg@kroah.com>
To: Johan Hovold <johan@kernel.org>
Cc: linux-usb@vger.kernel.org, stable <stable@vger.kernel.org>
Subject: Re: [PATCH 1/2] USB: serial: mos7720: fix remote wakeup
Date: Mon, 11 Nov 2019 14:28:23 +0100 [thread overview]
Message-ID: <20191111132823.GB450958@kroah.com> (raw)
In-Reply-To: <20191107132119.2159-1-johan@kernel.org>
On Thu, Nov 07, 2019 at 02:21:18PM +0100, Johan Hovold wrote:
> The driver was setting the device remote-wakeup feature during probe in
> violation of the USB specification (which says it should only be set
> just prior to suspending the device). This could potentially waste
> power during suspend as well as lead to spurious wakeups.
>
> Note that USB core would clear the remote-wakeup feature at first
> resume.
>
> Fixes: 0f64478cbc7a ("USB: add USB serial mos7720 driver")
> Cc: stable <stable@vger.kernel.org> # 2.6.19
> Signed-off-by: Johan Hovold <johan@kernel.org>
> ---
> drivers/usb/serial/mos7720.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/drivers/usb/serial/mos7720.c b/drivers/usb/serial/mos7720.c
> index 18110225d506..2ec4eeacebc7 100644
> --- a/drivers/usb/serial/mos7720.c
> +++ b/drivers/usb/serial/mos7720.c
> @@ -1833,10 +1833,6 @@ static int mos7720_startup(struct usb_serial *serial)
> product = le16_to_cpu(serial->dev->descriptor.idProduct);
> dev = serial->dev;
>
> - /* setting configuration feature to one */
> - usb_control_msg(serial->dev, usb_sndctrlpipe(serial->dev, 0),
> - (__u8)0x03, 0x00, 0x01, 0x00, NULL, 0x00, 5000);
> -
> if (product == MOSCHIP_DEVICE_ID_7715) {
> struct urb *urb = serial->port[0]->interrupt_in_urb;
>
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
prev parent reply other threads:[~2019-11-11 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 13:21 [PATCH 1/2] USB: serial: mos7720: fix remote wakeup Johan Hovold
2019-11-07 13:21 ` [PATCH 2/2] USB: serial: mos7840: " Johan Hovold
2019-11-11 13:28 ` Greg KH
2019-11-11 13:28 ` Greg KH [this message]
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=20191111132823.GB450958@kroah.com \
--to=greg@kroah.com \
--cc=johan@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stable@vger.kernel.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).