From: Frank Li <Frank.Li@nxp.com>
To: arnd@arndb.de, vkoul@kernel.org
Cc: Frank.Li@nxp.com, bhe@redhat.com, dmaengine@vger.kernel.org,
gregkh@linuxfoundation.org, imx@lists.linux.dev,
linux-kernel@vger.kernel.org, lkp@intel.com,
oe-kbuild-all@lists.linux.dev, rafael@kernel.org
Subject: [PATCH v5 0/3] dmaengine: fsl_edma: add trace and debugfs support
Date: Mon, 2 Oct 2023 14:37:47 -0400 [thread overview]
Message-ID: <20231002183750.552759-1-Frank.Li@nxp.com> (raw)
Change from v3 to v5
- There are still some discussion about 64bit register access.
Drop 64 register support and use sperate patch to enable 64bit register
support in future.
Change from v3 to v4
- Fix build warning
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202309210500.owiirl4c-lkp@intel.com/
Change from v2 to v3
- Fixed sparse build warning
- improve debugfs_create_regset32 and use debugfs_create_regset() to dump
all registers
Change from v1 to v2
- Fixed tcd trace issue, data need be saved firstly.
=== Trace ===
echo 1 >/sys/kernel/debug/tracing/tracing_on
echo 1 >/sys/kernel/debug/tracing/events/fsl_edma/enable
Run any dma test
...
cat /sys/kernel/debug/tracing/trace
uart_testapp_11-448 [000] d..1. 69.185019: edma_fill_tcd:
==== TCD =====
saddr: 0x831ee020
soff: 0x8000
attr: 0xffff
nbytes: 0xfba40000
slast: 0x00000000
daddr: 0x8aaa4800
doff: 0x0001
citer: 0x0800
dlast: 0xfba40020
csr: 0x0052
biter: 0x0800
uart_testapp_11-448 [000] d..2. 69.185022: edma_writew: offset 0001803c: value 00000000
uart_testapp_11-448 [000] d..2. 69.185023: edma_writel: offset 00018020: value 4259001c
uart_testapp_11-448 [000] d..2. 69.185024: edma_writel: offset 00018030: value 8aaa4000
=== DebugFS ===
cat /sys/kernel/debug/dmaengine/42000000.dma-controller/42000000.dma-controller-CH00/ch_sbr
0x00208003
Frank Li (3):
debugfs_create_regset32() support 8/16 bit width registers
dmaengine: fsl-emda: add debugfs support
dmaengine: fsl-edma: add trace event support
drivers/dma/Makefile | 7 +-
drivers/dma/fsl-edma-common.c | 2 +
drivers/dma/fsl-edma-common.h | 37 +++++-
drivers/dma/fsl-edma-debugfs.c | 200 +++++++++++++++++++++++++++++++++
drivers/dma/fsl-edma-main.c | 2 +
drivers/dma/fsl-edma-trace.c | 4 +
drivers/dma/fsl-edma-trace.h | 134 ++++++++++++++++++++++
fs/debugfs/file.c | 53 ++++++---
include/linux/debugfs.h | 17 ++-
9 files changed, 428 insertions(+), 28 deletions(-)
create mode 100644 drivers/dma/fsl-edma-debugfs.c
create mode 100644 drivers/dma/fsl-edma-trace.c
create mode 100644 drivers/dma/fsl-edma-trace.h
--
2.34.1
next reply other threads:[~2023-10-02 18:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 18:37 Frank Li [this message]
2023-10-02 18:37 ` [PATCH v5 1/3] debugfs_create_regset32() support 8/16 bit width registers Frank Li
2023-10-02 18:55 ` Arnd Bergmann
2023-10-02 19:07 ` Frank Li
2023-10-02 19:39 ` Arnd Bergmann
2023-10-02 18:37 ` [PATCH v5 2/3] dmaengine: fsl-emda: add debugfs support Frank Li
2023-10-02 18:37 ` [PATCH v5 3/3] dmaengine: fsl-edma: add trace event support Frank Li
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=20231002183750.552759-1-Frank.Li@nxp.com \
--to=frank.li@nxp.com \
--cc=arnd@arndb.de \
--cc=bhe@redhat.com \
--cc=dmaengine@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rafael@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