[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VeRemcJkMMB7D2==Y-A4We=s1ntojZoPRdVS8vs+dB_Ew@mail.gmail.com>
Date: Tue, 4 Feb 2020 13:21:00 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Vinod Koul <vkoul@...nel.org>
Cc: Peter Ujfalusi <peter.ujfalusi@...com>,
dmaengine <dmaengine@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Dan Williams <dan.j.williams@...el.com>
Subject: Re: [PATCH 0/3] dmaengine: Stear users towards dma_request_slave_chan()
On Tue, Feb 4, 2020 at 8:21 AM Vinod Koul <vkoul@...nel.org> wrote:
>
> On 03-02-20, 12:37, Andy Shevchenko wrote:
> > On Mon, Feb 3, 2020 at 12:32 PM Peter Ujfalusi <peter.ujfalusi@...com> wrote:
> >
> > > dma_request_slave_channel_reason() no longer have user in mainline, it
> > > can be removed.
> > >
> > > Advise users of dma_request_slave_channel() and
> > > dma_request_slave_channel_compat() to move to dma_request_slave_chan()
> >
> > How? There are legacy ARM boards you have to care / remove before.
> > DMAengine subsystem makes a p*s off decisions without taking care of
> > (I'm talking now about dma release callback, for example) end users.
>
> Can you elaborate issue you are seeing with dma_release callback?
[ 7.980381] intel-lpss 0000:00:1e.3: WARN: Device release is not
defined so it is not safe to unbind this driver while in use
It's not limited to that driver, but actually all I'm maintaining.
Users are not happy!
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists