From: Johan Hovold <johan@kernel.org>
To: Konstantin Shkolnyy <konstantin.shkolnyy@gmail.com>
Cc: Johan Hovold <johan@kernel.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] USB: serial: cp210x: Workaround for cp2108 failure due to GET_LINE_CTL bug
Date: Fri, 16 Oct 2015 17:40:58 +0200 [thread overview]
Message-ID: <20151016154058.GB32032@localhost> (raw)
In-Reply-To: <CAL_jEz_jBW3eJ-Hsq6xKFx6Mi-Z32q9PJxYp5NnJxMkRVDx8-Q@mail.gmail.com>
On Fri, Oct 16, 2015 at 10:39:13AM -0500, Konstantin Shkolnyy wrote:
> On Fri, Oct 16, 2015 at 10:27 AM, Johan Hovold <johan@kernel.org> wrote:
> > On Fri, Oct 16, 2015 at 10:11:12AM -0500, Konstantin Shkolnyy wrote:
> >> On Fri, Oct 16, 2015 at 8:27 AM, Johan Hovold <johan@kernel.org> wrote:
> >> > On Thu, Oct 15, 2015 at 06:23:31PM -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.
> >> >
> >> > That sounds weird. Are you saying that all or only some cp2108 devices
> >> > would be affected by this? And only for the line-control register?
> >>
> >> The bug exists in all current cp2108 devices and affects only
> >> GET_LINE_CTL. But it may be fixed in a future revision.
> >
> > Ok, have you some kind of confirmation from silabs on this already?
>
> I work for SiLabs.
Heh. :)
Johan
prev parent reply other threads:[~2015-10-16 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 23:23 [PATCH v2] USB: serial: cp210x: Workaround for cp2108 failure due to GET_LINE_CTL bug Konstantin Shkolnyy
2015-10-16 13:27 ` Johan Hovold
2015-10-16 15:11 ` Konstantin Shkolnyy
2015-10-16 15:27 ` Johan Hovold
2015-10-16 15:39 ` Konstantin Shkolnyy
2015-10-16 15:40 ` 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=20151016154058.GB32032@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox