public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] armv7, timer: move static data to global_data struct
Date: Tue, 30 Nov 2010 09:10:54 +0100	[thread overview]
Message-ID: <4CF4B18E.8090901@gmail.com> (raw)
In-Reply-To: <4CF4ADCC.9060101@denx.de>

Dear Heiko Schocher,

Am 30.11.2010 08:54, schrieb Heiko Schocher:
> Hello Andreas,
> 
> Andreas Bie?mann wrote:
>> Am 30.11.2010 um 08:02 schrieb Heiko Schocher:
>>

[snip another ARM-SoC add to GD for timer]

>> can't this generalized in some way?
> 
> Good question.
> 
>> AT91 still has some values like that in global_data, yesterday David M?ller sent a patch for S3C24X0 to add some values like that to global_data ... we have a lot of arm cores out there, should each get his own style of global_data?
> 
> A common way would be better, ideas are welcome ;-)

I think Reinhard is already thinking about a solution.

> For example we could rename for the armv7 timer variants the "lastinc"
> and "lastdec" value in "lastval", so we could merge them ... if it
> is possible to find a solution for all arm cores, I don;t know ...

A short look to the arm/cpu/**/timer.c showed that most of them use a 16
bit timer to provide an 32 bit timer value. For that class of timer
implementation it would be suffucient to have a 'uint32_t
last_timer_val' and an 'uint32_t timestamp' in GD.

regards

Andreas Bie?mann

  reply	other threads:[~2010-11-30  8:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-30  7:02 [U-Boot] [PATCH] armv7, timer: move static data to global_data struct Heiko Schocher
2010-11-30  7:14 ` Andreas Bießmann
2010-11-30  7:54   ` Heiko Schocher
2010-11-30  8:10     ` Andreas Bießmann [this message]
2010-11-30  8:11     ` Minkyu Kang
2010-11-30  8:06   ` Wolfgang Denk
2010-11-30  8:00 ` Thomas Weber

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=4CF4B18E.8090901@gmail.com \
    --to=andreas.devel@googlemail.com \
    --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