From mboxrd@z Thu Jan 1 00:00:00 1970 From: tomi.valkeinen@ti.com (Tomi Valkeinen) Date: Tue, 19 Apr 2011 17:16:55 +0300 Subject: [RFC PATCH] Consolidate SRAM support In-Reply-To: <20110418081743.GH12272@atomide.com> References: <20110415130607.GM1611@n2100.arm.linux.org.uk> <20110416130929.GL4423@n2100.arm.linux.org.uk> <20110418064838.GE12272@atomide.com> <1303110011.2062.7.camel@deskari> <20110418081743.GH12272@atomide.com> Message-ID: <1303222615.32281.91.camel@deskari> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi Tony and Russell, On Mon, 2011-04-18 at 11:17 +0300, Tony Lindgren wrote: > * Tomi Valkeinen [110418 09:57]: > > So, I can make a patch that removes the SRAM support from omapfb, and > > queue it up for the next merge window. > > OK. That patch should probably go into Russell's tree along with > other SRAM related patches to avoid conflicts. Here's a simple patch to remove SRAM support from omapfb. Or more precisely, this just disables it. I started to remove the SRAM support from the drivers, but the patches got quite big and will probably cause conflicts if they reside in somebody else's tree than mine. So I believe it's easiest to divide SRAM FB removal into this patch, handled by Russell (?), and then the rest, handled by me. Is there something else related to OMAP FB than the code removed in this patch that is hindering the SRAM work? Tomi