From: Johan Hovold <johan@kernel.org>
To: gregkh@linuxfoundation.org
Cc: johan@kernel.org, stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "USB: serial: ch341: fix resume after reset" has been added to the 4.4-stable tree
Date: Tue, 17 Jan 2017 15:22:05 +0100 [thread overview]
Message-ID: <20170117142205.GB4040@localhost> (raw)
In-Reply-To: <1484658281245153@kroah.com>
On Tue, Jan 17, 2017 at 02:04:41PM +0100, Greg Kroah-Hartman wrote:
>
> This is a note to let you know that I've just added the patch titled
>
> USB: serial: ch341: fix resume after reset
>
> to the 4.4-stable tree which can be found at:
> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
> The filename of the patch is:
> usb-serial-ch341-fix-resume-after-reset.patch
> and it can be found in the queue-4.4 subdirectory.
>
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@vger.kernel.org> know about it.
>
>
> From ce5e292828117d1b71cbd3edf9e9137cf31acd30 Mon Sep 17 00:00:00 2001
> From: Johan Hovold <johan@kernel.org>
> Date: Fri, 6 Jan 2017 19:15:14 +0100
> Subject: USB: serial: ch341: fix resume after reset
>
> From: Johan Hovold <johan@kernel.org>
>
> commit ce5e292828117d1b71cbd3edf9e9137cf31acd30 upstream.
>
> Fix reset-resume handling which failed to resubmit the read and
> interrupt URBs, thereby leaving a port that was open before suspend in a
> broken state until closed and reopened.
>
> Fixes: 1ded7ea47b88 ("USB: ch341 serial: fix port number changed after resume")
> Fixes: 2bfd1c96a9fb ("USB: serial: ch341: remove reset_resume callback")
> Signed-off-by: Johan Hovold <johan@kernel.org>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> ---
> drivers/usb/serial/ch341.c | 17 +++++++++++++----
> 1 file changed, 13 insertions(+), 4 deletions(-)
>
> --- a/drivers/usb/serial/ch341.c
> +++ b/drivers/usb/serial/ch341.c
> @@ -538,14 +538,23 @@ static int ch341_tiocmget(struct tty_str
>
> static int ch341_reset_resume(struct usb_serial *serial)
> {
> - struct ch341_private *priv;
> -
> - priv = usb_get_serial_port_data(serial->port[0]);
> + struct usb_serial_port *port = serial->port[0];
> + struct ch341_private *priv = usb_get_serial_port_data(port);
> + int ret;
>
> /* reconfigure ch341 serial port after bus-reset */
> ch341_configure(serial->dev, priv);
>
> - return 0;
> + if (tty_port_initialized(&port->port)) {
Note that this needs to be
if (test_bit(ASYNCB_INITIALIZED, &port->port.flags))
prior to commit d41861ca19c9 ("tty: Replace ASYNC_INITIALIZED bit and
update atomically") that went into 4.7.
I'll send a backport.
Johan
next prev parent reply other threads:[~2017-01-17 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 13:04 Patch "USB: serial: ch341: fix resume after reset" has been added to the 4.4-stable tree gregkh
2017-01-17 14:22 ` Johan Hovold [this message]
2017-01-17 15:16 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2017-01-17 16:11 gregkh
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=20170117142205.GB4040@localhost \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=stable-commits@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).