# # VME configuration. # menuconfig VME_BUS bool "VME bridge support" depends on PCI ---help--- If you say Y here you get support for the VME bridge Framework. if VME_BUS source "drivers/vme/bridges/Kconfig" source "drivers/vme/boards/Kconfig" source "drivers/staging/vme/devices/Kconfig" endif # VME ext.git/atom/?h=master' type='application/atom+xml'/>
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRoderick Colenbrander <roderick.colenbrander@sony.com>2016-11-23 14:07:06 -0800
committerJiri Kosina <jkosina@suse.cz>2016-11-28 14:54:56 +0100
commit4f967f6d73746f66514528cc1191025f0b5d69b3 (patch)
tree7988a32b3b29ab600d72fdd9b24e700931b0f6db
parentcf1015d65d7c8a5504a4c03afb60fb86bff0f032 (diff)
HID: sony: Fix memory issue when connecting device using both Bluetooth and USB
A previous patch moved most input initialization from sony_probe to sony_input_configured to avoid some race conditions. The driver has some special logic to prevent the device to get registered twice in case the user connects it both over Bluetooth and USB. When this condition happens sony_input_configured returns a failure, but sony_probe continues as hid_hw_start doesn't fail. As was discussed on linux-input, it is acceptable for this function to fail. This patch adds a check for the HID_CLAIMED_INPUT flag within sony_probe to determine whether initialization succeeded correctly. The flag is not set by the HID layer when sony_input_configured fails. Signed-off-by: Roderick Colenbrander <roderick.colenbrander@sony.com> Signed-off-by: Jiri Kosina <jkosina@suse.cz>