Vaibhav Hiremath <[email protected]> writes: > OMAP device has 32k-sync timer which is currently used as a > clocksource in the kernel (omap2plus_defconfig). > The current implementation uses compile time selection between > gp-timer and 32k-sync timer, which breaks multi-omap build for > the devices like AM33xx, where 32k-sync timer is not available. > > So use hwmod database lookup mechanism, through which at run-time > we can identify availability of 32k-sync timer on the device, > else fall back to gp-timer.
With the runtime detection & fallback, I suggest also removing the Kconfig choice between the two as well. Kevin -- 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
