Input: da9063_onkey - avoid explicitly setting input's parent

devm_input_allocate_device() already sets parent of the new input
device, there's no need to set it up explicitly.

Reviewed-by: Biju Das <biju.das.jz@bp.renesas.com>
Link: https://lore.kernel.org/r/ZYOseYfVgg0Ve6Zl@google.com
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

diff --git a/drivers/input/misc/da9063_onkey.c b/drivers/input/misc/da9063_onkey.c
index ce499c28a7b267a22d755844603312f48c96a383..c338765e0ecd032ab541ad70020cec84bea9c296 100644 (file)
--- a/drivers/input/misc/da9063_onkey.c
+++ b/drivers/input/misc/da9063_onkey.c
@@ -211,7 +211,6 @@ static int da9063_onkey_probe(struct platform_device *pdev)
        snprintf(onkey->phys, sizeof(onkey->phys), "%s/input0",
                 onkey->config->name);
        onkey->input->phys = onkey->phys;
-       onkey->input->dev.parent = &pdev->dev;
 
        input_set_capability(onkey->input, EV_KEY, KEY_POWER);