Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: Stefan Wahren <wahrenst@gmx.net>
To: Fabio Estevam <festevam@gmail.com>, gregkh@linuxfoundation.org
Cc: shawnguo@kernel.org, kernel@pengutronix.de,
	tomasz.mon@camlingroup.com, linux-serial@vger.kernel.org,
	imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] serial: imx: Restore original RXTL for console to fix data loss
Date: Fri, 20 Jun 2025 11:05:07 +0200	[thread overview]
Message-ID: <cb757d69-2e14-4b8b-9db4-5f3362be37dc@gmx.net> (raw)
In-Reply-To: <20250619114617.2791939-1-festevam@gmail.com>

Am 19.06.25 um 13:46 schrieb Fabio Estevam:
> Commit 7a637784d517 ("serial: imx: reduce RX interrupt frequency")
> introduced a regression on the i.MX6UL EVK board. The issue can be
> reproduced with the following steps:
>
> - Open vi on the board.
> - Paste a text file (~150 characters).
> - Save the file, then repeat the process.
> - Compare the sha256sum of the saved files.
>
> The checksums do not match due to missing characters or entire lines.
>
> Fix this by restoring the RXTL value to 1 when the UART is used as a
> console.
>
> This ensures timely RX interrupts and reliable data reception in console
> mode.
>
> With this change, pasted content is saved correctly, and checksums are
> always consistent.
>
> Cc: stable@vger.kernel.org
> Fixes: 7a637784d517 ("serial: imx: reduce RX interrupt frequency")
> Signed-off-by: Fabio Estevam <festevam@gmail.com>
>
Reviewed-by: Stefan Wahren <wahrenst@gmx.net>

Thanks

      reply	other threads:[~2025-06-20  9:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19 11:46 [PATCH] serial: imx: Restore original RXTL for console to fix data loss Fabio Estevam
2025-06-20  9:05 ` Stefan Wahren [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=cb757d69-2e14-4b8b-9db4-5f3362be37dc@gmx.net \
    --to=wahrenst@gmx.net \
    --cc=festevam@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tomasz.mon@camlingroup.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