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: Thu, 5 Mar 2026 13:59:17 +0530 [thread overview]
Message-ID: <20260305082919.5940-1-rahulnavale04@gmail.com> (raw)
In-Reply-To: <DGHGTCJRRZCW.9TGXQW44V6RR@folker-schwesinger.de>
From: Rahul Navale <rahul.navale@ifm.com>
>Could you show the debug output from dma_get_slave_caps()?
logs:
<4>[ 0.302360] dma_slave_caps:
<4>[ 0.302364] src_addr_widths = 0x00000000
<4>[ 0.302368] dst_addr_widths = 0x00000000
<4>[ 0.302371] directions = 0x00000000
<4>[ 0.302374] min_burst = 0x00000000
<4>[ 0.302377] max_burst = 0x00000000
<4>[ 0.302380] max_sg_burst = 0x00000000
<4>[ 0.302383] cmd_pause = 0x00
<4>[ 0.302386] cmd_resume = 0x00
<4>[ 0.302388] cmd_terminate = 0x00
<4>[ 0.302391] residue_granularity= 0x00000000
<4>[ 0.302394] descriptor_reuse = 0x00
<4>[ 0.302398] xilinx_dma_device_caps: caps->directions = 0x00000001
<4>[ 0.302401] xilinx_dma_device_caps: caps->directions = 0x00000001
<4>[ 0.302404] dma_slave_caps:
<4>[ 0.302406] src_addr_widths = 0x00000000
<4>[ 0.302409] dst_addr_widths = 0x00000000
<4>[ 0.302412] directions = 0x00000001
<4>[ 0.302415] min_burst = 0x00000000
<4>[ 0.302418] max_burst = 0x00000000
<4>[ 0.302421] max_sg_burst = 0x00000000
<4>[ 0.302423] cmd_pause = 0x00
<4>[ 0.302426] cmd_resume = 0x00
<4>[ 0.302429] cmd_terminate = 0x01
<4>[ 0.302431] residue_granularity= 0x00000001
<4>[ 0.302434] descriptor_reuse = 0x00
next prev parent reply other threads:[~2026-03-05 8:29 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 [this message]
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
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=20260305082919.5940-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