From: "Krzysztof Wilczyński" <kw@linux.com>
To: Ajay Agarwal <ajayagarwal@google.com>
Cc: Jingoo Han <jingoohan1@gmail.com>,
Gustavo Pimentel <gustavo.pimentel@synopsys.com>,
Manivannan Sadhasivam <mani@kernel.org>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Rob Herring <robh@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Manu Gautam <manugautam@google.com>,
Sajid Dalvi <sdalvi@google.com>,
William McVicker <willmcvicker@google.com>,
Serge Semin <fancer.lancer@gmail.com>,
Robin Murphy <robin.murphy@arm.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v6] PCI: dwc: Strengthen the MSI address allocation logic
Date: Mon, 11 Mar 2024 03:15:30 +0900 [thread overview]
Message-ID: <20240310181530.GC2765217@rocinante> (raw)
In-Reply-To: <20240221153840.1789979-1-ajayagarwal@google.com>
Hello,
> There can be platforms that do not use/have 32-bit DMA addresses.
> The current implementation of 32-bit IOVA allocation can fail for
> such platforms, eventually leading to the probe failure.
>
> Try to allocate a 32-bit msi_data. If this allocation fails,
> attempt a 64-bit address allocation. Please note that if the
> 64-bit MSI address is allocated, then the EPs supporting 32-bit
> MSI address only will not work.
Applied to controller/dwc, thank you!
[1/1] PCI: dwc: Strengthen the MSI address allocation logic
https://git.kernel.org/pci/pci/c/f3a296405b6e
Krzysztof
next prev parent reply other threads:[~2024-03-10 18:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 15:38 [PATCH v6] PCI: dwc: Strengthen the MSI address allocation logic Ajay Agarwal
2024-02-21 17:32 ` Serge Semin
2024-02-21 23:13 ` William McVicker
2024-02-27 14:45 ` Manivannan Sadhasivam
2024-03-10 18:15 ` Krzysztof Wilczyński [this message]
2024-03-11 16:58 ` Bjorn Helgaas
2024-03-12 13:52 ` Robin Murphy
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=20240310181530.GC2765217@rocinante \
--to=kw@linux.com \
--cc=ajayagarwal@google.com \
--cc=bhelgaas@google.com \
--cc=fancer.lancer@gmail.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=jingoohan1@gmail.com \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=manugautam@google.com \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sdalvi@google.com \
--cc=willmcvicker@google.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