From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/3] clocksource: timer-keystone: introduce clocksource driver for Keystone
Date: Thu, 26 Dec 2013 12:58:23 -0500 [thread overview]
Message-ID: <52BC6E3F.9060204@ti.com> (raw)
In-Reply-To: <1387974724-31138-2-git-send-email-ivan.khoronzhuk@ti.com>
On Wednesday 25 December 2013 07:32 AM, Ivan Khoronzhuk wrote:
> Add broadcast clock-event device for the Keystone arch.
>
> The timer can be configured as a general-purpose 64-bit timer,
> dual general-purpose 32-bit timers. When configured as dual 32-bit
> timers, each half can operate in conjunction (chain mode) or
> independently (unchained mode) of each other.
>
> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
> ---
Thanks for the update Ivan. This version looks good to me.
Acked-by: Santosh shilimkar <santosh.shilimkar@ti.com>
next prev parent reply other threads:[~2013-12-26 17:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-25 12:32 [PATCH v3 0/3] Introduce clocksource driver for Keystone platform Ivan Khoronzhuk
2013-12-25 12:32 ` [PATCH v3 1/3] clocksource: timer-keystone: introduce clocksource driver for Keystone Ivan Khoronzhuk
2013-12-26 17:58 ` Santosh Shilimkar [this message]
2013-12-26 18:22 ` Stephen Boyd
2013-12-26 18:40 ` ivan.khoronzhuk
2013-12-26 19:42 ` Stephen Boyd
2013-12-25 12:32 ` [PATCH v3 2/3] clocksource: keystone: add bindings for keystone timer Ivan Khoronzhuk
2013-12-26 18:00 ` Santosh Shilimkar
2013-12-25 12:32 ` [PATCH v3 3/3] arm: dts: keystone: add keystone timer entry Ivan Khoronzhuk
2013-12-26 18:02 ` Santosh Shilimkar
2013-12-28 19:07 ` Daniel Lezcano
2013-12-29 19:23 ` Santosh Shilimkar
2014-01-13 11:28 ` ivan.khoronzhuk
2014-01-13 13:14 ` Daniel Lezcano
2014-01-13 14:20 ` Santosh Shilimkar
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=52BC6E3F.9060204@ti.com \
--to=santosh.shilimkar@ti.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.