public inbox for dmaengine@vger.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>,
	Dan Williams <dan.j.williams@intel.com>,
	dmaengine@vger.kernel.org,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] dmaengine: Create symlinks between DMA channels and slaves
Date: Fri, 24 Jan 2020 11:43:59 +0530	[thread overview]
Message-ID: <20200124061359.GF2841@vkoul-mobl> (raw)
In-Reply-To: <20200122094002.GS2841@vkoul-mobl>

On 22-01-20, 15:10, Vinod Koul wrote:

> I like the idea of adding this in debugfs and giving more info, I would
> actually love to add bytes_transferred and few more info (descriptors
> submitted etc) to it...
> 
> > > This way we will have all the information in one place, easy to look up
> > > and you don't need to manage symlinks dynamically, just check all
> > > channels if they have slave_device/name when they are in_use (in_use w/o
> > > slave_device is 'non slave')
> > >
> > > Some drivers are requesting and releasing the DMA channel per transfer
> > > or when they are opened/closed or other variations.
> > >
> > > > What do other people think?
> > 
> > Vinod: do you have some guidance for your minions? ;-)
> 
> 
> That said, I am not against merging this patch while we add more
> (debugfs)... So do my minions agree or they have better ideas :-)

So no new ideas, I am going to apply this and queue for 5.6, something
is better than nothing.

And I am looking forward for debugfs to give better picture, volunteers?

-- 
~Vinod

  reply	other threads:[~2020-01-24  6:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200129174723eucas1p1fe4f76325f463fc9e3645ce18740d2eb@eucas1p1.samsung.com>
2020-01-17 15:30 ` [PATCH v2] dmaengine: Create symlinks between DMA channels and slaves Geert Uytterhoeven
2020-01-17 16:26   ` Niklas Söderlund
2020-01-17 20:10   ` Peter Ujfalusi
2020-01-20  9:01     ` Geert Uytterhoeven
2020-01-20 10:16       ` Peter Ujfalusi
2020-01-20 10:51         ` Geert Uytterhoeven
2020-01-20 12:06           ` Peter Ujfalusi
2020-01-21 20:22             ` Geert Uytterhoeven
2020-01-22  9:40               ` Vinod Koul
2020-01-24  6:13                 ` Vinod Koul [this message]
2020-01-24  7:31                   ` Peter Ujfalusi
2020-01-27  5:08                     ` Vinod Koul
2020-01-29 17:47   ` Marek Szyprowski
2020-01-30  8:30     ` Geert Uytterhoeven
2020-01-30 10:33       ` Marek Szyprowski
2020-01-30 10:47         ` Geert Uytterhoeven
2020-01-30  9:43   ` Peter Ujfalusi
2020-01-30  9:51     ` Geert Uytterhoeven
2020-01-30 10:22       ` Peter Ujfalusi

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=20200124061359.GF2841@vkoul-mobl \
    --to=vkoul@kernel.org \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=peter.ujfalusi@ti.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