Commit ca3704c2 authored by Charles Keepax's avatar Charles Keepax Committed by Dmitry Torokhov

Input: arizona-haptic - don't assign input_dev parent

We shouldn't assign the parent device of the input_dev to be the
parent MFD device, because this will be used for devres which causes
input_unregister_device to run after the haptics device has been
removed, since it is itself a child of the MFD device. The default
of using the haptics device itself as the parent is correct.
Signed-off-by: default avatarCharles Keepax <ckeepax@opensource.wolfsonmicro.com>
Signed-off-by: default avatarDmitry Torokhov <dmitry.torokhov@gmail.com>
parent 7eb5ca09
...@@ -178,7 +178,6 @@ static int arizona_haptics_probe(struct platform_device *pdev) ...@@ -178,7 +178,6 @@ static int arizona_haptics_probe(struct platform_device *pdev)
input_set_drvdata(haptics->input_dev, haptics); input_set_drvdata(haptics->input_dev, haptics);
haptics->input_dev->name = "arizona:haptics"; haptics->input_dev->name = "arizona:haptics";
haptics->input_dev->dev.parent = pdev->dev.parent;
haptics->input_dev->close = arizona_haptics_close; haptics->input_dev->close = arizona_haptics_close;
__set_bit(FF_RUMBLE, haptics->input_dev->ffbit); __set_bit(FF_RUMBLE, haptics->input_dev->ffbit);
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment