aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/staging/iio/resolver/Kconfig
blob: a4a36342935510f94646a81a041bbdc692b41521 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
#
# Resolver/Synchro drivers
#
comment "Resolver to digital converters"

config AD2S90
	tristate "Analog Devices ad2s90 driver"
	depends on SPI
	help
	  Say yes here to build support for Analog Devices spi resolver
	  to digital converters, ad2s90, provides direct access via sysfs.

config AD2S120X
	tristate "Analog Devices ad2s120x driver"
	depends on SPI
	help
	  Say yes here to build support for Analog Devices spi resolver
	  to digital converters, ad2s1200 and ad2s1205, provides direct access
	  via sysfs.

config AD2S1210
	tristate "Analog Devices ad2s1210 driver"
	depends on SPI
	help
	  Say yes here to build support for Analog Devices spi resolver
	  to digital converters, ad2s1210, provides direct access via sysfs.

choice
	prompt "Resolution Control"
	depends on AD2S1210
	default AD2S1210_GPIO_NONE
	help
	  In normal mode, the resolution of the digital output is selected
	  using the RES0 and RES1 input pins. In configuration mode, the
	  resolution is selected by setting the RES0 and RES1 bits in the
	  control regsiter. When switching between normal mode and configuration
	  mode, there are some schemes to keep them matchs.

config AD2S1210_GPIO_INPUT
	bool "read resolution from gpio pins"
	help
	  GPIO pins are sampling RES0 and RES1 pins, read the resolution
	  settings from the GPIO pins.

config AD2S1210_GPIO_OUTPUT
	bool "set gpio pins to set resolution"
	help
	  RES0 and RES1 pins are controlled by GPIOs, setting GPIO pins to
	  set the resolution.

config AD2S1210_GPIO_NONE
	bool "take the responsibility by user"

endchoice