From: Bjorn Helgaas <helgaas@kernel.org>
To: "Luís Mendes" <luis.p.mendes@gmail.com>
Cc: "Marc Zyngier" <maz@kernel.org>, "Pali Rohár" <pali@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: mvebu: Use devm_request_irq() for registering interrupt handler
Date: Mon, 3 Mar 2025 14:21:27 -0600 [thread overview]
Message-ID: <20250303202127.GA192918@bhelgaas> (raw)
In-Reply-To: <CAEzXK1qtSRVS0TYAwMHTYh=7edO604iRKuXMQNMO_MC+-hunQg@mail.gmail.com>
On Sat, Mar 01, 2025 at 07:49:23PM +0000, Luís Mendes wrote:
> ... I would like to offer my help for testing the patches with your
> guidance.
>
> ... In any way, long story short I've read in some threads about
> mvebu that PCIe is broken, and I say that it is not, the secret to
> have PCIe working is to use a good u-boot bootloader. Many recent
> u-boot versions cause the PCIe not to work on boot and I haven't
> figured out why yet. In fact my A388 systems are working with the
> amdgpu driver and an AMD Polaris, a RX 550 with 4GB VRAM. I have
> been succesfully using PCIe with this old u-boot version:
> https://github.com/SolidRun/u-boot-armada38x repo and branch
> u-boot-2013.01-15t1-clearfog.
Glad to hear that. Making this work with more versions of u-boot
would be great, and maybe we can make progress on that eventually.
For right now, I want to try to make progress on Pali's patches. I'm
pretty much in the dark as far as mvebu and IRQ details, but it might
help enlighten me if you could collect these:
- complete dmesg log, booted with "pci=nomsi"
- complete output of "sudo lspci -vv"
- contents of /proc/interrupts
- output of "grep -r . /proc/irq/"
For now just pick one of your systems, probably the solidrun one since
that sounds like one that other folks might have.
Bjorn
next prev parent reply other threads:[~2025-03-03 20:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 12:28 [PATCH] PCI: mvebu: Use devm_request_irq() for registering interrupt handler Pali Rohár
2022-06-23 13:10 ` Pali Rohár
2022-06-23 16:27 ` Bjorn Helgaas
2022-06-23 16:32 ` Pali Rohár
2022-06-23 16:49 ` Bjorn Helgaas
2022-06-23 20:31 ` Marc Zyngier
2025-02-26 21:50 ` Bjorn Helgaas
2025-03-01 19:49 ` Luís Mendes
2025-03-03 20:21 ` Bjorn Helgaas [this message]
2025-03-09 23:10 ` Luís Mendes
2025-03-11 16:24 ` Bjorn Helgaas
2025-03-12 16:25 ` Luís Mendes
2025-07-06 18:48 ` Luís Mendes
2022-07-01 14:29 ` Pali Rohár
2022-07-09 14:31 ` Pali Rohár
2022-07-09 23:44 ` Bjorn Helgaas
2022-07-10 0:06 ` Pali Rohár
2022-08-29 16:51 ` Pali Rohár
2022-09-11 15:45 ` Pali Rohár
2022-09-12 8:01 ` Lorenzo Pieralisi
2022-09-12 8:48 ` Pali Rohár
2022-09-12 8:55 ` Lorenzo Pieralisi
2022-09-12 9:03 ` Pali Rohár
2022-11-11 12:56 ` Lorenzo Pieralisi
2022-11-11 17:15 ` Pali Rohár
2022-11-14 9:33 ` Lorenzo Pieralisi
2022-11-06 23:25 ` Pali Rohár
2025-02-25 16:28 ` Bjorn Helgaas
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=20250303202127.GA192918@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=luis.p.mendes@gmail.com \
--cc=maz@kernel.org \
--cc=pali@kernel.org \
--cc=robh@kernel.org \
--cc=thomas.petazzoni@bootlin.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