From: Paul Walmsley <paul@pwsan.com>
To: linux-omap@vger.kernel.org
Subject: [PATCH 0/2] OMAP3 timer: switch Beagle clockevents source to GPTIMER12
Date: Mon, 11 Aug 2008 17:34:20 -0600 [thread overview]
Message-ID: <20080811233109.3046.54050.stgit@localhost.localdomain> (raw)
This patch series allows the clockevents source GPTIMER to be selectable via
Kconfig, and changes the Beagle Kbuild config to use GPTIMER12 instead of
GPTIMER1. The theory here is that GPTIMER12 has its own internal 32kHz
secure oscillator, and does not depend on the external 32kHz clock source,
which we suspect may be noisy.
---
size:
text data bss dec hex filename
3265520 145472 105480 3516472 35a838 vmlinux.beagle.orig
3265568 145472 105480 3516520 35a868 vmlinux.beagle
arch/arm/configs/omap3_beagle_defconfig | 5 +++--
arch/arm/mach-omap2/Kconfig | 16 ++++++++++++++++
arch/arm/mach-omap2/timer-gp.c | 5 ++++-
3 files changed, 23 insertions(+), 3 deletions(-)
next reply other threads:[~2008-08-11 23:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 23:34 Paul Walmsley [this message]
2008-08-11 23:34 ` [PATCH 1/2] OMAP2/3 GPTIMER: allow system tick GPTIMER to be configurable at build Paul Walmsley
2008-08-11 23:34 ` [PATCH 2/2] BeagleBoard: make Beagle use GPTIMER12 for system ticks Paul Walmsley
2008-08-11 23:39 ` Paul Walmsley
2008-08-13 13:36 ` [PATCH 0/2] OMAP3 timer: switch Beagle clockevents source to GPTIMER12 Tony Lindgren
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=20080811233109.3046.54050.stgit@localhost.localdomain \
--to=paul@pwsan.com \
--cc=linux-omap@vger.kernel.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