stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Macpaul Lin <macpaul.lin@mediatek.com>
Cc: Johan Hovold <johan@kernel.org>, Oliver Neukum <oneukum@suse.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, stable@vger.kernel.org,
	Mediatek WSD Upstream <wsd_upstream@mediatek.com>
Subject: Re: [PATCH v3] cdc-acm: fix abnormal DATA RX issue for Mediatek Preloader.
Date: Tue, 18 Dec 2018 11:54:19 +0100	[thread overview]
Message-ID: <20181218105419.GL20658@localhost> (raw)
In-Reply-To: <1545129680-3224-1-git-send-email-macpaul.lin@mediatek.com>

On Tue, Dec 18, 2018 at 06:41:20PM +0800, Macpaul Lin wrote:
> Mediatek Preloader is a proprietary embedded boot loader for loading
> Little Kernel and Linux into device DRAM.
> 
> This boot loader also handle firmware update. Mediatek Preloader will be
> enumerated as a virtual COM port when the device is connected to Windows
> or Linux OS via CDC-ACM class driver. When the USB enumeration has been
> done, Mediatek Preloader will send out handshake command "READY" to PC
> actively instead of waiting command from the download tool.
> Since Linux 4.12, the commit "tty: reset termios state on device
> registration" (93857edd9829e144acb6c7e72d593f6e01aead66) causes Mediatek
> Preloader receiving some abnoraml command like "READYXX" as it sent.
> This will be recognized as an incorrect response. The behavior change
> also causes the download handshake fail.
> 
> By disabling the ECHO termios flag could avoid this problem. However, it
> cannot be done by user space configuration when download tool open
> /dev/ttyACM0. This is because the device running Mediatek Preloader will
> send handshake command "READY" immediately once the CDC-ACM driver is
> ready.
> 
> This patch wants to fix above problem by introducing "DISABLE_ECHO"
> property in driver_info. When Mediatek Preloader is connected, the
> CDC-ACM driver could disable ECHO flag in termios to avoid the problem.
> 
> Signed-off-by: Macpaul Lin <macpaul.lin@mediatek.com>
> ---
> Changes for v2:
>  - Move quirks testing of DISABLE_ECHO flag into acm_tty_install().
>  - Change quirks testing into bitwise comparison.
> Changes for v3:
>  - Replace clear flag operation from driver->init_termios to tty->termios.
>  - Remove parenthesis of ECHO flag.

Thanks for the update. Looks good, just some minor issues below.

>  drivers/usb/class/cdc-acm.c | 13 ++++++++++++-
>  drivers/usb/class/cdc-acm.h |  1 +
>  2 files changed, 13 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/usb/class/cdc-acm.c b/drivers/usb/class/cdc-acm.c
> index 1b68fed..c1b88c3 100644
> --- a/drivers/usb/class/cdc-acm.c
> +++ b/drivers/usb/class/cdc-acm.c
> @@ -571,6 +571,7 @@ static void acm_softint(struct work_struct *work)
>  static int acm_tty_install(struct tty_driver *driver, struct tty_struct *tty)
>  {
>  	struct acm *acm;
> +	unsigned long quirks;
>  	int retval;
>  
>  	acm = acm_get_by_minor(tty->index);
> @@ -583,6 +584,13 @@ static int acm_tty_install(struct tty_driver *driver, struct tty_struct *tty)
>  
>  	tty->driver_data = acm;
>  
> +	/* get normal quirks */
> +	quirks = acm->quirks;

I'd drop the quirks variable as you only need it once and acm->quirks is
pretty short to begin with.

> +
> +	/* handle active handshake triggered by device */

Please make this description more general; other devices may also end up
needing to suppress initial echoing.

> +	if (quirks & DISABLE_ECHO)
> +		tty->termios.c_lflag &= ~ECHO;

And finally, please move this just after installing the tty (i.e. before
setting tty->driver data).

> +
>  	return 0;

Thanks,
Johan

  reply	other threads:[~2018-12-18 10:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1544671676-23912-1-git-send-email-macpaul.lin@mediatek.com>
2018-12-18  5:00 ` [PATCH v2] cdc-acm: fix abnormal DATA RX issue for Mediatek Preloader Macpaul Lin
2018-12-18  9:02   ` Johan Hovold
2018-12-18 10:41 ` [PATCH v3] " Macpaul Lin
2018-12-18 10:54   ` Johan Hovold [this message]
2018-12-18 11:38 ` [PATCH v4] " Macpaul Lin
2018-12-18 11:44   ` Johan Hovold
2018-12-18 11:59 ` [PATCH v5] " Macpaul Lin
2018-12-18 12:38   ` Johan Hovold
2018-12-18 13:37     ` Oliver Neukum
2018-12-18 14:26       ` Macpaul Lin
2018-12-18 15:19         ` Macpaul Lin
2018-12-18 16:42           ` Lars Melin
2018-12-18 17:48             ` Macpaul Lin
2018-12-19  0:45               ` Lars Melin
2018-12-19  2:22               ` Macpaul Lin
2018-12-19  3:16                 ` Macpaul Lin
2018-12-19  3:31                   ` Lars Melin
2018-12-19  4:03                     ` Macpaul Lin
2018-12-19  8:56                       ` Oliver Neukum
2018-12-20 15:19                         ` Greg Kroah-Hartman
2018-12-18 15:37 ` [PATCH v6] " Macpaul Lin
2018-12-19  4:11 ` [PATCH v7] " Macpaul Lin
2018-12-19  9:00   ` Johan Hovold
2018-12-20 15:28     ` 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=20181218105419.GL20658@localhost \
    --to=johan@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=macpaul.lin@mediatek.com \
    --cc=oneukum@suse.com \
    --cc=stable@vger.kernel.org \
    --cc=wsd_upstream@mediatek.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 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).