From: Michael Kelley <mikelley@microsoft.com>
To: sthemmin@microsoft.com, kys@microsoft.com,
haiyangz@microsoft.com, wei.liu@kernel.org, decui@microsoft.com,
rafael@kernel.org, lenb@kernel.org, lorenzo.pieralisi@arm.com,
robh@kernel.org, kw@linux.com, bhelgass@google.com, hch@lst.de,
m.szyprowski@samsung.com, robin.murphy@arm.com,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hyperv@vger.kernel.org, linux-pci@vger.kernel.org,
iommu@lists.linux-foundation.org
Cc: mikelley@microsoft.com
Subject: [PATCH 1/4] ACPI: scan: Export acpi_get_dma_attr()
Date: Thu, 17 Mar 2022 09:12:40 -0700 [thread overview]
Message-ID: <1647533563-2170-2-git-send-email-mikelley@microsoft.com> (raw)
In-Reply-To: <1647533563-2170-1-git-send-email-mikelley@microsoft.com>
Export acpi_get_dma_attr() so that it can be used by the Hyper-V
VMbus driver, which may be built as a module. The related function
acpi_dma_configure_id() is already exported.
Signed-off-by: Michael Kelley <mikelley@microsoft.com>
---
drivers/acpi/scan.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/acpi/scan.c b/drivers/acpi/scan.c
index 1331756..9f3c88f 100644
--- a/drivers/acpi/scan.c
+++ b/drivers/acpi/scan.c
@@ -1489,6 +1489,7 @@ enum dev_dma_attr acpi_get_dma_attr(struct acpi_device *adev)
else
return DEV_DMA_NON_COHERENT;
}
+EXPORT_SYMBOL_GPL(acpi_get_dma_attr);
/**
* acpi_dma_get_range() - Get device DMA parameters.
--
1.8.3.1
next prev parent reply other threads:[~2022-03-17 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 16:12 [PATCH 0/4] Fix coherence for VMbus and PCI pass-thru devices in Hyper-V VM Michael Kelley
2022-03-17 16:12 ` Michael Kelley [this message]
2022-03-17 16:12 ` [PATCH 2/4] dma-mapping: Add wrapper function to set dma_coherent Michael Kelley
2022-03-17 16:12 ` [PATCH 3/4] Drivers: hv: vmbus: Propagate VMbus coherence to each VMbus device Michael Kelley
2022-03-17 16:12 ` [PATCH 4/4] PCI: hv: Propagate coherence from VMbus device to PCI device Michael Kelley
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=1647533563-2170-2-git-send-email-mikelley@microsoft.com \
--to=mikelley@microsoft.com \
--cc=bhelgass@google.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=kw@linux.com \
--cc=kys@microsoft.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=m.szyprowski@samsung.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sthemmin@microsoft.com \
--cc=wei.liu@kernel.org \
/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