public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Rahul Navale <rahulnavale04@gmail.com>
To: Folker Schwesinger <dev@folker-schwesinger.de>
Cc: Rahul Navale <rahul.navale@ifm.com>,
	dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, vkoul@kernel.org,
	Frank.Li@kernel.org, michal.simek@amd.com, suraj.gupta2@amd.com,
	thomas.gessler@brueckmann-gmbh.de, radhey.shyam.pandey@amd.com,
	tomi.valkeinen@ideasonboard.com, rahulnavale04@gmail.com,
	marex@nabladev.com, marex@denx.de
Subject: Re: [RFC PATCH] dmaengine: xilinx_dma: Fix per-channel direction reporting via device_caps
Date: Mon,  9 Mar 2026 12:58:21 +0530	[thread overview]
Message-ID: <20260309072822.5016-1-rahulnavale04@gmail.com> (raw)
In-Reply-To: <DGHGTCJRRZCW.9TGXQW44V6RR@folker-schwesinger.de>

From: Rahul Navale <rahul.navale@ifm.com>

>Please undo the latest Xilinx DMA patch I sent.
>To get some more data, could you apply the following patch (keep RFC
>patch and debug stuff) and rerun with 7e01511443c3 a) applied and b)
>reverted and post logs for both cases:

I have applied provided patch (with kept RFC patch and debug stuff) and with
7e01511443c3 applied. logs:

root@pdm3:~# dmesg | grep xilinx_dma_device_caps                                                                                                                                         
[    0.285057] xilinx_dma_device_caps: caps->directions = 0x00000001
[    0.285060] xilinx_dma_device_caps: caps->directions = 0x00000001
[    0.285759] xilinx_dma_device_caps: caps->directions = 0x00000002
[    0.285763] xilinx_dma_device_caps: caps->directions = 0x00000002
[    7.535143] xilinx_dma_device_caps: caps->directions = 0x00000001
[    7.535147] xilinx_dma_device_caps: caps->directions = 0x00000001
root@pdm3:~# dmesg | grep ptr_res
root@pdm3:~# aplay closetoyou.wav 
Playing WAVE 'closetoyou.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Stereo
^CAborted by signal Interrupt...
aplay: pcm_write:2178: write error: Interrupted system call
root@pdm3:~# 
root@pdm3:~# dmesg | grep ptr_res
[  198.997591] ptr_res: ptr = 0x00000000
[  199.002885] ptr_res: ptr = 0x00000000
[  199.002900] ptr_res: ptr = 0x00000000
[  199.002925] ptr_res: ptr = 0x00000000
[  199.002946] ptr_res: ptr = 0x00000000
[  199.117775] ptr_res: ptr = 0x00000000
[  199.117818] ptr_res: ptr = 0x00000000
[  199.117839] ptr_res: ptr = 0x00000000
[  199.242766] ptr_res: ptr = 0x00000000
[  199.242800] ptr_res: ptr = 0x00000000
[  199.242820] ptr_res: ptr = 0x00000000


Also I have applied provided patch (with kept RFC patch and debug stuff) and with
7e01511443c3 reverted. logs:

root@pdm3:~# dmesg | grep xilinx_dma_device_caps
root@pdm3:~# dmesg | grep ptr_res
root@pdm3:~# aplay closetoyou.wav 
Playing WAVE 'closetoyou.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Stereo
^CAborted by signal Interrupt...
aplay: pcm_write:2178: write error: Interrupted system call
root@pdm3:~# 
root@pdm3:~# dmesg | grep ptr_res
[   60.480754] ptr_res_no: ptr = 0x00000000
[   60.486058] ptr_res_no: ptr = 0x00000000
[   60.486070] ptr_res_no: ptr = 0x00000000
[   60.486094] ptr_res_no: ptr = 0x00000000
[   60.486113] ptr_res_no: ptr = 0x00000000
[   60.600877] ptr_res_no: ptr = 0x00001770
[   60.600920] ptr_res_no: ptr = 0x00001770
[   60.600939] ptr_res_no: ptr = 0x00001770
[   60.600948] ptr_res_no: ptr = 0x00001770
[   60.600968] ptr_res_no: ptr = 0x00001770
[   60.602739] ptr_res_no: ptr = 0x00001770
[   60.602750] ptr_res_no: ptr = 0x00001770
[   60.725869] ptr_res_no: ptr = 0x00002ee0
[   60.725904] ptr_res_no: ptr = 0x00002ee0
[   60.725921] ptr_res_no: ptr = 0x00002ee0
[   60.725931] ptr_res_no: ptr = 0x00002ee0
[   60.725949] ptr_res_no: ptr = 0x00002ee0
[   60.727667] ptr_res_no: ptr = 0x00002ee0
[   60.727677] ptr_res_no: ptr = 0x00002ee0
[   60.850877] ptr_res_no: ptr = 0x00000000
[   60.850939] ptr_res_no: ptr = 0x00000000
[   60.850960] ptr_res_no: ptr = 0x00000000
[   60.850969] ptr_res_no: ptr = 0x00000000
[   60.851000] ptr_res_no: ptr = 0x00000000
[   60.852750] ptr_res_no: ptr = 0x00000000
[   60.852760] ptr_res_no: ptr = 0x00000000
[   60.975869] ptr_res_no: ptr = 0x00001770
[   60.975905] ptr_res_no: ptr = 0x00001770
[   60.975923] ptr_res_no: ptr = 0x00001770
...
...




  parent reply	other threads:[~2026-03-09  7:28 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-17 18:49 [RFC PATCH] dmaengine: xilinx_dma: Fix per-channel direction reporting via device_caps Folker Schwesinger
2026-02-20  9:14 ` Rahul Navale
2026-02-20  9:30   ` Pandey, Radhey Shyam
2026-02-20 13:28 ` Rahul Navale
2026-02-20 19:09   ` Folker Schwesinger
2026-02-24  9:30 ` Rahul Navale
2026-02-24 15:10   ` Folker Schwesinger
2026-02-26  7:35 ` Rahul Navale
2026-02-26 20:06   ` Folker Schwesinger
2026-02-26  8:02 ` Rahul Navale
2026-03-02  7:24 ` Rahul Navale
2026-03-03 20:09   ` Folker Schwesinger
2026-03-03 20:19     ` Folker Schwesinger
2026-03-04  8:35 ` Rahul Navale
2026-03-04 14:49   ` Folker Schwesinger
2026-03-05  7:23 ` Rahul Navale
2026-03-05  8:22   ` Folker Schwesinger
2026-03-05  8:29 ` Rahul Navale
2026-03-05  8:32   ` Folker Schwesinger
2026-03-05 11:27 ` Rahul Navale
2026-03-06 10:38   ` Folker Schwesinger
2026-03-09  7:28 ` Rahul Navale [this message]
2026-03-14  8:35   ` Folker Schwesinger
2026-03-16 22:35     ` Marek Vasut
2026-03-14  8:45 ` Folker Schwesinger
2026-03-17 10:49 ` Rahul Navale
2026-03-17 17:20   ` Marek Vasut
2026-03-18 12:35 ` Rahul Navale
2026-03-27 14:51   ` Marek Vasut
2026-03-25 14:22 ` Rahul Navale
2026-03-27 11:43   ` Michal Simek

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=20260309072822.5016-1-rahulnavale04@gmail.com \
    --to=rahulnavale04@gmail.com \
    --cc=Frank.Li@kernel.org \
    --cc=dev@folker-schwesinger.de \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marex@denx.de \
    --cc=marex@nabladev.com \
    --cc=michal.simek@amd.com \
    --cc=radhey.shyam.pandey@amd.com \
    --cc=rahul.navale@ifm.com \
    --cc=suraj.gupta2@amd.com \
    --cc=thomas.gessler@brueckmann-gmbh.de \
    --cc=tomi.valkeinen@ideasonboard.com \
    --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