[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161207164341.GX6408@localhost>
Date: Wed, 7 Dec 2016 22:13:41 +0530
From: Vinod Koul <vinod.koul@...el.com>
To: Måns Rullgård <mans@...sr.com>
Cc: Mason <slash.tmp@...e.fr>, Russell King <linux@....linux.org.uk>,
dmaengine@...r.kernel.org,
Linus Walleij <linus.walleij@...aro.org>,
Dan Williams <dan.j.williams@...el.com>,
LKML <linux-kernel@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Jon Mason <jdmason@...zu.us>, Mark Brown <broonie@...nel.org>,
Lars-Peter Clausen <lars@...afoo.de>,
Lee Jones <lee.jones@...aro.org>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Arnd Bergmann <arnd@...db.de>,
Maxime Ripard <maxime.ripard@...e-electrons.com>,
Dave Jiang <dave.jiang@...el.com>,
Peter Ujfalusi <peter.ujfalusi@...com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>,
Sebastian Frias <sf84@...oste.net>,
Thibaud Cornic <thibaud_cornic@...madesigns.com>
Subject: Re: Tearing down DMA transfer setup after DMA client has finished
On Tue, Dec 06, 2016 at 01:14:20PM +0000, Måns Rullgård wrote:
>
> That's not going to work very well. Device drivers typically request
> dma channels in their probe functions or when the device is opened.
> This means that reserving one of the few channels there will inevitably
> make some other device fail to operate.
No that doesnt make sense at all, you should get a channel only when you
want to use it and not in probe!
--
~Vinod
Powered by blists - more mailing lists