summaryrefslogtreecommitdiff
path: root/include/dt-bindings/iio/adi,ad5592r.h
blob: c48aca1dcade61094996d23b0a69a3760a3ea5eb (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16

#ifndef _DT_BINDINGS_ADI_AD5592R_H
#define _DT_BINDINGS_ADI_AD5592R_H

#define CH_MODE_UNUSED			0
#define CH_MODE_ADC			1
#define CH_MODE_DAC			2
#define CH_MODE_DAC_AND_ADC		3
#define CH_MODE_GPIO			8

#define CH_OFFSTATE_PULLDOWN		0
#define CH_OFFSTATE_OUT_LOW		1
#define CH_OFFSTATE_OUT_HIGH		2
#define CH_OFFSTATE_OUT_TRISTATE	3

#endif /* _DT_BINDINGS_ADI_AD5592R_H */
y.com>2016-11-23 14:07:06 -0800 committerJiri Kosina <jkosina@suse.cz>2016-11-28 14:54:56 +0100 commit4f967f6d73746f66514528cc1191025f0b5d69b3 (patch) tree7988a32b3b29ab600d72fdd9b24e700931b0f6db /include/trace 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>
Diffstat (limited to 'include/trace')