From: tony@atomide.com
To: balrogg@gmail.com
Cc: Linux-OMAP <linux-omap-open-source@linux.omap.com>
Subject: Re: [PATCH] ARM: OMAP: Disable 32kHz timer warning
Date: Thu, 10 Aug 2006 09:55:17 +0300 [thread overview]
Message-ID: <20060810065516.GB30195@atomide.com> (raw)
In-Reply-To: <fb249edb0608092349l7af8a3a0sc34efd84013d8a8e@mail.gmail.com>
* andrzej zaborowski <balrog@zabor.org> [060810 09:49]:
> This makes the following warning conditional as the 32kHz timer is
> only implemented for 16xx out of OMAP1 cpus:
> arch/arm/mach-omap1/pm.c:138:2: warning: #warning Enable 32kHz OS
> timer in order to allow sleep states in idle
The warning is still valid though. The current tree does not use sleep
states for idling for 15xx.
It may be worth checking if there is a continuously running 32KHz
timer somewhere on 15xx as it would allow using dynamic tick and sleep
states for idling. Last time I looked I did not find anything, but then
again I only browsed the TRM and did not scan registers for it.
Could somebody at TI confirm if 15xx has a continuously running 32KHz
timer at some register? If not, some other unused timer could be
set to run at 32KHz continuously to update time from it.
Regards,
Tony
prev parent reply other threads:[~2006-08-10 6:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 6:49 [PATCH] ARM: OMAP: Disable 32kHz timer warning andrzej zaborowski
2006-08-10 6:55 ` tony [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=20060810065516.GB30195@atomide.com \
--to=tony@atomide.com \
--cc=balrogg@gmail.com \
--cc=linux-omap-open-source@linux.omap.com \
/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