[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200124061359.GF2841@vkoul-mobl>
Date: Fri, 24 Jan 2020 11:43:59 +0530
From: Vinod Koul <vkoul@...nel.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Peter Ujfalusi <peter.ujfalusi@...com>,
Dan Williams <dan.j.williams@...el.com>,
dmaengine@...r.kernel.org,
Linux-Renesas <linux-renesas-soc@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] dmaengine: Create symlinks between DMA channels and
slaves
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
Powered by blists - more mailing lists