Since I was in a nice mood, because the week-end is almost there, Ifixed them myself.

Please note that I had to rename the API becasue it was way too long todo a proper alignement.

omap_device_fill_dma_resources -> _od_fill_dma_resources

In fact I realized that some private APIs should probably be renamed aswell like that forconsistency.

Just let me know if you have any issue with that version.

Regards,Benoit

---From b82b04e8eb27abe0cfe9cd7bf4fee8bb1bb9b013 Mon Sep 17 00:00:00 2001From: Vaibhav Hiremath <hvaibhav@ti.com>Date: Wed, 29 Aug 2012 15:18:11 +0530Subject: [PATCH] ARM: OMAP: omap_device: Do not overwrite resourcesallocated by OF layerWith the new devices (like, AM33XX and OMAP5) we now only supportDT boot mode of operation and now it is the time to start killingslowly the dependency on hwmod, so with this patch, we are startingwith device resources.The idea here is implemented considering to both boot modes - - DT boot mode OF framework will construct the resource structure (currently does for MEM & IRQ resource) and we should respect/use these resources, killing hwmod dependency. If pdev->num_resources > 0, we assume that MEM & IRQ resources have been allocated by OF layer already (through DTB). Once DMA resource is available from OF layer, we should kill filling any resources from hwmod.

- Non-DT boot mode Here, pdev->num_resources = 0, and we should get all the resources from hwmod (following existing steps)