linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Jiri Slaby <jirislaby@kernel.org>
Cc: Jonathan Woithe <jwoithe@just42.net>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH 1/2] USB: serial: ch341: fix lost character on LCR updates
Date: Wed, 31 Aug 2022 10:43:47 +0200	[thread overview]
Message-ID: <Yw8fQz2amdKKYNvS@hovoldconsulting.com> (raw)
In-Reply-To: <863b4190-9b38-ed5a-0a18-74505702da21@kernel.org>

On Wed, Aug 31, 2022 at 10:36:18AM +0200, Jiri Slaby wrote:
> On 31. 08. 22, 10:15, Johan Hovold wrote:
> > Disable LCR updates for pre-0x30 devices which use a different (unknown)
> > protocol for line control and where the current register write causes
> > the next received character to be lost.
> > 
> > Note that updating LCR using the INIT command has no effect on these
> > devices either.
> > 
> > Reported-by: Jonathan Woithe <jwoithe@just42.net>
> > Link: https://lore.kernel.org/r/Ys1iPTfiZRWj2gXs@marvin.atrad.com.au
> > Fixes: 4e46c410e050 ("USB: serial: ch341: reinitialize chip on reconfiguration")
> > Fixes: 55fa15b5987d ("USB: serial: ch341: fix baud rate and line-control handling")
> > Cc: stable@vger.kernel.org      # 4.10
> > Signed-off-by: Johan Hovold <johan@kernel.org>
> > ---
> >   drivers/usb/serial/ch341.c | 10 +++++++++-
> >   1 file changed, 9 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/usb/serial/ch341.c b/drivers/usb/serial/ch341.c
> > index 2798fca71261..2bcce172355b 100644
> > --- a/drivers/usb/serial/ch341.c
> > +++ b/drivers/usb/serial/ch341.c
> > @@ -97,7 +97,10 @@ struct ch341_private {
> >   	u8 mcr;
> >   	u8 msr;
> >   	u8 lcr;
> > +
> >   	unsigned long quirks;
> > +	u8 version;
> 
> Could you move version above quirks? That would not create another 
> 7-byte padding in here. Actually it would not make ch341_private larger 
> on 64bit at all, if I am looking correctly.

No, I added it after quirks on purpose as it isn't protected by the
spinlock and doesn't change during runtime like the shadow registers.

And I really don't care about saving 8 bytes on 64-bit. :)

Johan

  reply	other threads:[~2022-08-31  8:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-31  8:15 [PATCH 0/2] USB: serial: ch341: fixes for older devices Johan Hovold
2022-08-31  8:15 ` [PATCH 1/2] USB: serial: ch341: fix lost character on LCR updates Johan Hovold
2022-08-31  8:36   ` Jiri Slaby
2022-08-31  8:43     ` Johan Hovold [this message]
2022-08-31  8:15 ` [PATCH 2/2] USB: serial: ch341: fix disabled rx timer on older devices Johan Hovold
2022-08-31 13:09 ` [PATCH 0/2] USB: serial: ch341: fixes for " Jonathan Woithe

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=Yw8fQz2amdKKYNvS@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=jirislaby@kernel.org \
    --cc=jwoithe@just42.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --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 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).