From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: Configure reference clock for Versatile Express timers
Date: Tue, 18 Jan 2011 18:18:40 +0000 [thread overview]
Message-ID: <20110118181840.GH16980@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <000001cbb739$ef879490$ce96bdb0$@moll@arm.com>
On Tue, Jan 18, 2011 at 06:02:56PM -0000, Pawel Moll wrote:
> > This patch performs required magic and also removes code clearing
> > > timer's control registers, as exactly the same operations are
> > > performed by the timer driver few jiffies later.
> > It would be nice if these registers were documented...
>
> The best I can do is to create some more meaningful constants.
I was actually referring to the manuals - last time I looked these
register bits are not documented in the user guide for the system.
DUI0447A, 4.4.9: "You can, however, use the System Controller to change
the timer reference from 32.768kHz to 1MHz."
The only other reference to "System Controller" is at the beginning of
the document in the preface: "ARM PrimeCell System Controller (SP810)
Technical Reference Manual (ARM DDI 0254)".
Section 4.4.1 refers to the memory map, which tells me that the System
Control ARM SP810 is at CS7 + 0x1000.
Section 4.2 is titled "System control registers" but actually describes
the "System registers" described in table 4-1. 4.3 describes those
system registers. 4.4 describes the other peripherals.
DDI0254 is not published, so there's nothing on the register layout.
next prev parent reply other threads:[~2011-01-18 18:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 16:39 [PATCH] arm: Configure reference clock for Versatile Express timers Pawel Moll
2011-01-18 17:44 ` Russell King - ARM Linux
2011-01-18 18:02 ` Pawel Moll
2011-01-18 18:18 ` Russell King - ARM Linux [this message]
2011-01-18 18:28 ` Pawel Moll
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=20110118181840.GH16980@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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 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 NNTP newsgroup(s).