Return-path: Received: from lunge.queued.net ([173.255.254.236]:60583 "EHLO lunge.queued.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751932Ab2GSEha (ORCPT ); Thu, 19 Jul 2012 00:37:30 -0400 Date: Wed, 18 Jul 2012 21:37:13 -0700 From: Andres Salomon To: Andrew Morton Cc: Paul Fox , Daniel Drake , "Richard A. Smith" , linux-kernel@vger.kernel.org, libertas-dev@lists.infradead.org, linux-wireless@vger.kernel.org, netdev@vger.kernel.org, platform-driver-x86@vger.kernel.org, devel@driverdev.osuosl.org, Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , x86@kernel.org, Dan Williams , "John W. Linville" , Matthew Garrett , Anton Vorontsov , David Woodhouse , Chris Ball , Jon Nettleton , Greg Kroah-Hartman Subject: [PATCH RESEND 0/9] OLPC: create a generic OLPC EC driver Message-ID: <20120718213713.232e4161@dev.queued.net> (sfid-20120719_063749_144494_628A49F9) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-wireless-owner@vger.kernel.org List-ID: The OLPC EC (Embedded Controller) code that is currently upstream is x86-only, originally written for the XO-1. Since then, we've had the XO-1.5 (also x86), and XO-1.75 (arm-based) enter mass production. The 1.75 uses a vastly different EC protocol, and future hardware revisions are likely to change it even further. However, the drivers do share quite a bit of code, so it makes sense to have a platform-agnostic driver that calls into platform-specific hooks for each XO's EC driver. This is the first stab and creating such a beast (with further patches pending). Aside from the lack of code duplication, this is helpful for fixing bugs in one place (for example, we fixed an EC suspend/resume bug in 1.75 that I've just seen happen on 1.5 without these patches. With these patches, the problem goes away). These patches are against Linus's current HEAD; let me know if they don't apply somewhere, and I'll happily redo them against the -next tree. I'm assuming that these changes (which touch places like x86, wireless, and staging) should go through either the x86 tree, or through akpm's tree. Alternatively, if the reviews are positive and I can get SOBs from the relevant maintainers, I can set up a platform-olpc tree somewhere and request a pull from Linus.