From: Greg KH <gregkh@linuxfoundation.org>
To: Johan Hovold <johan@kernel.org>
Cc: linux-usb@vger.kernel.org, "Jaromír Škorpil" <Jerry@jrr.cz>
Subject: Re: [PATCH 0/5] USB: serial: cp210x: add support for line-status events
Date: Mon, 13 Jul 2020 15:41:29 +0200 [thread overview]
Message-ID: <20200713134129.GA3175228@kroah.com> (raw)
In-Reply-To: <20200713105517.27796-1-johan@kernel.org>
On Mon, Jul 13, 2020 at 12:55:12PM +0200, Johan Hovold wrote:
> This series add supports for line-status events that specifically can be
> used to detect parity errors.
>
> The implementation relies on the device's event-insertion mode, which
> can also be used to detect line-breaks and modem status changes. But as
> this doesn't seem to work as expected on CP2102, support has been left
> unimplemented for now.
>
> Included are also a couple of cleanups.
>
> Johan
>
> Changes since RFC [1]:
> - drop sysrq support which relies on break detection
> - use 0xec (instead of 0xff) as escape character
>
> [1] https://lore.kernel.org/r/20200703150104.GE3453@localhost
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2020-07-13 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 10:55 [PATCH 0/5] USB: serial: cp210x: add support for line-status events Johan Hovold
2020-07-13 10:55 ` [PATCH 1/5] USB: serial: cp210x: disable interface on errors in open Johan Hovold
2020-07-13 10:55 ` [PATCH 2/5] USB: serial: cp210x: add support for line-status events Johan Hovold
2020-07-13 10:55 ` [PATCH 3/5] USB: serial: cp210x: add support for TIOCGICOUNT Johan Hovold
2020-07-13 10:55 ` [PATCH 4/5] USB: serial: cp210x: drop unnecessary packed attributes Johan Hovold
2020-07-13 10:55 ` [PATCH 5/5] USB: serial: cp210x: use in-kernel types in port data Johan Hovold
2020-07-13 13:41 ` Greg KH [this message]
2020-07-14 9:55 ` [PATCH 0/5] USB: serial: cp210x: add support for line-status events 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=20200713134129.GA3175228@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Jerry@jrr.cz \
--cc=johan@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;
as well as URLs for NNTP newsgroup(s).