Re: [PATCH v12 00/11] DMA Engine support for AM33XX

[Santosh Shilimkar]

On Tuesday 25 June 2013 10:16 AM, Sekhar Nori wrote:
> On 6/25/2013 12:24 PM, Tony Lindgren wrote:
>> * Benoit Cousson <b-cousson@xxxxxx> [130624 07:42]:
>>> Hi Tony,
>>>
>>> On 06/24/2013 12:19 PM, Tony Lindgren wrote:
>>>> Hi,
>>>>
>>>> For merging this series, I suggest the following sets:
>>>>
>>>> * Joel A Fernandes <joelagnel@xxxxxx> [130620 14:13]:
>>>>>
>>>>> Joel A Fernandes (3):
>>>>>   edma: config: Enable config options for EDMA
>>>>>   da8xx: config: Enable MMC and FS options
>>>>>   ARM: davinci: Fix compiler warnings in devices-da8xx
>>>>>
>>>>> Matt Porter (8):
>>>>>   dmaengine: edma: Add TI EDMA device tree binding
>>>>>   ARM: edma: Add DT and runtime PM support to the private EDMA API
>>>>>   ARM: edma: Add EDMA crossbar event mux support
>>>>>   dmaengine: edma: enable build for AM33XX
>>>>
>>>> Sekhar should queue the above patches, I've acked the
>>>> mach-omap2/Kconfig change.
>>>>
>>>>>   spi: omap2-mcspi: add generic DMA request support to the DT binding
>>>>>   spi: omap2-mcspi: convert to dma_request_slave_channel_compat()
>>>>
>>>>
>>>> The spi changes should get merged via the driver list.
>>>>
>>>>>   ARM: dts: add AM33XX EDMA support
>>>>>   ARM: dts: add AM33XX SPI DMA support
>>>>
>>>> Benoit should queue the .dts changes.
>>>
>>> I'll do that, but do you consider them for 3.11?
>>
>> Yes right after -rc1 if it makes the DMA work. We almost
>> certainly need to send few branches of fixes after -rc1 once
>> we find out what might have broken by the removal of the
>> hwmod data..
> 
> The DMA related changes went into arm-soc yesterday. So it should be
> safe to send the DT patches in before the merge window opens. If Tony is
> done with sending his pull requests may be Benoit can send to arm-soc
> directly?
> 
I was just typing the same thing. Even if Tony send them during rc's,
thats fine.

Regards,
Santosh

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/