From: Ferry Toth <fntoth@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"John Ogness" <john.ogness@linutronix.de>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Crescent Hsieh" <crescentcy.hsieh@moxa.com>,
"Hugo Villeneuve" <hvilleneuve@dimonoff.com>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
"Jiri Slaby" <jirislaby@kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH v1 1/1] Revert "serial: 8250_port: Drop duplicate NULL check"
Date: Sun, 11 Oct 2026 21:28:41 +0200 [thread overview]
Message-ID: <2fe443ce-2d3e-4a1d-aaf0-0aef68da4cf0@gmail.com> (raw)
In-Reply-To: <2026101151-regroup-caterer-b92d@gregkh>
Hi
Op 11-10-2026 om 07:35 schreef Greg Kroah-Hartman:
> On Sat, Oct 10, 2026 at 09:37:56PM +0200, Ferry Toth wrote:
>> This reverts commit 7885af04df6e4efd72910200c1bfc079d61202e4.
>>
>> Commit 7885af04df6e ("serial: 8250_port: Drop duplicate NULL check")
>> added `up->dma = NULL;` to serial8250_release_dma(), with the stated
>> intent of making sure DMA would not be used again after release.
>>
>> However, up->dma is assigned once at probe time. serial8250_do_startup()
>> only calls serial8250_request_dma() when up->dma is non-NULL, so after
>> the first close the pointer stays NULL and DMA is never re-acquired.
>>
>> On Intel Tangier (Edison) with HSU DMA this causes a regression: the
>> first port open uses TX DMA, the second and later opens transmit in PIO
>> mode, producing 64-byte FIFO bursts with ~50us gaps between them.
> Ugh, sorry about missing that. I'll queue this up when I get a chance
> in the next few days, thanks for posting it.
>
> greg k-h
No worries, sorry I found it this late. I have been behind testing
kernels and only now trying to catch up.
Ferry
prev parent reply other threads:[~2026-10-11 19:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 19:37 Ferry Toth
2026-10-11 5:35 ` Greg Kroah-Hartman
2026-10-11 19:28 ` Ferry Toth [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=2fe443ce-2d3e-4a1d-aaf0-0aef68da4cf0@gmail.com \
--to=fntoth@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=crescentcy.hsieh@moxa.com \
--cc=gregkh@linuxfoundation.org \
--cc=hvilleneuve@dimonoff.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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
all inboxes | Powered by JetHome®