mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: "Viresh Kumar" <vireshk@kernel.org>,
	"Vinod Koul" <vkoul@kernel.org>, "Frank Li" <Frank.Li@kernel.org>,
	"Dan Williams" <djbw@kernel.org>,
	"Serge Semin" <fancer.lancer@gmail.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Jiri Slaby" <jirislaby@kernel.org>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	dmaengine@vger.kernel.org, linux-serial@vger.kernel.org,
	linux-kernel@vger.kernel.org, Sashiko <sashiko-bot@kernel.org>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	stable@vger.kernel.org, "Frank Li" <Frank.Li@nxp.com>
Subject: Re: [PATCH v7 00/10] dmaengine: dw: serialize completion and termination
Date: Mon, 16 Nov 2026 11:04:56 +0200	[thread overview]
Message-ID: <avrHOJ-fVZOO32bI@ashevche-desk.local> (raw)
In-Reply-To: <20261115-submit-dw-dma-synchronize-v1-v7-0-8d58f3d49e4d@gmail.com>

On Sun, Nov 15, 2026 at 12:19:33AM -0700, James Hilliard wrote:
> Keep client callbacks in the controller tasklet while preserving polled
> completion. Serialize descriptor ownership across completion, error
> recovery and termination, and wait for callbacks before a client reuses
> its resources.
> 
> The series first serializes completion, error recovery and cookie
> accounting with termination. Separate patches extract hardware-LLP
> residue calculation, calculate it in the status getter, simplify completion
> handling and report queued residue. Channel release and
> device_synchronize then gain tasklet draining before the final patch
> adds deferred notifications and shared completed-descriptor cleanup.
> 
> The series adapts Serge Semin's channel-restart and callback fixes [0-2].
> Polling continues to advance cookies and software-LLP blocks, while client
> notifications run from the controller tasklet. Synchronization preserves
> pending tasklet runs from other channels.
> 
> Based on dmaengine/fixes at 6628e7d4c6b2.

Most of the patches refer to Fixes tag as an initial commit 3bfb1d20b547.
But some are not. I think the Fixes tag(s) in many patches in this series
is (are) broken and/or incomplete.

Another question, wouldn't move this driver to use virt-dma infra be helpful
to begin with?

-- 
With Best Regards,
Andy Shevchenko



      parent reply	other threads:[~2026-11-16  9:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-15  7:19 James Hilliard
2026-11-15  7:19 ` [PATCH v7 01/10] dmaengine: dw: Fix XFER bit set, but channel not idle error James Hilliard
2026-11-15  7:19 ` [PATCH v7 02/10] dmaengine: dw: serialize error recovery with channel termination James Hilliard
2026-11-15  7:19 ` [PATCH v7 03/10] dmaengine: dw: complete cookies before releasing the channel lock James Hilliard
2026-11-15  7:19 ` [PATCH v7 04/10] dmaengine: dw: extract hardware-LLP residue calculation James Hilliard
2026-11-15  7:19 ` [PATCH v7 05/10] dmaengine: dw: calculate residue in the status getter James Hilliard
2026-11-15  7:19 ` [PATCH v7 06/10] dmaengine: dw: simplify transfer-complete handling James Hilliard
2026-11-15  7:19 ` [PATCH v7 07/10] dmaengine: dw: report residue for queued transfers James Hilliard
2026-11-15  7:19 ` [PATCH v7 08/10] dmaengine: dw: drain the tasklet before releasing channel resources James Hilliard
2026-11-15  7:19 ` [PATCH v7 09/10] dmaengine: dw: synchronize completion callbacks James Hilliard
2026-11-15  7:19 ` [PATCH v7 10/10] dmaengine: dw: Prevent tx-status calling DMA-desc callback James Hilliard
2026-11-16  9:04 ` Andy Shevchenko [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=avrHOJ-fVZOO32bI@ashevche-desk.local \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=Frank.Li@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=djbw@kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=fancer.lancer@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=james.hilliard1@gmail.com \
    --cc=jirislaby@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=sashiko-bot@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=vireshk@kernel.org \
    --cc=vkoul@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®