On 10/17/2012 01:01 PM, Jon Hunter wrote: > This series adds device-tree support for the timers on OMAP2+ devices > including AM33xx. > > Testing: > 1. I have booted tested this series on OMAP2420 H4, OMAP3430 Beagle, OMAP4430 > Panda and AM335x Beagle Bone with/without ... > a). device-tree present > b). CONFIG_OMAP_32K_TIMER set > c). kernel boot parameter "clocksource=gp_timer" present > 2. I have tested the all the timers (not used by the kernel as sys-timers) on > OMAP2420 H4, OMAP3430 Beagle and OMAP4430 Panda with/without device-tree with > this series. The testing includes ... > a. Configuring, starting a timer and checking the counter value is > incrementing. > b. Testing timer overflow interrupt when timer expires. > c. Using different clock sources to operate the timer with. > > V3 changes: > - Removed definition "TIMER_PROP_ALWON" per Rob Herring's feedback > - Updated OMAP system timer (clock-events and clock-source) code so that > HWMOD is NOT used for getting resource (memory and interrupt) information > when device-tree is present. > > V2 changes: > - Remove use of device-tree alias property > - Migrate OMAP timers to request timers by property instead of device ID > - Include OMAP2 support Forgot to mention that this is based on top of v3.7-rc1. Cheers Jon -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
