From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] core ticks/timer code
Date: Tue, 31 Mar 2009 07:25:19 -0400 [thread overview]
Message-ID: <200903310725.20652.vapier@gentoo.org> (raw)
In-Reply-To: <20090331102823.A2F9883797DC@gemini.denx.de>
On Tuesday 31 March 2009 06:28:23 Wolfgang Denk wrote:
> In message Mike Frysinger wrote:
> > > I'll propose a new design with the following Requierement
> > >
> > > Generic delay function implementation
> > > - ndelay()
> > > - udelay()
> > > - mdelay()
> > >
> > > Generic helper
> > > - khz2cycles()
> > > - hz2cycles()
> > > - cs2ns()
> > >
> > > Timer API
> > > - timer_init() - setup the timer
> > > - timer_reset() - reset the timer (use in case of overflow)
> > > - get_ticks() - return the current ticks
> > > - get_cycles() - return the ticks frequency in ns
> >
> > do you have real use cases here ? i'd actually propose the opposite:
> > kill off the notion of "ticks", "cycles", and "hz". i dont think
> > ndelay() is really necessary, and mdelay() is a simple macro on top of
> > udelay(). that leaves us with really only the three functions we have
> > today: timer_init(), get_timer(), and reset_timer(). we clarify that the
> > function operates in terms of milliseconds and blam, it's all so simple
> > now.
>
> Agreed (except that we probably cannot completely throw away the
> tick; IIRC there are cases in early startup when nothing else is
> available yet).
hrm, i can see that. but you agree that most use of ticks in common code can
be converted to get_timer() ? on Blackfin systems (and it isnt alone going by
a grep), the ticks interface simply returns get_timer(0), so clearly we should
be able to convert common code to all use get_timer(0). that'd leave the
ticks interface as optional ... for the systems that need early time sources,
they can implement/use it as they need without bringing down everyone else.
i wouldnt mind starting a patch series for post 2009.05 to clean this up ...
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20090331/eb32f988/attachment.pgp
next prev parent reply other threads:[~2009-03-31 11:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-28 1:30 [U-Boot] core ticks/timer code Mike Frysinger
2009-03-28 7:07 ` Dirk Behme
2009-03-31 1:10 ` Mike Frysinger
2009-03-31 11:41 ` Scott McNutt
2009-03-31 15:48 ` Wolfgang Denk
2009-03-31 21:25 ` Scott Wood
2009-03-31 21:27 ` Wolfgang Denk
2009-04-02 12:38 ` Detlev Zundel
2009-04-02 13:09 ` Scott McNutt
2009-03-31 20:46 ` Wolfgang Denk
2009-03-31 8:17 ` Jean-Christophe PLAGNIOL-VILLARD
2009-03-31 9:13 ` Mike Frysinger
2009-03-31 10:28 ` Wolfgang Denk
2009-03-31 11:25 ` Mike Frysinger [this message]
2009-03-31 11:41 ` Jean-Christophe PLAGNIOL-VILLARD
2009-03-31 15:55 ` Dirk Behme
2009-04-02 19:16 ` Ladislav Michl
2009-04-02 21:18 ` Graeme Russ
2009-04-04 21:35 ` Wolfgang Denk
2009-03-31 15:46 ` Wolfgang Denk
2009-03-31 11:39 ` Jean-Christophe PLAGNIOL-VILLARD
2009-03-31 15:49 ` Wolfgang Denk
2009-03-31 21:32 ` Scott Wood
2009-04-04 21:14 ` Wolfgang Denk
2009-04-06 19:12 ` Scott Wood
2009-04-06 19:43 ` Wolfgang Denk
2009-03-31 20:43 ` Wolfgang Denk
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=200903310725.20652.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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