From: Johan Hovold <johan@kernel.org>
To: Mathieu OTHACEHE <m.othacehe@gmail.com>
Cc: johan@kernel.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH 2/3] USB: mxu11x0: clean device control commands
Date: Sun, 3 Jan 2016 17:33:13 +0100 [thread overview]
Message-ID: <20160103163313.GE25304@localhost> (raw)
In-Reply-To: <1451831161-26792-3-git-send-email-m.othacehe@gmail.com>
On Sun, Jan 03, 2016 at 03:26:00PM +0100, Mathieu OTHACEHE wrote:
> Sending OPEN and START commands twice is not necessary for this driver.
> Also send STOP command at close.
>
> Signed-off-by: Mathieu OTHACEHE <m.othacehe@gmail.com>
> ---
> drivers/usb/serial/mxu11x0.c | 31 +++++++------------------------
> 1 file changed, 7 insertions(+), 24 deletions(-)
>
> diff --git a/drivers/usb/serial/mxu11x0.c b/drivers/usb/serial/mxu11x0.c
> index 0fe7eab..354fcb5 100644
> --- a/drivers/usb/serial/mxu11x0.c
> +++ b/drivers/usb/serial/mxu11x0.c
> @@ -823,30 +823,6 @@ static int mxu1_open(struct tty_struct *tty, struct usb_serial_port *port)
> goto unlink_int_urb;
> }
>
> - /*
> - * reset the data toggle on the bulk endpoints to work around bug in
> - * host controllers where things get out of sync some times
> - */
> - usb_clear_halt(serial->dev, port->write_urb->pipe);
> - usb_clear_halt(serial->dev, port->read_urb->pipe);
This is an unrelated change. You can remove it, but then do so in a
separate patch.
> -
> - if (tty)
> - mxu1_set_termios(tty, port, NULL);
But you should definitely not be removing this.
> -
> - status = mxu1_send_ctrl_urb(serial, MXU1_OPEN_PORT,
> - open_settings, MXU1_UART1_PORT);
> - if (status) {
> - dev_err(&port->dev, "cannot send open command: %d\n", status);
> - goto unlink_int_urb;
> - }
> -
> - status = mxu1_send_ctrl_urb(serial, MXU1_START_PORT,
> - 0, MXU1_UART1_PORT);
> - if (status) {
> - dev_err(&port->dev, "cannot send start command: %d\n", status);
> - goto unlink_int_urb;
> - }
> -
Also did you not say that your sniffed traffic showed the following
sequence OPEN, CONFIG (e.g. purge, set_termios), START?
Johan
next prev parent reply other threads:[~2016-01-03 16:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-03 14:25 [PATCH 0/3] USB: mxu11x0: fixes and follow ups Mathieu OTHACEHE
2016-01-03 14:25 ` [PATCH 1/3] USB: mxu11x0: fix memory leak on usb_serial private data Mathieu OTHACEHE
2016-01-03 16:27 ` Johan Hovold
2016-01-03 14:26 ` [PATCH 2/3] USB: mxu11x0: clean device control commands Mathieu OTHACEHE
2016-01-03 16:33 ` Johan Hovold [this message]
2016-01-03 14:26 ` [PATCH 3/3] USB: mxu11x0: move firmware download and endpoint testing to probe callback Mathieu OTHACEHE
2016-01-03 16:45 ` Johan Hovold
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=20160103163313.GE25304@localhost \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.othacehe@gmail.com \
/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.