From: Dan Malek <dan@embeddededge.com>
To: Steve Rossi <srossi@labs.mot.com>
Cc: Embedded Linux PPC List <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: high priority interrupts disabled - problem found
Date: Thu, 13 Dec 2001 14:35:12 -0500 [thread overview]
Message-ID: <3C1902F0.9040807@embeddededge.com> (raw)
In-Reply-To: 3C18C309.9D234D7F@labs.mot.com
Steve Rossi wrote:
> Thanks for your followup Dan. I've got a rather straightforward "dumb" approach
> to fixing this problem - see the patch below.
Looks pretty good. My last concern is the way we overload the semantics of
the functions depending upon a driver requesting the service and the interrupt
controller using these functions. For example, a driver will request to
enable or disable one particular interrupt, while the interrupt handling functions
will need to honor the priority, as you have added. Allowing a driver request
to affect the priority mask may not be appropriate.
Thanks for the effort understanding the problem and finding a solution that
works for you. It appears to be "more right" than it was :-).
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-12-13 19:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 20:12 high priority interrupts disabled Steve Rossi
2001-12-07 23:10 ` Dan Malek
2001-12-10 18:04 ` Steve Rossi
2001-12-10 18:38 ` Wolfgang Denk
2001-12-12 15:27 ` Steve Rossi
2001-12-12 23:09 ` high priority interrupts disabled - problem found Steve Rossi
2001-12-13 4:49 ` Dan Malek
2001-12-13 15:02 ` Steve Rossi
2001-12-13 19:35 ` Dan Malek [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=3C1902F0.9040807@embeddededge.com \
--to=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=srossi@labs.mot.com \
/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;
as well as URLs for NNTP newsgroup(s).