On Wed, Sep 26, 2012 at 02:10:19PM -0700, Greg Kroah-Hartman wrote: > On Wed, Sep 26, 2012 at 09:44:29AM -0400, Matt Porter wrote: > > Add ifdefery hacks to only use SRAM on Davinci. This > > needs to be cleaned up with a sane generic SRAM allocator > > (like the DT based driver available that can't be used on > > Davinci which is just starting DT conversion) before it > > can go upstream. > > > > Adds DT, pinctrl, and runtime PM support for use on > > AM33xx. > > Ick, that's really messy, no other way to do this in a "cleaner" > fashion? There is, I had to untangle some ugly history on the SRAM situation first. First, and what I found humorous is that this driver is completely dead code in the tree...a driver to nowhere. It's not hooked up at all for DA850, no platform devices, no clock support, and to top it off the private SRAM API it's calling uses the ARM local SRAM that the PRU can't even access it [1]. So it's completely broken and one possible course of action is to just say tough luck to Davinci and remove all that SRAM code. I happen to care a bit about DA850 as I have the AM180x variant here... I noticed that previous attempts at consolidating SRAM allocation failed to achieve consensus [2] or in the case of when Jean added the phys support to genalloc the associated mach-davinci/ support was never picked up [3]. The patch in to enable L3 RAM support [1] depended on the genalloc conversion and all appears to have been forgotten and bitrotted since then. I decided to go ahead and add a genalloc pool for the L3 RAM (shared sram) on DA850 that PRU can use and strip out the private API. I'll post v2 with that supports that supports both platforms cleanly. -Matt [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2011-June/051609.html [2] https://patchwork.kernel.org/patch/710741/ [3] http://lists.infradead.org/pipermail/linux-arm-kernel/2011-July/057293.html -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
