Messages in this thread | | | Date | Wed, 31 Oct 2012 14:43:11 -0700 | From | Tony Lindgren <> | Subject | Re: [PATCH 0/3] capebus moving omap_devices to mach-omap2 |
| |
* Pantelis Antoniou <panto@antoniou-consulting.com> [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
| |