Merge tag 'driver-core-5.19-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git...

[people/ms/linux.git] / include / linux / platform_device.h

diff --git a/include/linux/platform_device.h b/include/linux/platform_device.h
index 582d83ed9a91fb451e0e4dd5b7ddfc83eb999ec8..b0d5a253156ecee00fd1c4429d19ef9f1822bc78 100644 (file)
--- a/include/linux/platform_device.h
+++ b/include/linux/platform_device.h
@@ -214,6 +214,14 @@ struct platform_driver {
        struct device_driver driver;
        const struct platform_device_id *id_table;
        bool prevent_deferred_probe;
+       /*
+        * For most device drivers, no need to care about this flag as long as
+        * all DMAs are handled through the kernel DMA API. For some special
+        * ones, for example VFIO drivers, they know how to manage the DMA
+        * themselves and set this flag so that the IOMMU layer will allow them
+        * to setup and manage their own I/O address space.
+        */
+       bool driver_managed_dma;
 };
 
 #define to_platform_driver(drv)        (container_of((drv), struct platform_driver, \
@@ -332,8 +340,6 @@ extern int platform_pm_restore(struct device *dev);
 #define platform_pm_restore            NULL
 #endif
 
-extern int platform_dma_configure(struct device *dev);
-
 #ifdef CONFIG_PM_SLEEP
 #define USE_PLATFORM_PM_SLEEP_OPS \
        .suspend = platform_pm_suspend, \