public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] How to add Timer Interrupt to u-boot?
Date: Mon, 30 Jul 2007 16:17:41 +0200	[thread overview]
Message-ID: <m2bqdugem2.fsf@sowhat.denx.de> (raw)
In-Reply-To: <001301c7d026$259a6ac0$3400a8c0@nmarobert> (Robert's message of "Fri\, 27 Jul 2007 16\:14\:14 +0800")

Hi Robert,

>     Everybody knows how to add Timer Interrupt to the u-boot?
> I wrote a fuction called timer0_isr(), and wanted to add it to Uboot,
> but I didn't know what to do,  Does the uboot has a funciton like
> function  request_irq() in linux kernel?

As Jerry told you, U-Boot generally avoids using interrupts.  

For some architectures however we have code to allow using interrupts,
e.g. from standalone applications.  You can look at
examples/interrupt.c which effectively was written with
cpu/mpc5xxx/interrupts.c in mind.  The latter was of course derived
from the Linux version so it shouldn't be a big problem to do
something similar for other architectures.

Cheers
  Detlev

-- 
Once the  implementation is  up and running,  it is still a trick to keep it
running.  In a normal,  closed implementation,  this is not a problem;  in a
system with metaobject protocols [..] there is the potential for spectacular
failure modes if certain situations are not properly anticipated.
                                       -- The Art of the Metaobject Protocol
--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de

      parent reply	other threads:[~2007-07-30 14:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-27  8:14 [U-Boot-Users] How to add Timer Interrupt to u-boot? Robert
2007-07-27 12:57 ` Jerry Van Baren
2007-07-30 14:17 ` Detlev Zundel [this message]

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=m2bqdugem2.fsf@sowhat.denx.de \
    --to=dzu@denx.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