Hi,
On Thu, Sep 23, 2010 at 10:23:17AM -0500, Kevin Hilman wrote:
could the omap_hwmod_lookup() part be moved to omap_device_build ? Or
maybe create a omap_hwmod_lookup_and_build(oh_name, dev_name, bus_id,
pdata, sizeof(*pdata)) ??
I don't think that this is too much extra work.
Also, many drivers are not doing a single hwmod lookup, they are using
an iterator to iterate over a bunch of hwmods in a given class (c.f.
omap_hwmod_for_each_by_class)
So, IMO, keeping the lookup and build separate is better.
I think this is also a duplication, it's gonna on all hwmod device
registration, no ?
Only for devices setting DMA masks.
This is no more duplication than we have today for all platform_devices.
ok, agreed.
--
balbi
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
