summaryrefslogtreecommitdiffstats
path: root/Kconfig
diff options
context:
space:
mode:
authorSrinivas Pandruvada <srinivas.pandruvada@linux.intel.com>2015-05-07 14:26:34 -0700
committerJiri Kosina <jkosina@suse.cz>2015-05-12 14:13:20 +0200
commit2d94e5224e81c58986a8cf44a3bf4830ce5cb96e (patch)
treeb12b410a0dc0fea939f8da807e8d83471bc1c111 /Kconfig
parent5006c1052aafa01dab5b0e643b7dac755b41f3bb (diff)
downloadlinux-2d94e5224e81c58986a8cf44a3bf4830ce5cb96e.tar.bz2
HID: hid-sensor-hub: Fix debug lock warning
When CONFIG_DEBUG_LOCK_ALLOC is defined, mutex magic is compared and warned for (l->magic != l), here l is the address of mutex pointer. In hid-sensor-hub as part of hsdev creation, a per hsdev mutex is initialized during MFD cell creation. This hsdev, which contains, mutex is part of platform data for the a cell. But platform_data is copied in platform_device_add_data() in platform.c. This copy will copy the whole hsdev structure including mutex. But once copied the magic will no longer match. So when client driver call sensor_hub_input_attr_get_raw_value, this will trigger mutex warning. So to avoid this allocate mutex dynamically. This will be same even after copy. Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'Kconfig')
0 files changed, 0 insertions, 0 deletions