From: Will McVicker <willmcvicker@google.com>
To: "Jingoo Han" <jingoohan1@gmail.com>,
"Gustavo Pimentel" <gustavo.pimentel@synopsys.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Will McVicker" <willmcvicker@google.com>
Cc: kernel-team@android.com, Vidya Sagar <vidyas@nvidia.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/2] PCI: dwc: Add support for 64-bit MSI target addresses
Date: Wed, 10 Aug 2022 23:14:42 +0000 [thread overview]
Message-ID: <20220810231445.2242126-1-willmcvicker@google.com> (raw)
Hi All,
I have updated the series based on the reviews to use managed DMA
allocation API. This allows me to drop the msi_page parameter from struct
dw_pcie_rp. Please take a look and let me know if you have any concerns.
Thanks again for the reviews!
Regards,
Will
Will McVicker (2):
PCI: dwc: drop dependency on ZONE_DMA32
PCI: dwc: add support for 64-bit MSI target address
v3:
* Switched to a managed DMA allocation.
* Simplified the DMA allocation cleanup.
* Dropped msi_page from struct dw_pcie_rp.
* Allocating a u64 instead of a full page.
v2:
* Fixed build error caught by kernel test robot
* Fixed error handling reported by Isaac Manjarres
.../pci/controller/dwc/pcie-designware-host.c | 42 +++++++++----------
drivers/pci/controller/dwc/pcie-designware.c | 9 ++++
drivers/pci/controller/dwc/pcie-designware.h | 2 +-
3 files changed, 29 insertions(+), 24 deletions(-)
base-commit: aeb6e6ac18c73ec287b3b1e2c913520699358c13
--
2.37.1.559.g78731f0fdb-goog
next reply other threads:[~2022-08-10 23:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 23:14 Will McVicker [this message]
2022-08-10 23:14 ` [PATCH v3 1/2] PCI: dwc: drop dependency on ZONE_DMA32 Will McVicker
2022-08-10 23:14 ` [PATCH v3 2/2] PCI: dwc: add support for 64-bit MSI target address Will McVicker
2022-08-11 16:07 ` Bjorn Helgaas
2022-08-11 16:31 ` William McVicker
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=20220810231445.2242126-1-willmcvicker@google.com \
--to=willmcvicker@google.com \
--cc=bhelgaas@google.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=jingoohan1@gmail.com \
--cc=kernel-team@android.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=robh@kernel.org \
--cc=vidyas@nvidia.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