From: Byron Jacquot <BJacquot@vestatech.com>
To: <ecos-devel@ecos.sourceware.org>
Subject: Wallclock on LCP2xxx dependency
Date: Fri, 14 May 2010 20:08:00 -0000 [thread overview]
Message-ID: <CC4F5268C9A9A04EAFB0F383F338229507B768@phoenix.vestatech.local> (raw)
Howdy Everyone,
I'm trying to track down the history of an item in the LPC2xxx wallclock
driver CDL file.
The Wallclock CDL contains the following:
requires { CYGHWR_HAL_ARM_LPC2XXX_IDLE_PWRSAVE == 0 }
I'm trying to figure out where this dependency comes from. The
IDLE_PWRSAVE option allows the idle thread to turn off the CPU core.
This has no impact on the peripherals, including the RTC. The
peripherals continue to run, and they will wake the CPU on any interrupt
activity.
I've verified this on live LPC2292/01 hardware - the RTC is keeping
time, and the CPU is spending a fair amount of time idle, as measured
with an Ammeter.
Was there an intent that I'm not grasping? It seems that this
requirement isn't a hard one.
Thanks,
Byron Jacquot
Vesta Technology
next reply other threads:[~2010-05-14 20:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 20:08 Byron Jacquot [this message]
2010-05-15 7:19 ` Sergei Gavrikov
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=CC4F5268C9A9A04EAFB0F383F338229507B768@phoenix.vestatech.local \
--to=bjacquot@vestatech.com \
--cc=ecos-devel@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).