From: Robert Hancock <hancock@sedsystems.ca>
To: Baruch Siach <baruch@tkos.co.il>,
Andrey Smirnov <andrew.smirnov@gmail.com>
Cc: linux-pci@vger.kernel.org, "A.s. Dong" <aisheng.dong@nxp.com>,
Richard Zhu <hongxing.zhu@nxp.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-imx@nxp.com,
bhelgaas@google.com, Leonard Crestez <leonard.crestez@nxp.com>,
cphealy@gmail.com, l.stach@pengutronix.de,
Trent Piepho <tpiepho@impinj.com>
Subject: Re: [PATCH] PCI: controller: dwc: Make PCI_IMX6 depend on PCIEPORTBUS
Date: Thu, 6 Dec 2018 09:45:47 -0600 [thread overview]
Message-ID: <5a3543f2-fe58-221d-694f-0f98a643edfc@sedsystems.ca> (raw)
In-Reply-To: <87o99zjcsc.fsf@tkos.co.il>
On 2018-12-06 2:10 a.m., Baruch Siach wrote:
> Hi Andrey,
>
> Adding Robert Hancock who reported[1] on a PCIe MSI issue with i.MX6.
>
> Andrey Smirnov writes:
>
>> 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.
>
> Robert, does that fix your issue?
Unfortunately, no.. in fact the situation on my setup is even worse with
CONFIG_PCIEPORTBUS enabled: Not only does MSI still not function, but
now INTx interrupts are somehow broken as well - no interrupts are
received. The IRQ information shown in /proc/interrupts is correct, but
the count remains stubbornly at 0.
So given that outcome, I don't think we should add this as a hard
dependency until we can figure out what is going on, as it seems to
regress working setups.
>
>> Signed-off-by: Andrey Smirnov <andrew.smirnov@gmail.com>
>> ---
>>
>> Assuming this is a reasonable dependency, shold this be done to more
>> than just i.MX6 driver?
>>
>> drivers/pci/controller/dwc/Kconfig | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/pci/controller/dwc/Kconfig b/drivers/pci/controller/dwc/Kconfig
>> index 2b139acccf32..44ededbeab85 100644
>> --- a/drivers/pci/controller/dwc/Kconfig
>> +++ b/drivers/pci/controller/dwc/Kconfig
>> @@ -92,6 +92,7 @@ config PCI_IMX6
>> bool "Freescale i.MX6 PCIe controller"
>> depends on SOC_IMX8MQ || SOC_IMX6Q || (ARM && COMPILE_TEST)
>> depends on PCI_MSI_IRQ_DOMAIN
>> + depends on PCIEPORTBUS
>
> This effectively disables PCIe in imx_v6_v7_defconfig, since
> CONFIG_PCIEPORTBUS is not enabled there. Maybe do 'select' instead?
>
>> Select PCIE_DW_HOST
>>
>> config PCIE_SPEAR13XX
>
> baruch
>
> [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2018-November/614800.html
>
> --
> http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
> =}------------------------------------------------ooO--U--Ooo------------{=
> - baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
>
--
Robert Hancock
Senior Software Developer
SED Systems
Email: hancock@sedsystems.ca
next prev parent reply other threads:[~2018-12-06 16:04 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 [this message]
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
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=5a3543f2-fe58-221d-694f-0f98a643edfc@sedsystems.ca \
--to=hancock@sedsystems.ca \
--cc=aisheng.dong@nxp.com \
--cc=andrew.smirnov@gmail.com \
--cc=baruch@tkos.co.il \
--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 \
--cc=tpiepho@impinj.com \
/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).