All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Konstantin Shkolnyy <konstantin.shkolnyy@gmail.com>
Cc: johan@kernel.org, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 3/3] USB: serial: cp210x: Workaround cp2108 GET_LINE_CTL bug
Date: Thu, 29 Oct 2015 08:19:23 +0100	[thread overview]
Message-ID: <20151029071923.GD32753@localhost> (raw)
In-Reply-To: <20151028085126.GA28572@localhost>

On Wed, Oct 28, 2015 at 09:51:26AM +0100, Johan Hovold wrote:
> On Tue, Oct 27, 2015 at 04:53:34PM -0500, Konstantin Shkolnyy wrote:
> > cp2108 GET_LINE_CTL returns the 16-bit value with the 2 bytes swapped.
> > However, SET_LINE_CTL functions properly. When the driver tries to modify
> > the register, it reads it, modifies some bits and writes back. Because the
> > read bytes were swapped, this often results in an invalid value to be
> > written. In turn, this causes cp2108 respond with a stall. The stall
> > sometimes doesn't clear properly and cp2108 starts responding to following
> > valid commands also with stalls, effectively failing.
> > 
> > Signed-off-by: Konstantin Shkolnyy <konstantin.shkolnyy@gmail.com>

> I gave the series a really quick test on an cp2102-device I had lying
> around. I assume you verified the changes on some other older devices as
> well?

Did you test this series on the older device types as well?

Thanks,
Johan

  reply	other threads:[~2015-10-29  7:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-27 21:53 [PATCH v4 3/3] USB: serial: cp210x: Workaround cp2108 GET_LINE_CTL bug Konstantin Shkolnyy
2015-10-28  8:51 ` Johan Hovold
2015-10-29  7:19   ` Johan Hovold [this message]
2015-10-29 13:39     ` Konstantin Shkolnyy
2015-10-31 12:16       ` Johan Hovold
2015-10-31 14:54         ` Konstantin Shkolnyy
2015-11-03 13:26         ` Konstantin Shkolnyy
2015-11-03 13:33           ` 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=20151029071923.GD32753@localhost \
    --to=johan@kernel.org \
    --cc=konstantin.shkolnyy@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@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.