public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 11/11] RFC: ARM: get PCI device IRQs from device tree
Date: Thu, 4 Apr 2013 15:27:52 +0000	[thread overview]
Message-ID: <201304041527.52400.arnd@arndb.de> (raw)
In-Reply-To: <1365087696-9548-12-git-send-email-linus.walleij@linaro.org>

On Thursday 04 April 2013, Linus Walleij wrote:
> This adds the interrupt-map property to the PCIv3 DTS file
> and makes the bridge obtain mappings from the device tree.
> 
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> This currently bugs out - when trying to get the IRQs for
> devices of_irq_map_pci() reads the IRQ pin from the PCI config
> space successfully, then comes to trying to look up the parent
> PCI device by checking pdev->bus->self, which is NULL, then
> tries to treat it as a bridge doing pci_bus_to_OF_node(pdev->bus)
> which also results in NULL and it bails out.
> 
> No clue why this is so - some problem with the parent of this
> bus not being a PCI device in itself? Help.

All the PowerPC implementations I remember had the PCI bus
as a device under the root node. It's very possible that it's
just a bug in of_irq_map_pci().

	Arnd

       reply	other threads:[~2013-04-04 15:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1365087696-9548-1-git-send-email-linus.walleij@linaro.org>
     [not found] ` <1365087696-9548-2-git-send-email-linus.walleij@linaro.org>
     [not found]   ` <1365087696-9548-3-git-send-email-linus.walleij@linaro.org>
     [not found]     ` <1365087696-9548-4-git-send-email-linus.walleij@linaro.org>
     [not found]       ` <1365087696-9548-5-git-send-email-linus.walleij@linaro.org>
     [not found]         ` <1365087696-9548-6-git-send-email-linus.walleij@linaro.org>
     [not found]           ` <1365087696-9548-7-git-send-email-linus.walleij@linaro.org>
     [not found]             ` <1365087696-9548-8-git-send-email-linus.walleij@linaro.org>
     [not found]               ` <1365087696-9548-9-git-send-email-linus.walleij@linaro.org>
     [not found] ` <1365087696-9548-11-git-send-email-linus.walleij@linaro.org>
     [not found]   ` <1365087696-9548-12-git-send-email-linus.walleij@linaro.org>
2013-04-04 15:27     ` Arnd Bergmann [this message]
2013-04-07 18:43       ` [PATCH 11/11] RFC: ARM: get PCI device IRQs from device tree Linus Walleij
2013-04-11 20:27     ` Linus Walleij
2013-04-12  8:22       ` Andrew Murray
2013-04-12  8:51         ` Linus Walleij
2013-04-04 15:29 ` [PATCH 00/11] ARM: integrator PCI DT adaption Arnd Bergmann

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=201304041527.52400.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.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