mfd: core: propagate device properties to sub devices drivers

In the similar way like we do for the platform data we propagate the device
properties. For example, in case of Intel LPSS drivers we may provide a
specific property to tell the actual device driver an additional information
such as platform name.

Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

diff --git a/drivers/mfd/mfd-core.c b/drivers/mfd/mfd-core.c
index 60b60dc63dddbc610d0ac1cf02111066b4af5095..88bd1b1e47bedb650c83771de09d7a9e85316ee4 100644 (file)
--- a/drivers/mfd/mfd-core.c
+++ b/drivers/mfd/mfd-core.c
@@ -14,6 +14,7 @@
 #include <linux/kernel.h>
 #include <linux/platform_device.h>
 #include <linux/acpi.h>
+#include <linux/property.h>
 #include <linux/mfd/core.h>
 #include <linux/pm_runtime.h>
 #include <linux/slab.h>
@@ -192,6 +193,12 @@ static int mfd_add_device(struct device *parent, int id,
                        goto fail_alias;
        }
 
+       if (cell->pset) {
+               ret = platform_device_add_properties(pdev, cell->pset);
+               if (ret)
+                       goto fail_alias;
+       }
+
        ret = mfd_platform_add_cell(pdev, cell, usage_count);
        if (ret)
                goto fail_alias;

diff --git a/include/linux/mfd/core.h b/include/linux/mfd/core.h
index 27dac3ff18b949a0c32d508a3830f676992fc14c..bc6f7e00fb3de33438759c6c88184b7385dc86b7 100644 (file)
--- a/include/linux/mfd/core.h
+++ b/include/linux/mfd/core.h
@@ -17,6 +17,7 @@
 #include <linux/platform_device.h>
 
 struct irq_domain;
+struct property_set;
 
 /* Matches ACPI PNP id, either _HID or _CID, or ACPI _ADR */
 struct mfd_cell_acpi_match {
@@ -44,6 +45,10 @@ struct mfd_cell {
        /* platform data passed to the sub devices drivers */
        void                    *platform_data;
        size_t                  pdata_size;
+
+       /* device properties passed to the sub devices drivers */
+       const struct property_set *pset;
+
        /*
         * Device Tree compatible string
         * See: Documentation/devicetree/usage-model.txt Chapter 2.2 for details