From: Michael Walle <michael@walle.cc>
To: Sherry Sun <sherry.sun@nxp.com>
Cc: gregkh@linuxfoundation.org, jirislaby@kernel.org,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-imx@nxp.com
Subject: Re: [PATCH 1/2] tty: serial: fsl_lpuart: correct the count of break characters
Date: Fri, 15 Jul 2022 14:33:46 +0200 [thread overview]
Message-ID: <71eee711668a0a17a7f5a44096f2c398@walle.cc> (raw)
In-Reply-To: <20220715025944.11076-2-sherry.sun@nxp.com>
Am 2022-07-15 04:59, schrieb Sherry Sun:
> The LPUART can't distinguish between a break signal and a framing
> error,
> so need to count the break characters if there is a framing error and
> received data is zero instead of the parity error.
>
> Fixes: 5541a9bacfe5 ("serial: fsl_lpuart: handle break and make sysrq
> work")
> Signed-off-by: Sherry Sun <sherry.sun@nxp.com>
Reviewed-by: Michael Walle <michael@walle.cc>
-michael
next prev parent reply other threads:[~2022-07-15 12:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 2:59 [PATCH 0/2] fsl_lpuart: fix the bugs in received break signal count and send break signal Sherry Sun
2022-07-15 2:59 ` [PATCH 1/2] tty: serial: fsl_lpuart: correct the count of break characters Sherry Sun
2022-07-15 6:58 ` Michael Walle
2022-07-15 7:22 ` Sherry Sun
2022-07-15 12:33 ` Michael Walle [this message]
2022-07-15 2:59 ` [PATCH 2/2] tty: serial: fsl_lpuart: writing a 1 and then a 0 to trigger a break character Sherry Sun
2022-07-15 6:47 ` Michael Walle
2022-07-15 7:20 ` Sherry Sun
2022-07-15 7:42 ` Michael Walle
2022-07-15 9:18 ` Sherry Sun
2022-07-15 11:52 ` Michael Walle
2022-07-18 7:02 ` Jiri Slaby
2022-07-22 9:41 ` Sherry Sun
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=71eee711668a0a17a7f5a44096f2c398@walle.cc \
--to=michael@walle.cc \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=sherry.sun@nxp.com \
/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