From: Chetan Nanda <chetannanda@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] question about interrupt
Date: Tue, 20 May 2008 15:10:13 +0530 [thread overview]
Message-ID: <7f245da80805200240o7dde7b3bl83875b910d69ad08@mail.gmail.com> (raw)
In-Reply-To: <20080520092345.D27B224312@gemini.denx.de>
On Tue, May 20, 2008 at 2:53 PM, Wolfgang Denk <wd@denx.de> wrote:
> In message <7f245da80805200136y297e5309k110f1b193981ac16@mail.gmail.com> you wrote:
>>
>> as i have mentioned, u-boot do not handle any interrupt, and neither
>
> In this general form, the statement is wrong.
>
> Depending on architecture, U-Boot does implement and use interrupts.
> It even exports an interface to standalone applications which allows
> to register custom interrupt handlers.
So if someone enable a interrupt and handled it properly then at the
time of interrupt handler will be called, but how then control reaches
back to u-boot original task that was running prior to interrupt
delivery? I mean who is taking care of context switch at the time of
interrupts?
>
> It's just just most U-Boot drivers do not use interrupts but polling
> mode - note that there are exceptions from this rule, too.
>
> Best regards,
>
> Wolfgang Denk
>
> --
> DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
> A modem is a baudy house.
>
next prev parent reply other threads:[~2008-05-20 9:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 2:11 [U-Boot-Users] question about interrupt loody
2008-05-20 5:18 ` Chetan Nanda
2008-05-20 5:53 ` loody
2008-05-20 8:36 ` Chetan Nanda
2008-05-20 9:23 ` Wolfgang Denk
2008-05-20 9:40 ` Chetan Nanda [this message]
2008-05-20 12:31 ` Wolfgang Denk
2008-05-20 8:36 ` Andreas Schweigstill
2008-05-20 9:25 ` 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=7f245da80805200240o7dde7b3bl83875b910d69ad08@mail.gmail.com \
--to=chetannanda@gmail.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