From: Xupei Liang <tliang@yahoo.com>
To: Eugene Surovegin <ebs@ebshome.net>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: IDE driver support in PPC440
Date: Thu, 15 May 2003 07:56:17 -0700 (PDT) [thread overview]
Message-ID: <20030515145617.89401.qmail@web11005.mail.yahoo.com> (raw)
In-Reply-To: <5.1.0.14.2.20030514094842.029fc6c0@mail.ebshome.net>
Hi, Eugene,
Thank you for pointing out this. I have updated
ibm440.h and ppc4xx_pic.c as well. Now, in
ppc405_disable_and_ack(), besides acking the
interrupt, it will clear UIC0_UIC1NC bit in the
UIC0_SR register as well. That works for my
board.
Thanks.
Regards,
Terry L.
--- Eugene Surovegin <ebs@ebshome.net> wrote:
>
> At 08:20 AM 5/14/2003, Xupei Liang wrote:
> >Hi, Eugene,
> >
> >The IRQ7 is setup as level trigger and active low.
>
> <snip>
>
> >This time, ppc405_pic_get_irq() returns irq 64
> because
> >the routine knows that all interrupts have been
> >disabled (I have looked at UIC_ER0 and UIC_ER1
> >and verified that is the case).
>
> No, this is not correct, it should return -1.
> Otherwise do_IRQ will spin forever (see
> arch/ppc/kernel/irq.c)
>
> Here is the code in question:
>
> int
> ppc405_pic_get_irq(struct pt_regs *regs)
> {
>
> ........
>
> if (irq == (NR_UIC_IRQS * NR_UICS))
> irq = -1;
>
> #ifdef UIC_DEBUG
> printk("ppc405_pic_get_irq - irq %d bit
> 0x%x\n", irq, bits);
> #endif
>
> return (irq);
> }
>
>
> Check, that NR_UIC_IRQS == 32 (defined in
> include/arch-ppc/irq.h)
> and NR_UICS == 2 (defined in
> /include/arch-ppc/ibm440.h) in your tree.
>
> They weren't set correctly in some early versions of
> 440GP code.
>
> Eugene
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-05-15 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 5:15 IDE driver support in PPC440 Xupei Liang
2003-05-14 6:56 ` Eugene Surovegin
2003-05-14 15:20 ` Xupei Liang
2003-05-14 16:57 ` Eugene Surovegin
2003-05-15 14:56 ` Xupei Liang [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-14 16:09 Ralph Blach
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=20030515145617.89401.qmail@web11005.mail.yahoo.com \
--to=tliang@yahoo.com \
--cc=ebs@ebshome.net \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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).