From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 0/3] Introduce clocksource driver for Keystone platform
Date: Tue, 11 Feb 2014 13:50:20 +0100 [thread overview]
Message-ID: <52FA1C8C.40105@linaro.org> (raw)
In-Reply-To: <52F8F55A.2090903@ti.com>
On 02/10/2014 04:50 PM, Santosh Shilimkar wrote:
> 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.
Sure.
--
<http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
prev parent reply other threads:[~2014-02-11 12:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 10:10 [PATCH v6 0/3] Introduce clocksource driver for Keystone platform Ivan Khoronzhuk
2014-02-10 10:10 ` [PATCH v6 1/3] clocksource: timer-keystone: introduce clocksource driver for Keystone Ivan Khoronzhuk
2014-02-11 12:58 ` Daniel Lezcano
2014-02-18 10:40 ` Matthias Brugger
2014-02-18 10:46 ` Daniel Lezcano
2014-02-10 10:10 ` [PATCH v6 2/3] clocksource: keystone: add bindings for keystone timer Ivan Khoronzhuk
2014-02-11 12:58 ` Daniel Lezcano
2014-02-10 10:10 ` [PATCH v6 3/3] arm: dts: keystone: add keystone timer entry Ivan Khoronzhuk
2014-02-10 15:50 ` [PATCH v6 0/3] Introduce clocksource driver for Keystone platform Santosh Shilimkar
2014-02-11 12:50 ` Daniel Lezcano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52FA1C8C.40105@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).