From: Jens Scharsig <js_at_ng@scharsoft.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 7/9 V3] prepare joining at91rm9200 into at91
Date: Wed, 03 Feb 2010 22:44:39 +0100 [thread overview]
Message-ID: <4B69EE47.205@scharsoft.de> (raw)
In-Reply-To: <4B64DEC8.8030905@windriver.com>
>> + /* reset time */
>> + at91_tc_t *tc = (at91_tc_t *) AT91_TC_BASE;
>> + lastinc = readl(&tc->tc[0].cv) & 0x0000ffff;
>> + timestamp = 0;
>
> rm9200 did not zero out the top bits
> Is this needed ?
>
The datasheet say not, is bit 16 to 31 of cv high or low.
>> +typedef struct at91_mc {
>> + u32 rcr; /* 0x00 MC Remap Control Register */
next prev parent reply other threads:[~2010-02-03 21:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 11:03 [U-Boot] [PATCH 7/9 V3] prepare joining at91rm9200 into at91 Jens Scharsig
2010-01-31 1:37 ` Tom
2010-01-31 15:33 ` Jens Scharsig
2010-02-03 21:44 ` Jens Scharsig [this message]
2010-02-03 21:47 ` [U-Boot] [PATCH 7/9 V4] " Jens Scharsig
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=4B69EE47.205@scharsoft.de \
--to=js_at_ng@scharsoft.de \
--cc=u-boot@lists.denx.de \
/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