The hi655x-regulator driver consumes a similarly named platform device.
Adding that to the module device table, allows modprobe to locate this
driver once the device is created. Without this the sd/mmc device fails
to start, resulting in boot failures.

Signed-off-by: Jeremy Linton <lintonrjer...@gmail.com>
---
 drivers/regulator/hi655x-regulator.c | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/drivers/regulator/hi655x-regulator.c 
b/drivers/regulator/hi655x-regulator.c
index 065c100..36ae54b 100644
--- a/drivers/regulator/hi655x-regulator.c
+++ b/drivers/regulator/hi655x-regulator.c
@@ -214,7 +214,14 @@ static int hi655x_regulator_probe(struct platform_device 
*pdev)
        return 0;
 }
 
+static const struct platform_device_id hi655x_regulator_table[] = {
+       { .name = "hi655x-regulator" },
+       {},
+};
+MODULE_DEVICE_TABLE(platform, hi655x_regulator_table);
+
 static struct platform_driver hi655x_regulator_driver = {
+       .id_table = hi655x_regulator_table,
        .driver = {
                .name   = "hi655x-regulator",
        },
-- 
2.10.2

Reply via email to