From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [PATCH 0/3] capebus moving omap_devices to mach-omap2 Date: Wed, 31 Oct 2012 14:43:11 -0700 Message-ID: <20121031214310.GA15766@atomide.com> References: <1351783082-11411-1-git-send-email-panto@antoniou-consulting.com> <20121031175219.GH12739@atomide.com> <20121031180935.GL12739@atomide.com> <50918223.6080003@ti.com> <8AD2F7AF-8315-442B-A394-1A38DAB29F52@antoniou-consulting.com> <20121031212639.GQ12739@atomide.com> <8B058B00-6C21-4410-A24B-75651D49F6EC@antoniou-consulting.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <8B058B00-6C21-4410-A24B-75651D49F6EC@antoniou-consulting.com> Sender: linux-kernel-owner@vger.kernel.org To: Pantelis Antoniou Cc: Benoit Cousson , linux-kernel@vger.kernel.org, Koen Kooi , Matt Porter , Russ Dill , linux-omap@vger.kernel.org, Kevin Hilman , Paul Walmsley List-Id: linux-omap@vger.kernel.org * Pantelis Antoniou [121031 14:38]: > > There a a whole bunch of conflicting capes. There's no > way to instantiate them together. They must be instantiated > only after their EEPROMs are read and they are matched > to their corresponding cape drivers. You don't need to instantiate the capes during __init, you need to just instantiate the omap internal devices which are always there in the hardware. These internal devices just need to be set to state = "disabled" until they are used. The capes themselves should not have anything to do with omap_hwmod or omap_device, they just contain external connectors, regulators, LCD panels etc. To your capebus the omap internal devices should look like just regular struct device entries. Regards, Tony