All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Desfarges <simon.desfarges-s/S/64wAxt+H1Tvi1vFFB9BPR1lH4CV8@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org
Subject: Re: Interruption on PCI Bus
Date: Thu, 16 Apr 2009 17:12:00 +0200	[thread overview]
Message-ID: <49E74AC0.4000508@fr.thalesgroup.com> (raw)
In-Reply-To: <fa686aa40904160720s77efa749u56392d7027467a4a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>



Grant Likely a écrit :
> On Thu, Apr 16, 2009 at 2:50 AM, Mitch Bradley <wmb-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org> wrote:
>> Sorry for being so vague.  As the person who originally devised this
>> interrupt tree stuff, I'm pretty sure about the intention, but much less
>> sure about what specific versions of Linux and U-Boot actually do.
>>  Hopefully someone else can give you a definitive answer about that.
> 
> U-Boot doesn't really do anything with interrupts.  It usually just
> polls everything.
> 
> Linux arch/powerpc does walk the device tree to get irq routing and
> resolve to a Linux-internal virtual IRQ number.  I'm pretty sure that
> the IRQ registers are normally ignored unless something goes wrong
> with parsing the tree.  See arch/powerpc/kernel/pci-common.c and
> search for of_irq_map_pci().
> 
> g.
> 
OK, thank you very much for your answers, you are very helpful for a 
newbie like me.

So, if I understood well, of_irq_map_pci() maps the IRQs by reading the 
device tree and doesn't use the irq_line register (if there is nothing 
wrong) of the PCI device and doesn't initialize it. My problem is PCI 
device drivers are using this field (I have read this in the ldd book). 
I think I have missed something because it seems to work well like this.

Regards,
Simon Desfarges

  parent reply	other threads:[~2009-04-16 15:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-16  7:58 Interruption on PCI Bus Simon Desfarges
     [not found] ` <49E6E542.5090504-s/S/64wAxt+H1Tvi1vFFB9BPR1lH4CV8@public.gmane.org>
2009-04-16  8:50   ` Mitch Bradley
     [not found]     ` <49E6F14A.9010800-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
2009-04-16 14:20       ` Grant Likely
     [not found]         ` <fa686aa40904160720s77efa749u56392d7027467a4a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-04-16 15:12           ` Simon Desfarges [this message]
     [not found]             ` <49E74AC0.4000508-s/S/64wAxt+H1Tvi1vFFB9BPR1lH4CV8@public.gmane.org>
2009-04-16 15:15               ` Grant Likely
     [not found]                 ` <fa686aa40904160815y5eca6f5fn865762b645903c7a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-04-17  8:24                   ` Simon Desfarges

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=49E74AC0.4000508@fr.thalesgroup.com \
    --to=simon.desfarges-s/s/64waxt+h1tvi1vffb9bpr1lh4cv8@public.gmane.org \
    --cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
    --cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.