From: Peter Hurley <peter@hurleysoftware.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI, PCI: Get PRT entry during acpi_pci_enable_irq()
Date: Tue, 12 Feb 2013 21:20:10 -0500 [thread overview]
Message-ID: <1360722010.3604.3.camel@thor.lan> (raw)
In-Reply-To: <1360696283-20313-1-git-send-email-yinghai@kernel.org>
On Tue, 2013-02-12 at 11:11 -0800, Yinghai Lu wrote:
> Peter Hurley found "irq 18 nobody cared" with pci-next, and dmesg has
>
> [ 8.983246] pci 0000:00:1e.0: can't derive routing for PCI INT A
> [ 8.983600] snd_ctxfi 0000:09:02.0: PCI INT A: no GSI - using ISA IRQ 5
>
> bisect to
> | commit 4f535093cf8f6da8cfda7c36c2c1ecd2e9586ee4
> | PCI: Put pci_dev in device tree as early as possible
>
> It turns out we need to call acpi_pci_irq_add_prt() after the pci bridges
> are scanned.
>
> Bjorn said:
> The bus number binding means acpi_pci_irq_add_prt() has to happen
> after enumerating everything below a bridge, and it will prevent us
> from doing any bus number reassignment for hotplug.
>
> I think we should remove the bus numbers from the cached _PRT (or
> maybe even remove the _PRT caching completely). When we enable a PCI
> device's IRQ, we should search up the PCI device tree looking for a
> _PRT associated with each node, and applying normal PCI bridge
> swizzling when we don't find a _PRT. I think this can be done without
> using PCI bus numbers at all.
>
> So here we try to remove _PRT caching completely.
>
> -v2: check !handle early.
>
> Reported-and-tested-by: Peter Hurley <peter@hurleysoftware.com>
Actually true now :)
Reported-and-tested-by: Peter Hurley <peter@hurleysoftware.com>
Regards and thanks again,
Peter Hurley
PS - I just happened to see this version on the list. Would you please
cc me on any future versions?
next prev parent reply other threads:[~2013-02-13 2:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44L0.1302051520220.2245-100000@iolanthe.rowland.org>
[not found] ` <1360466060.3703.15.camel@thor.lan>
[not found] ` <1360506199.3461.5.camel@thor.lan>
[not found] ` <CAE9FiQX0Jzqi=Dy=r3MoU9vK7HgAf+919LvbgLygW7VH3O4=bg@mail.gmail.com>
[not found] ` <CAE9FiQX5wQ8zFzPfgmvm0BESyLVxzDRQ33XPgj+QjBZ0kxuHXg@mail.gmail.com>
[not found] ` <1360587768.3454.2.camel@thor.lan>
[not found] ` <CAE9FiQWUZ3BgLOtcGePppLzWBv-uR8L+7abditH2MNA7zZW-WA@mail.gmail.com>
[not found] ` <CAE9FiQXcgxY_vW6gjqU7Jtxc71J=sKt_2SPsN8x1O9EfDRN_0g@mail.gmail.com>
[not found] ` <CAE9FiQXnb-op9vsQJroMisDQt_-X2UpBB1R_WJ1Lifnk5pPpGg@mail.gmail.com>
2013-02-11 22:41 ` [Bisected] [-next-20130204] usb/hcd: irq 18: nobody cared Bjorn Helgaas
2013-02-12 0:08 ` Yinghai Lu
2013-02-12 3:21 ` Yinghai Lu
2013-02-12 19:11 ` [PATCH] ACPI, PCI: Get PRT entry during acpi_pci_enable_irq() Yinghai Lu
2013-02-12 20:22 ` Rafael J. Wysocki
2013-02-15 0:50 ` Yinghai Lu
2013-02-16 0:39 ` Bjorn Helgaas
2013-02-16 1:26 ` Yinghai Lu
2013-02-16 1:37 ` Yinghai Lu
2013-02-19 18:51 ` Bjorn Helgaas
2013-02-13 2:20 ` Peter Hurley [this message]
2013-02-13 2:42 ` Yinghai Lu
2013-02-13 3:18 ` Peter Hurley
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=1360722010.3604.3.camel@thor.lan \
--to=peter@hurleysoftware.com \
--cc=bhelgaas@google.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=yinghai@kernel.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).