From: fengchengwen <fengchengwen@huawei.com>
To: Gagandeep Singh <g.singh@nxp.com>, <dev@dpdk.org>
Cc: <hemant.agrawal@nxp.com>, Prashant Gupta <prashant.gupta_3@nxp.com>
Subject: Re: [PATCH v4 5/5] dma/imx_edma5: add statistics and dump
Date: Sat, 10 Oct 2026 15:26:54 +0800 [thread overview]
Message-ID: <afcff76f-b776-4a5f-a405-80cae31d4e3e@huawei.com> (raw)
In-Reply-To: <20260812092929.563973-6-g.singh@nxp.com>
Acked-by: Chengwen Feng <fengchengwen@huawei.com>
On 8/12/2026 5:29 PM, Gagandeep Singh wrote:
> Add per-vchan statistics, virtual channel status reporting and a device
> dump callback to the eDMA5 dmadev.
>
> stats_get and stats_reset expose the submitted, completed and error
> counters maintained by the data path, supporting both a single vchan and
> the RTE_DMA_ALL_VCHAN aggregate. vchan_status reports whether a channel is
> idle, active or halted on an unreaped error by inspecting the outstanding
> jobs in the software ring. dev_dump prints the device and per-vchan
> software state to aid debugging.
>
> Signed-off-by: Gagandeep Singh <g.singh@nxp.com>
> Signed-off-by: Prashant Gupta <prashant.gupta_3@nxp.com>
...
next prev parent reply other threads:[~2026-10-10 7:27 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 8:42 [PATCH 0/4] dma/imx_edma5: introduce NXP i.MX95 eDMA5 driver Gagandeep Singh
2026-08-06 8:42 ` [PATCH 1/4] dma/imx_edma5: introduce eDMA5 dmadev skeleton Gagandeep Singh
2026-08-06 8:42 ` [PATCH 2/4] dma/imx_edma5: add device configuration Gagandeep Singh
2026-08-06 8:42 ` [PATCH 3/4] dma/imx_edma5: add data path Gagandeep Singh
2026-08-06 8:42 ` [PATCH 4/4] dma/imx_edma5: add statistics and dump Gagandeep Singh
2026-08-06 16:21 ` Stephen Hemminger
2026-08-07 7:05 ` Gagandeep Singh
2026-08-06 17:11 ` [PATCH 0/4] dma/imx_edma5: introduce NXP i.MX95 eDMA5 driver Stephen Hemminger
2026-08-07 6:54 ` Gagandeep Singh
2026-08-07 6:48 ` [PATCH v2 0/5] " Gagandeep Singh
2026-08-07 6:48 ` [PATCH v2 1/5] bus/platform: match device by devicetree compatible string Gagandeep Singh
2026-08-07 6:48 ` [PATCH v2 2/5] dma/imx_edma5: introduce eDMA5 dmadev skeleton Gagandeep Singh
2026-08-07 6:48 ` [PATCH v2 3/5] dma/imx_edma5: add device configuration Gagandeep Singh
2026-08-07 6:48 ` [PATCH v2 4/5] dma/imx_edma5: add data path Gagandeep Singh
2026-08-07 6:48 ` [PATCH v2 5/5] dma/imx_edma5: add statistics and dump Gagandeep Singh
2026-08-10 15:37 ` [PATCH v2 0/5] dma/imx_edma5: introduce NXP i.MX95 eDMA5 driver Stephen Hemminger
2026-08-11 10:49 ` [PATCH v3 " Gagandeep Singh
2026-08-11 10:49 ` [PATCH v3 1/5] bus/platform: match device by devicetree compatible string Gagandeep Singh
2026-08-11 10:49 ` [PATCH v3 2/5] dma/imx_edma5: introduce eDMA5 dmadev skeleton Gagandeep Singh
2026-08-11 10:49 ` [PATCH v3 3/5] dma/imx_edma5: add device configuration Gagandeep Singh
2026-08-11 10:49 ` [PATCH v3 4/5] dma/imx_edma5: add data path Gagandeep Singh
2026-08-11 10:49 ` [PATCH v3 5/5] dma/imx_edma5: add statistics and dump Gagandeep Singh
2026-08-11 17:00 ` [PATCH v3 0/5] dma/imx_edma5: introduce NXP i.MX95 eDMA5 driver Stephen Hemminger
2026-08-12 9:29 ` [PATCH v4 " Gagandeep Singh
2026-08-12 9:29 ` [PATCH v4 1/5] bus/platform: match device by devicetree compatible string Gagandeep Singh
2026-10-08 17:24 ` David Marchand
2026-10-09 7:31 ` David Marchand
2026-10-13 10:12 ` David Marchand
2026-10-10 9:29 ` fengchengwen
2026-08-12 9:29 ` [PATCH v4 2/5] dma/imx_edma5: introduce eDMA5 dmadev skeleton Gagandeep Singh
2026-10-10 6:45 ` fengchengwen
2026-08-12 9:29 ` [PATCH v4 3/5] dma/imx_edma5: add device configuration Gagandeep Singh
2026-10-10 7:01 ` fengchengwen
2026-08-12 9:29 ` [PATCH v4 4/5] dma/imx_edma5: add data path Gagandeep Singh
2026-10-10 7:24 ` fengchengwen
2026-08-12 9:29 ` [PATCH v4 5/5] dma/imx_edma5: add statistics and dump Gagandeep Singh
2026-10-10 7:26 ` fengchengwen [this message]
2026-10-08 17:27 ` [PATCH v4 0/5] dma/imx_edma5: introduce NXP i.MX95 eDMA5 driver David Marchand
2026-10-10 9:31 ` fengchengwen
2026-10-13 6:51 ` [PATCH v5 " Gagandeep Singh
2026-10-13 6:51 ` [PATCH v5 1/5] bus/platform: match device by devicetree compatible string Gagandeep Singh
2026-10-13 6:51 ` [PATCH v5 2/5] dma/imx_edma5: introduce eDMA5 dmadev skeleton Gagandeep Singh
2026-10-13 6:51 ` [PATCH v5 3/5] dma/imx_edma5: add device configuration Gagandeep Singh
2026-10-13 6:51 ` [PATCH v5 4/5] dma/imx_edma5: add data path Gagandeep Singh
2026-10-13 6:51 ` [PATCH v5 5/5] dma/imx_edma5: add statistics and dump Gagandeep Singh
2026-10-14 3:57 ` [PATCH v6 0/5] dma/imx_edma5: introduce NXP i.MX95 eDMA5 driver Gagandeep Singh
2026-10-14 3:57 ` [PATCH v6 1/5] bus/platform: match device by devicetree compatible string Gagandeep Singh
2026-10-14 3:57 ` [PATCH v6 2/5] dma/imx_edma5: introduce eDMA5 dmadev skeleton Gagandeep Singh
2026-10-14 3:57 ` [PATCH v6 3/5] dma/imx_edma5: add device configuration Gagandeep Singh
2026-10-14 3:57 ` [PATCH v6 4/5] dma/imx_edma5: add data path Gagandeep Singh
2026-10-14 3:57 ` [PATCH v6 5/5] dma/imx_edma5: add statistics and dump Gagandeep Singh
2026-10-14 7:28 ` [PATCH v6 0/5] dma/imx_edma5: introduce NXP i.MX95 eDMA5 driver David Marchand
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=afcff76f-b776-4a5f-a405-80cae31d4e3e@huawei.com \
--to=fengchengwen@huawei.com \
--cc=dev@dpdk.org \
--cc=g.singh@nxp.com \
--cc=hemant.agrawal@nxp.com \
--cc=prashant.gupta_3@nxp.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