linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Leonid <Leonid@a-k-a.net>
Cc: Balajee Premraj <balajee@a-k-a.net>, linuxppc-embedded@ozlabs.org
Subject: Re: 2 PCI devices behind PCI bridge on Yosemite board.
Date: Thu, 30 Nov 2006 14:07:50 -0600	[thread overview]
Message-ID: <456F3A16.7070204@freescale.com> (raw)
In-Reply-To: <406A31B117F2734987636D6CCC93EE3C99D6F2@ehost011-3.exch011.intermedia.net>

Leonid wrote:
> Problem starts when I work with Dreamchip. Interrupt arrives from it and
> kernel doesn't know what to do with this interrupt and it gets disabled.
> Looks like interrupt doesn't get acknowledged properly.
> 
> I tried to register Dreamchip PCI device by 2 ways:
> 
> 1) I request interrupt and provide as interrupt handler empty function:
> 
> irqreturn_t snd_dream_interrupt(int irq, void *dev_id, struct pt_regs
> *regs)
> {
> 	return IRQ_NONE;
> }

You didn't deal with the source of the interrupt.  Since it's apparently 
level-triggered, the interrupt just comes right back.

> 2) Because I don't need interrupt from Dreamchip anyway, I tried don't
> request interrupt upon Dreamchip PCI driver registration. Result was the
> same though kernel output different:

Not requesting the IRQ doesn't stop the device from asserting it.

> Any ideas what I have done wrong? Can I just tell to the bridge don't
> interrupt CPU if Dreamchip is interrupting?

No, because both devices share the same physical IRQ line.  The PIC 
can't tell which device is asserting it.  You need to either provide a 
real IRQ handler for the Dreamchip, or tell the Dreamchip itself to mask 
the IRQ.

-Scott

  reply	other threads:[~2006-11-30 20:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-30 19:52 2 PCI devices behind PCI bridge on Yosemite board Leonid
2006-11-30 20:07 ` Scott Wood [this message]
2006-11-30 20:18   ` Leonid
2006-11-30 20:26     ` Scott Wood

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=456F3A16.7070204@freescale.com \
    --to=scottwood@freescale.com \
    --cc=Leonid@a-k-a.net \
    --cc=balajee@a-k-a.net \
    --cc=linuxppc-embedded@ozlabs.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).