[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <517E7589.5030205@atmel.com>
Date: Mon, 29 Apr 2013 15:28:41 +0200
From: Nicolas Ferre <nicolas.ferre@...el.com>
To: Vinod Koul <vinod.koul@...el.com>
CC: <ludovic.desroches@...el.com>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-mmc@...r.kernel.org>, <linux-i2c@...r.kernel.org>,
<plagnioj@...osoft.com>,
Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 1/6] at_hdmac: move to generic DMA binding
On 04/23/2013 05:44 AM, Vinod Koul :
> On Mon, Apr 22, 2013 at 12:22:32PM +0200, Nicolas Ferre wrote:
>> On 04/19/2013 11:11 AM, ludovic.desroches@...el.com :
>>> From: Ludovic Desroches <ludovic.desroches@...el.com>
>
>>> +#ifdef CONFIG_OF
>>> +static bool at_dma_filter(struct dma_chan *chan, void *slave)
> this is not defined for else case here. Also this could be CONFIG_DMA_OF...?
in fact, at_dma_filter() is only used in corresponding
dma_request_channel() in at_dma_xlate() function just below and only in
case of CONFIG_OF.
As the at_dma_xlate() is an empty function in !CONFIG_OF case, the
at_dma_filter() is not needed.
For the use of CONFIG_OF and not CONFIG_OF_DMA, it is simply because it
it the directive that we currently use in drivers when we have to put
the device tree condition around a piece of code. It is quite a common
pattern I think.
Moreover, it is what is used in dw_dmac.c and mv_xor.c...
>>> +{
>>> + struct at_dma_slave *atslave = slave;
>>> +
>>> + if (atslave->dma_dev == chan->device->dev) {
>>> + chan->private = atslave;
>>> + return true;
>>> + } else {
>>> + return false;
>>> + }
>>> +}
>
> --
> ~Vinod
Best regards,
--
Nicolas Ferre
--
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