From: Trent Piepho <tpiepho@impinj.com>
To: "l.stach@pengutronix.de" <l.stach@pengutronix.de>,
"andrew.smirnov@gmail.com" <andrew.smirnov@gmail.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Cc: "hongxing.zhu@nxp.com" <hongxing.zhu@nxp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"cphealy@gmail.com" <cphealy@gmail.com>,
"linux-imx@nxp.com" <linux-imx@nxp.com>,
"aisheng.dong@nxp.com" <aisheng.dong@nxp.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"leonard.crestez@nxp.com" <leonard.crestez@nxp.com>
Subject: Re: [PATCH] PCI: controller: dwc: Make PCI_IMX6 depend on PCIEPORTBUS
Date: Thu, 6 Dec 2018 20:20:01 +0000 [thread overview]
Message-ID: <1544127600.18519.175.camel@impinj.com> (raw)
In-Reply-To: <1544092136.3709.57.camel@pengutronix.de>
On Thu, 2018-12-06 at 11:28 +0100, Lucas Stach wrote:
> Am Mittwoch, den 05.12.2018, 23:45 -0800 schrieb Andrey Smirnov:
> > Building a kernel with CONFIG_PCI_IMX6=y, but CONFIG_PCIEPORTBUS=n
> > produces a system where built-in PCIE bridge (16c3:abcd) isn't
> > bound
> > to pcieport driver. This, in turn, results in a PCIE bus that is
> > capable of enumerating attached PCIE device, but lacks functional
> > interrupt support.
>
> This is odd. AFAIK PCI port services are a totally optional thing and
> them being absent should not lead to a non-functional PCI bus. So I
> would really like to see some deeper analysis what is going on here.
I noticed this previously,
https://www.spinics.net/lists/linux-pci/msg77840.html
What happened was that PCIEPORTBUS *was* selected by all the platform
dwc drivers and those selections were removed in:
commit f3fdfc4ac3a26865e84627a7fe08a906081e5abc
Author: Bjorn Helgaas <bhelgaas@google.com>
Date: Fri May 18 15:08:36 2018 -0500
PCI: Remove host driver Kconfig selection of CONFIG_PCIEPORTBUS
Host bridge drivers do not use the portdrv interfaces (struct pcie_device,
struct pcie_port_service_driver, pcie_port_service_register(), etc), and
they should not select CONFIG_PCIEPORTBUS.
I encountered this when a kernel defconfig that previously turned on
PCIEPORTBUS stopped turning in on, resulting in the situation that
Andrey describes: no errors, device present, but no MSI interrupts.
The in kernel defconfigs (mine not being one of those) for all the dwc
pcie users should probably be refreshed to enable pcieportbus.
It seems appropriate that the port services are optional and it's
unfortunate that the kernel defconfig system resolves in the change in
this manner, vs keeping pcieportbus on by default. I do know why it is
this way and I don't think there is any great solution there.
It has never been clear to me why pcieportbus was necessary for MSI.
next prev parent reply other threads:[~2018-12-06 20:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 7:45 [PATCH] PCI: controller: dwc: Make PCI_IMX6 depend on PCIEPORTBUS Andrey Smirnov
2018-12-06 8:10 ` Baruch Siach
2018-12-06 15:45 ` Robert Hancock
2018-12-06 15:50 ` Lucas Stach
2018-12-06 16:10 ` Robert Hancock
2018-12-06 21:41 ` Robert Hancock
2018-12-06 10:28 ` Lucas Stach
2018-12-06 20:20 ` Trent Piepho [this message]
2018-12-07 4:55 ` Andrey Smirnov
2018-12-07 13:11 ` Niklas Cassel
2018-12-07 23:57 ` Andrey Smirnov
2018-12-12 8:11 ` Richard Zhu
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=1544127600.18519.175.camel@impinj.com \
--to=tpiepho@impinj.com \
--cc=aisheng.dong@nxp.com \
--cc=andrew.smirnov@gmail.com \
--cc=bhelgaas@google.com \
--cc=cphealy@gmail.com \
--cc=hongxing.zhu@nxp.com \
--cc=l.stach@pengutronix.de \
--cc=leonard.crestez@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.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