From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: "Shmuel H." <sh@tkos.co.il>
Cc: "Jason Cooper" <jason@lakedaemon.net>,
"Marek Behún" <marek.behun@nic.cz>,
"Baruch Siach" <baruch@tkos.co.il>,
"Chris ackham" <chris.packham@alliedtelesis.co.nz>,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH] pci: pci-mvebu: setup BAR0 to internal-regs
Date: Wed, 10 Jun 2020 12:27:50 +0200 [thread overview]
Message-ID: <20200610122750.389c990f@windsurf.home> (raw)
In-Reply-To: <df64c0b9-cba7-c92e-c32d-804a75796f83@tkos.co.il>
Hello,
On Tue, 9 Jun 2020 14:21:07 +0300
"Shmuel H." <sh@tkos.co.il> wrote:
> Unfortunately, there is almost no documentation about the purpose of
> this register apart from this cryptic sentence:
>
> "BAR0 is dedicated to internal register access" (Marvell a38x
> functional docs, section 19.8).
>
> I can only assume that only specific devices trigger the need for the
> PCIe controller to access the SoC's internal registers and therefore
> will fail to operate properly.
In fact, section 10.2.6 of the Armada XP datasheet, about MSI/MSI-X
support gives a hint: in order for the device to do a write to the MSI
doorbell address, it needs to write to a register in the "internal
registers" space". So it makes a lot of sense that this BAR0 has to be
configured.
Could you try to boot your system without your patch, and with the
pci=nomsi argument on the kernel command line ? This will prevent the
driver from using MSI, so it should fallback to legacy IRQs. If that
works, then we have the confirmation the issue is MSI related. This
will be useful just to have a good commit message that explains the
problem, because otherwise I am fine with your patch.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-06-10 10:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 14:40 [RFC PATCH] pci: pci-mvebu: setup BAR0 to internal-regs Shmuel Hazan
2020-06-08 19:43 ` Thomas Petazzoni
2020-06-09 11:21 ` Shmuel H.
2020-06-10 10:27 ` Thomas Petazzoni [this message]
2020-06-10 11:09 ` Shmuel H.
2020-06-10 14:17 ` Shmuel H.
2020-06-10 19:20 ` Thomas Petazzoni
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=20200610122750.389c990f@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=baruch@tkos.co.il \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=marek.behun@nic.cz \
--cc=sh@tkos.co.il \
/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