public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: Byron Jacquot <BJacquot@vestatech.com>
Cc: ecos-devel@ecos.sourceware.org
Subject: Re: Wallclock on LCP2xxx dependency
Date: Sat, 15 May 2010 07:19:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.00.1005151007321.19451@sg-desktop.local> (raw)
In-Reply-To: <CC4F5268C9A9A04EAFB0F383F338229507B768@phoenix.vestatech.local>

On Fri, 14 May 2010, Byron Jacquot wrote:
> 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.

Hi Byron,

It seems for me that is the odd requirement (according LPC2000 datasheets 
even in the sleep mode RTC oscillator is not stopped and its interrupts 
continue to awake core). Could you send a patch in the eCos patches list, 
please?

Thanks for the catch,

Sergei

      reply	other threads:[~2010-05-15  7:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-14 20:08 Byron Jacquot
2010-05-15  7:19 ` Sergei Gavrikov [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=alpine.DEB.2.00.1005151007321.19451@sg-desktop.local \
    --to=sergei.gavrikov@gmail.com \
    --cc=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).