DMA Engine development
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: rolanddreier@rivian.com
Cc: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>,
	Frank Li <Frank.Li@kernel.org>,
	dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] dmaengine: dw-axi-dmac: Fix LLP search, error reporting, and error dump
Date: Fri, 20 Nov 2026 15:04:19 +0530	[thread overview]
Message-ID: <awAUG_fO8eAkQq-c@parshuram> (raw)
In-Reply-To: <20261006-dw-axi-fixes-v1-0-3b319e456d93@rivian.com>

On 06-10-26, 01:03, Roland Dreier via B4 Relay wrote:
> One patch that build's on Jia Wang's fix for error-path LLI dump: the
> same bug is present in axi_chan_block_xfer_complete(), although it's
> not clear that it could ever be hit in practice, because the llp being
> searched for should always be found.
> 
> Then two fixes for failed transfer handling: one to report status in
> tx_result so that clients can know when a transfer hit an error, and
> another to make log messages more informative than "Bad descriptor
> submitted".

This fails for me against current code, please rebase on dmaengine/next

-- 
~Vinod

      parent reply	other threads:[~2026-11-20  9:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-06  1:03 [PATCH 0/3] dmaengine: dw-axi-dmac: Fix LLP search, error reporting, and error dump Roland Dreier via B4 Relay
2026-10-06  1:03 ` [PATCH 1/3] dmaengine: dw-axi-dmac: Bound the cyclic LLP search to the descriptor Roland Dreier via B4 Relay
2026-10-21 16:44   ` Frank Li
2026-10-06  1:03 ` [PATCH 2/3] dmaengine: dw-axi-dmac: Report failed transfers in the descriptor result Roland Dreier via B4 Relay
2026-10-06  1:19   ` sashiko-bot
2026-10-21 16:45   ` Frank Li
2026-10-06  1:03 ` [PATCH 3/3] dmaengine: dw-axi-dmac: Decode errors in the transfer failure log Roland Dreier via B4 Relay
2026-10-06  1:12   ` sashiko-bot
2026-10-21 16:49   ` Frank Li
2026-11-20  9:34 ` Vinod Koul [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=awAUG_fO8eAkQq-c@parshuram \
    --to=vkoul@kernel.org \
    --cc=Eugeniy.Paltsev@synopsys.com \
    --cc=Frank.Li@kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rolanddreier@rivian.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