mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Frank Li <Frank.li@nxp.com>, Sheetal <sheetal@nvidia.com>
Cc: Vinod Koul <vkoul@kernel.org>,
	Laxman Dewangan <ldewangan@nvidia.com>,
	Frank Li <Frank.Li@kernel.org>,
	Thierry Reding <thierry.reding@kernel.org>,
	Sameer Pujar <spujar@nvidia.com>,
	Mohan Kumar <mkumard@nvidia.com>,
	dmaengine@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6] dmaengine: tegra210-adma: Add error logging on failure paths
Date: Mon, 8 Jun 2026 11:29:03 +0100	[thread overview]
Message-ID: <65416413-d307-417b-91ce-51d6357552d2@nvidia.com> (raw)
In-Reply-To: <agOInxpOCTgX7dwi@lizhi-Precision-Tower-5810>


On 12/05/2026 21:07, Frank Li wrote:
> On Tue, May 12, 2026 at 09:25:08AM +0000, Sheetal wrote:
>> Add dev_err/dev_err_probe logging across failure paths to improve
>> debuggability of DMA errors during runtime and probe.
>>
>> Use return dev_err_probe() pattern consistently in the probe function,
>> and dev_err in non-probe functions. Also convert existing dev_err calls
>> in probe to dev_err_probe for consistency.
>>
>> As part of the probe-path cleanup, use dmaenginem_async_device_register()
>> and devm_pm_runtime_enable(), and add tegra_adma_irq_dispose() for managed
>> IRQ mapping cleanup. These managed helpers remove the probe error unwind
>> labels while keeping the remove path minimal.
>>
>> Signed-off-by: Sheetal <sheetal@nvidia.com>
>> ---
> 
> Reviewed-by: Frank Li <Frank.Li@nxp.com>


Reviewed-by: Jon Hunter <jonathanh@nvidia.com>

Thanks!
Jon

-- 
nvpublic


      reply	other threads:[~2026-06-08 10:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12  9:25 Sheetal
2026-05-12 20:07 ` Frank Li
2026-06-08 10:29   ` Jon Hunter [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=65416413-d307-417b-91ce-51d6357552d2@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=Frank.Li@kernel.org \
    --cc=Frank.li@nxp.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=ldewangan@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mkumard@nvidia.com \
    --cc=sheetal@nvidia.com \
    --cc=spujar@nvidia.com \
    --cc=thierry.reding@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®