Linux Serial subsystem development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Ferry Toth" <ftoth@exalondelft.nl>
Cc: linux-serial@vger.kernel.org
Subject: Re: [PATCH v1 1/1] Revert "serial: 8250_port: Drop duplicate NULL check"
Date: Sat, 10 Oct 2026 19:49:13 +0000	[thread overview]
Message-ID: <sashiko-outbox-166854@kernel.org> (raw)
In-Reply-To: <20261010193755.187706-2-ftoth@exalondelft.nl>

> 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.
> 
> Fixes: 7885af04df6e ("serial: 8250_port: Drop duplicate NULL check")
> Cc: stable@vger.kernel.org
> Signed-off-by: Ferry Toth <ftoth@exalondelft.nl>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261010193755.187706-2-ftoth@exalondelft.nl?part=1


  reply	other threads:[~2026-10-10 19:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-10 19:37 [PATCH v1 1/1] Revert "serial: 8250_port: Drop duplicate NULL check" Ferry Toth
2026-10-10 19:49 ` sashiko-bot [this message]
2026-10-11  5:35 ` Greg Kroah-Hartman
2026-10-11 19:28   ` Ferry Toth
2026-10-12 20:28 ` Andy Shevchenko

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=sashiko-outbox-166854@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=ftoth@exalondelft.nl \
    --cc=linux-serial@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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