From: Gustavo Pimentel <gustavo.pimentel@synopsys.com>
To: Marc Zyngier <marc.zyngier@arm.com>,
Lucas Stach <l.stach@pengutronix.de>,
Gustavo Pimentel <gustavo.pimentel@synopsys.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
Jingoo Han <jingoohan1@gmail.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Tim Harvey <tharvey@gateworks.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"patchwork-lst@pengutronix.de" <patchwork-lst@pengutronix.de>
Subject: Re: [PATCH] PCI: dwc: skip MSI init if MSIs have been explicitly disabled
Date: Wed, 6 Mar 2019 09:53:40 +0000 [thread overview]
Message-ID: <9abfe0b2-edfc-a989-04d3-0dd143b7557b@synopsys.com> (raw)
In-Reply-To: <86ef7m1ji2.wl-marc.zyngier@arm.com>
Hi,
On 04/03/2019 20:18, Marc Zyngier wrote:
> Hi both,
>
> On Mon, 04 Mar 2019 19:39:45 +0000,
> Lucas Stach <l.stach@pengutronix.de> wrote:
>>
(snipped)
>>>>
>>>> As MSI and legacy IRQs are already mutually exclusive on the DWC core,
>>>> as the core won't forward any legacy IRQs once any MSI has been enabled,
>>>> users wishing to use legacy IRQs already need to explictly disable MSI
>>>> support (usually via the pci=nomsi kernel commandline option). To avoid
>>>> any issues with MSI conflicting with legacy IRQs, just skip all of the
>>>> DWC MSI initalization, including the IRQ line claim, when MSI is disabled.
>>>
>>> Does this mean that if we have a device that uses legacy IRQs, the
>>> user has to figure out to boot with "pci=nomsi"?
>>
>> As long as there is only a single device connected and there are no
>> port services things will work. If port services are active, those will
>> start to use MSIs, breaking legacy IRQs in the process.
>>
>> I've asked Synopsys if there is a workaround for this, but it seems
>> that the core is working "as designed" with no workaround for this icky
>> behavior.
>
> Is this the general DWC controller behaviour? Or something that is
> specific to a given implementation? I can't believe someone actually
> thought this is an acceptable behaviour...
>
> Gustavo, can you please check with your HW colleagues and let
> everybody know what's the official Synopsys position on this?
>
Sure, I can ask the HW team to provide me more info about this, This can take a
while. Unfortunately on my setup I only have MSI and MSI-X, therefore I can't
really test what has been statemented.
Regards,
Gustavo
next prev parent reply other threads:[~2019-03-06 10:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 16:52 [PATCH] PCI: dwc: skip MSI init if MSIs have been explicitly disabled Lucas Stach
2019-02-27 17:25 ` Fabio Estevam
2019-02-27 17:43 ` Tim Harvey
2019-02-28 13:29 ` Lorenzo Pieralisi
2019-03-01 10:10 ` Gustavo Pimentel
2019-03-01 12:29 ` Lorenzo Pieralisi
2019-03-04 19:25 ` Bjorn Helgaas
2019-03-04 19:39 ` Lucas Stach
2019-03-04 20:18 ` Marc Zyngier
2019-03-06 9:53 ` Gustavo Pimentel [this message]
2019-03-06 11:39 ` Lucas Stach
2019-03-06 15:59 ` Tim Harvey
2019-04-15 14:34 ` Gustavo Pimentel
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=9abfe0b2-edfc-a989-04d3-0dd143b7557b@synopsys.com \
--to=gustavo.pimentel@synopsys.com \
--cc=helgaas@kernel.org \
--cc=jingoohan1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=marc.zyngier@arm.com \
--cc=patchwork-lst@pengutronix.de \
--cc=tharvey@gateworks.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).