From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [PATCH 1/5] capemgr: Beaglebone DT overlay based cape manager Date: Mon, 7 Jan 2013 12:23:06 -0800 Message-ID: <20130107202306.GH14149@atomide.com> References: <1357584666-17374-1-git-send-email-panto@antoniou-consulting.com> <1357584666-17374-2-git-send-email-panto@antoniou-consulting.com> <20130107200945.GF14149@atomide.com> <379B16EC-BFAA-4C27-8321-E7133C03368D@antoniou-consulting.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <379B16EC-BFAA-4C27-8321-E7133C03368D@antoniou-consulting.com> Sender: linux-omap-owner@vger.kernel.org To: Pantelis Antoniou Cc: Grant Likely , Rob Herring , Rob Landley , Jon Loeliger , Stephen Warren , David Gibson , Benoit Cousson , Mitch Bradley , Alan Tull , Arnd Bergmann , Greg Kroah-Hartman , linux-omap@vger.kernel.org, devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Matt Porter , Russ Dill , Koen Kooi , Joel A Fernandes , Rob Clark , Jason Kridner , Matt Ranostay List-Id: devicetree@vger.kernel.org * Pantelis Antoniou [130107 12:16]: > Hi Tony, > > On Jan 7, 2013, at 10:09 PM, Tony Lindgren wrote: > > > * Pantelis Antoniou [130107 10:54]: > >> A cape loader based on DT overlays and DT objects. > >> > >> Beaglebone cape manager implementation. > >> > >> Signed-off-by: Pantelis Antoniou > >> --- > >> arch/arm/mach-omap2/Kconfig | 2 + > >> drivers/misc/Kconfig | 2 + > >> drivers/misc/Makefile | 1 + > >> drivers/misc/cape/Kconfig | 5 + > >> drivers/misc/cape/Makefile | 5 + > >> drivers/misc/cape/beaglebone/Kconfig | 11 + > >> drivers/misc/cape/beaglebone/Makefile | 5 + > >> drivers/misc/cape/beaglebone/capemgr.c | 1835 ++++++++++++++++++++++++++++++++ > > > > The driver should probably be in drivers/bus? > > > > It was a bus on the previous iteration and there was a flame storm of epic proportions. Heh :) > It is not a bus at all now, it's just a device loader; there are no > bus constructs at all. I am at a loss to classify it really, so drivers/misc > where every misfit ends up sounded OK. Right.. > I'm open to suggestions though. Well how about split it to an eeprom driver, and Linux generic device loader parts? Regards, Tony