浏览代码

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: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Charles Keepax 9 年之前
父节点
当前提交
ca3704c23a
共有 1 个文件被更改,包括 0 次插入1 次删除
  1. 0 1
      drivers/input/misc/arizona-haptics.c

+ 0 - 1
drivers/input/misc/arizona-haptics.c

@@ -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);