Re: [PATCH v6 0/3] Introduce clocksource driver for Keystone platform

[Santosh Shilimkar]

Daniel,

On Monday 10 February 2014 05:10 AM, Ivan Khoronzhuk wrote:
> Add a broadcast timer64 based clockevent driver for keystone arch.
> This driver uses timer in 64-bit general purpose mode as clock event
> device.
> 
> Documentation:
>     http://www.ti.com/lit/ug/sprugv5a/sprugv5a.pdf
> 
> Based on
> git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git
> keystone/master
> 
> v5..v6:
> 	added function to encapsulate __iowmb().
> 
> v4..v5:
> 	used __iowmb() insted of wmb()
> 
> v3..v4:
> 	rebased on latest of linux-keystone.git keystone/master
> 
> v2..v3:
> - clocksource: timer-keystone: introduce clocksource driver for
> 	changed "u64" type to "unsigned long" for hz_period as more appropriate
> 	hz_period rounded up by DIV_ROUND_UP(rate, HZ)
> 	corrected comments
> 
> v1..v2:
> - clocksource: timer-keystone: introduce clocksource driver for
> 	renamed timer on "timer-keystone"
> 	in keystone_timer_interrupt() evet pointer is passed via "dev_id"
> 	used __relaxed variants of writel/readl and added explicit barriers
> 	added "keystone_timer_disable()" for using in keystone_set_mode()
> 	keystone_timer_config() is not used for disabling the timer any more
> 	in case of an unsupported mode the keystone_timer_config() returns -1.
> 	used request_irq() instead of setup_irq()
> 	assigned irq for event_device in event_dev->irq
> 	calculated timer.hz_period for CLOCK_EVT_MODE_PERIODIC at init
> 	deleted spare call of keystone_timer_config() in keystone_timer_init()
> 
> Ivan Khoronzhuk (3):
>   clocksource: timer-keystone: introduce clocksource driver for Keystone
>   clocksource: keystone: add bindings for keystone timer
>   arm: dts: keystone: add keystone timer entry
> 
Can you queue the first two patches from the series ?
I will queue the dts patch via my tree.

Regards,
Santosh


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/