From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomi Valkeinen Subject: Re: [GIT PULL] omap changes for v2.6.39 merge window Date: Fri, 01 Apr 2011 10:32:37 +0300 Message-ID: <1301643157.3393.17.camel@deskari> References: <201103301906.42429.arnd@arndb.de> <87d3l7jqpr.fsf@ti.com> <201103311723.02301.arnd@arndb.de> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <201103311723.02301.arnd@arndb.de> Sender: linux-kernel-owner@vger.kernel.org To: Arnd Bergmann Cc: Kevin Hilman , Thomas Gleixner , Russell King - ARM Linux , Ingo Molnar , Nicolas Pitre , david@lang.hm, Linus Torvalds , Tony Lindgren , David Brown , lkml , linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org, Catalin Marinas , "H. Peter Anvin" List-Id: linux-omap@vger.kernel.org On Thu, 2011-03-31 at 17:23 +0200, Arnd Bergmann wrote: > * The DSS display drivers introduce new infrastructure include new bus > types that have the complexity to make them completely generic, but > in practice can only work on OMAP, and are clearly not written with > cross-vendor abstractions in mind. If you mean the panel drivers, then I disagree. They are currently OMAP specific, but they are designed so that making them generic shouldn't be too difficult. It's been my aim for a long time already to make the panel drivers generic, but I've never had time and it's never been quite clear to me what would be the best way to do that. The core DSS driver is OMAP specific, and while the DSS IP could in theory be used in some other platform, that is not currently the case and I wouldn't want to needlessly start abstracting things for just the sake of abstracting. Tomi