All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Johan Hovold <johan@kernel.org>, Jakub Nantl <jn@forever.cz>,
	Jonathan Olds <jontio@i4free.co.nz>,
	Michael Dreher <michael@5dot1.de>,
	linux-usb@vger.kernel.org, stable <stable@vger.kernel.org>
Subject: Re: [PATCH] USB: serial: ch341: fix receiver regression
Date: Mon, 10 Feb 2020 10:35:00 +0100	[thread overview]
Message-ID: <20200210093500.GA3539@localhost> (raw)
In-Reply-To: <20200206114546.GA3275679@kroah.com>

On Thu, Feb 06, 2020 at 11:45:46AM +0000, Greg Kroah-Hartman wrote:
> On Thu, Feb 06, 2020 at 12:18:19PM +0100, Johan Hovold wrote:
> > While assumed not to make a difference, not using the factor 2 prescaler
> > makes the receiver more susceptible to errors.
> > 
> > Specifically, there have been reports of problems with devices that
> > cannot generate a 115200 rate with a smaller error than 2.1% (e.g.
> > 117647 bps). But this can also be reproduced with a low-speed RS232
> > tranceiver at 115200 when the input rate is close to nominal.
> > 
> > So whenever possible, enable the factor 2 prescaler and halve the
> > divisor in order to use settings closer to that of the previous
> > algorithm.
> > 
> > Fixes: 35714565089e ("USB: serial: ch341: reimplement line-speed handling")
> > Cc: stable <stable@vger.kernel.org>	# 5.5
> > Reported-by: Jakub Nantl <jn@forever.cz>
> > Tested-by: Jakub Nantl <jn@forever.cz>
> > Signed-off-by: Johan Hovold <johan@kernel.org>
> 
> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Thanks for reviewing. Now applied.

Johan

      reply	other threads:[~2020-02-10  9:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06 11:18 [PATCH] USB: serial: ch341: fix receiver regression Johan Hovold
2020-02-06 11:45 ` Greg KH
2020-02-10  9:35   ` Johan Hovold [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=20200210093500.GA3539@localhost \
    --to=johan@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jn@forever.cz \
    --cc=jontio@i4free.co.nz \
    --cc=linux-usb@vger.kernel.org \
    --cc=michael@5dot1.de \
    --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 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.