[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <565D6EDA.4070002@ti.com>
Date: Tue, 1 Dec 2015 11:56:42 +0200
From: Peter Ujfalusi <peter.ujfalusi@...com>
To: Andy Shevchenko <andy.shevchenko@...il.com>
CC: Vinod Koul <vinod.koul@...el.com>, Arnd Bergmann <arnd@...db.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
dmaengine <dmaengine@...r.kernel.org>,
Linux OMAP Mailing List <linux-omap@...r.kernel.org>,
linux-arm Mailing List <linux-arm-kernel@...ts.infradead.org>,
"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
Sekhar Nori <nsekhar@...com>,
linux-spi <linux-spi@...r.kernel.org>
Subject: Re: [RFC v02 03/15] dmaengine: core: Introduce new, universal API to
request a channel
On 11/30/2015 04:51 PM, Andy Shevchenko wrote:
>> +struct dma_chan *dma_request_chan(struct device *dev, const char *name)
>> +{
>> + struct dma_device *device, *_d;
>> + struct dma_chan *chan = NULL;
>> +
>> + /* If device-tree is present get slave info from here */
>> + if (dev->of_node)
>> + chan = of_dma_request_slave_channel(dev->of_node, name);
>> +
>> + /* If device was enumerated by ACPI get slave info from here */
>> + if (ACPI_HANDLE(dev) && !chan)
>
> The preferable way is to use
> has_acpi_companion() instead of ACPI_HANDLE().
I have done this part based on the dma_request_slave_channel_reason().
Will switch to use the has_acpi_companion() for the next RFC.
>> + chan = acpi_dma_request_slave_chan_by_name(dev, name);
>> +
>> + if (chan)
>> + return chan;
>> +
--
Péter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists