From: Vinod Koul <vkoul@kernel.org>
To: Katsuhiro Suzuki <katsuhiro@katsuster.net>
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [v2] dmaengine: pl330: introduce debugfs interface
Date: Mon, 25 Mar 2019 10:28:30 +0530 [thread overview]
Message-ID: <20190325045830.GI5348@vkoul-mobl> (raw)
On 17-03-19, 19:03, Katsuhiro Suzuki wrote:
> This patch adds debugfs interface to show the relationship between
> DMA threads (hardware resource for transferring data) and DMA
> channel ID of DMA slave.
>
> Typically, PL330 has many slaves than number of DMA threads.
> So sometimes PL330 cannot allocate DMA threads for all slaves even
> if a user specify DMA channel ID in devicetree. This interface will
> be useful for checking that DMA threads are allocated or not.
>
> Below is an output sample:
>
> $ sudo cat /sys/kernel/debug/ff1f0000.dmac
> PL330 physical channels:
> THREAD: CHANNEL:
> -------- -----
> 0 8
> 1 9
> 2 11
> 3 12
> 4 14
> 5 15
> 6 10
> 7 --
>
Applied, thanks
next reply other threads:[~2019-03-25 4:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 4:58 Vinod Koul [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-17 10:03 [v2] dmaengine: pl330: introduce debugfs interface Katsuhiro Suzuki
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=20190325045830.GI5348@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=katsuhiro@katsuster.net \
--cc=linux-kernel@vger.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