From: florian@openwrt.org (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: Clocksource/clockevent with non self-reloading timer blocks?
Date: Mon, 23 Jul 2012 21:14:49 +0200 [thread overview]
Message-ID: <1772014.SXB9lS46ng@bender> (raw)
Hi all,
The SoC I work on (Moschip MCS8140) has several timer blocks, but none of them
are self-reloading timers, yet I can enable/disable the free-running timer,
and enable/disable the interrupt generation.
Are there any existing in kernel clocksource/clockevent drivers with the same
constraints?
Thank you very much for your answer.
--
Florian
WARNING: multiple messages have this Message-ID (diff)
From: Florian Fainelli <florian@openwrt.org>
To: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, John Stultz <johnstul@us.ibm.com>
Subject: Clocksource/clockevent with non self-reloading timer blocks?
Date: Mon, 23 Jul 2012 21:14:49 +0200 [thread overview]
Message-ID: <1772014.SXB9lS46ng@bender> (raw)
Hi all,
The SoC I work on (Moschip MCS8140) has several timer blocks, but none of them
are self-reloading timers, yet I can enable/disable the free-running timer,
and enable/disable the interrupt generation.
Are there any existing in kernel clocksource/clockevent drivers with the same
constraints?
Thank you very much for your answer.
--
Florian
next reply other threads:[~2012-07-23 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 19:14 Florian Fainelli [this message]
2012-07-23 19:14 ` Clocksource/clockevent with non self-reloading timer blocks? Florian Fainelli
2012-07-26 7:20 ` Gilles Chanteperdrix
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=1772014.SXB9lS46ng@bender \
--to=florian@openwrt.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 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.