From: Greg KH <gregkh@linuxfoundation.org>
To: Hugo Villeneuve <hugo@hugovil.com>
Cc: stable@vger.kernel.org
Subject: Re: serial: sc16is7xx: improve regmap debugfs by using one regmap per port
Date: Fri, 26 Jan 2024 15:49:04 -0800 [thread overview]
Message-ID: <2024012643-resume-pounce-39e6@gregkh> (raw)
In-Reply-To: <20240123122957.9a88fb7839ae745975af6883@hugovil.com>
On Tue, Jan 23, 2024 at 12:29:57PM -0500, Hugo Villeneuve wrote:
> Hi,
> I would like the following patch to be applied to the stable
> kernel 6.6:
>
> 3837a0379533 serial: sc16is7xx: improve regmap debugfs by using one
> regmap per port
>
> As noted in
> https://lore.kernel.org/all/20231211171353.2901416-1-hugo@hugovil.com/raw :
> ---------------------
> I did not originally add a "Cc: stable" tag for the above mentioned
> commit, as it was intended only to improve debugging using debugfs. But
> since then, I have been able to confirm that it also fixes a long
> standing bug in our system where the Tx interrupt are no longer enabled
> at some point when transmitting large RS-485 paquets that completely
> fill the FIFO and thus require multiple and subsequent writes to the
> FIFO once space in it becomes available. I have been investigating why,
> but so far I haven't found the exact cause, altough I suspect it has
> something to do with regmap caching...
> ---------------------
>
> It applies cleanly and was tested on this kernel using a
> custom board with a Variscite IMX8MN NANO SOM, a NewHaven LCD, and two
> SC16IS752 on a SPI bus. The four UARTs are using RS-485 mode.
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2024-01-26 23:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 17:29 serial: sc16is7xx: improve regmap debugfs by using one regmap per port Hugo Villeneuve
2024-01-26 23:49 ` Greg KH [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=2024012643-resume-pounce-39e6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=hugo@hugovil.com \
--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