2 # Multifunction miscellaneous devices
6 menu "Multifunction device drivers"
13 bool "Support Marvell 88PM8606/88PM8607"
14 depends on I2C=y && GENERIC_HARDIRQS
18 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
19 This includes the I2C driver and the core APIs _only_, you have to
20 select individual components like voltage regulators, RTC and
21 battery-charger under the corresponding menus.
24 tristate "Support for Silicon Motion SM501"
26 This is the core driver for the Silicon Motion SM501 multimedia
27 companion chip. This device is a multifunction device which may
28 provide numerous interfaces including USB host controller, USB gadget,
29 asynchronous serial ports, audio functions, and a dual display video
30 interface. The device may be connected by PCI or local bus with
31 varying functions enabled.
34 bool "Export GPIO via GPIO layer"
35 depends on MFD_SM501 && GPIOLIB
37 This option uses the gpio library layer to export the 64 GPIO
38 lines on the SM501. The platform data is used to supply the
39 base number for the first GPIO line to register.
42 bool "Support for Compaq ASIC3"
43 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
46 This driver supports the ASIC3 multifunction chip found on many
47 PDAs (mainly iPAQ and HTC based ones)
49 config MFD_DAVINCI_VOICECODEC
53 config MFD_DM355EVM_MSP
54 bool "DaVinci DM355 EVM microcontroller"
55 depends on I2C=y && MACH_DAVINCI_DM355_EVM
57 This driver supports the MSP430 microcontroller used on these
58 boards. MSP430 firmware manages resets and power sequencing,
59 inputs from buttons and the IR remote, LEDs, an RTC, and more.
62 tristate "TI Sequencer Serial Port support"
63 depends on ARCH_DAVINCI_TNETV107X
66 Say Y here if you want support for the Sequencer Serial Port
67 in a Texas Instruments TNETV107X SoC.
69 To compile this driver as a module, choose M here: the
70 module will be called ti-ssp.
73 bool "HTC EGPIO support"
74 depends on GENERIC_HARDIRQS && GPIOLIB && ARM
76 This driver supports the CPLD egpio chip present on
77 several HTC phones. It provides basic support for input
78 pins, output pins, and irqs.
81 tristate "HTC PASIC3 LED/DS1WM chip support"
84 This core driver provides register access for the LED/DS1WM
85 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
86 HTC Magician devices, respectively. Actual functionality is
87 handled by the leds-pasic3 and ds1wm drivers.
90 bool "HTC I2C PLD chip support"
91 depends on I2C=y && GPIOLIB
93 If you say yes here you get support for the supposed CPLD
94 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
95 This device provides input and output GPIOs through an I2C
96 interface to one or more sub-chips.
99 tristate "Philips UCB1400 Core driver"
103 This enables support for the Philips UCB1400 core functions.
104 The UCB1400 is an AC97 audio codec.
106 To compile this driver as a module, choose M here: the
107 module will be called ucb1400_core.
110 tristate "TPS61050/61052 Boost Converters"
114 select REGULATOR_FIXED_VOLTAGE
116 This option enables a driver for the TP61050/TPS61052
117 high-power "white LED driver". This boost converter is
118 sometimes used for other things than white LEDs, and
119 also contains a GPIO pin.
122 tristate "TPS6501x Power Management chips"
123 depends on I2C && GPIOLIB
124 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
126 If you say yes here you get support for the TPS6501x series of
127 Power Management chips. These include voltage regulators,
128 lithium ion/polymer battery charging, and other features that
129 are often used in portable devices like cell phones and cameras.
131 This driver can also be built as a module. If so, the module
132 will be called tps65010.
135 tristate "TPS6507x Power Management / Touch Screen chips"
139 If you say yes here you get support for the TPS6507x series of
140 Power Management / Touch Screen chips. These include voltage
141 regulators, lithium ion/polymer battery charging, touch screen
142 and other features that are often used in portable devices.
143 This driver can also be built as a module. If so, the module
144 will be called tps6507x.
147 tristate "TPS65217 Power Management / White LED chips"
152 If you say yes here you get support for the TPS65217 series of
153 Power Management / White LED chips.
154 These include voltage regulators, lithium ion/polymer battery
155 charger, wled and other features that are often used in portable
158 This driver can also be built as a module. If so, the module
159 will be called tps65217.
162 bool "TPS6586x Power Management chips"
163 depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
166 If you say yes here you get support for the TPS6586X series of
167 Power Management chips.
168 This driver provides common support for accessing the device,
169 additional drivers must be enabled in order to use the
170 functionality of the device.
172 This driver can also be built as a module. If so, the module
173 will be called tps6586x.
176 bool "TPS65910 Power Management chip"
177 depends on I2C=y && GPIOLIB
182 if you say yes here you get support for the TPS65910 series of
183 Power Management chips.
189 config MFD_TPS65912_I2C
190 bool "TPS65912 Power Management chip with I2C"
193 depends on I2C=y && GPIOLIB
195 If you say yes here you get support for the TPS65912 series of
196 PM chips with I2C interface.
198 config MFD_TPS65912_SPI
199 bool "TPS65912 Power Management chip with SPI"
202 depends on SPI_MASTER && GPIOLIB
204 If you say yes here you get support for the TPS65912 series of
205 PM chips with SPI interface.
208 bool "Texas Instruments TWL92330/Menelaus PM chip"
209 depends on I2C=y && ARCH_OMAP2
211 If you say yes here you get support for the Texas Instruments
212 TWL92330/Menelaus Power Management chip. This include voltage
213 regulators, Dual slot memory card transceivers, real-time clock
214 and other features that are often used in portable devices like
215 cell phones and PDAs.
218 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
219 depends on I2C=y && GENERIC_HARDIRQS
222 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
223 This core driver provides register access and IRQ handling
224 facilities, and registers devices for the various functions
225 so that function-specific drivers can bind to them.
227 These multi-function chips are found on many OMAP2 and OMAP3
228 boards, providing power management, RTC, GPIO, keypad, a
229 high speed USB OTG transceiver, an audio codec (on most
230 versions) and many other features.
233 tristate "Texas Instruments TWL4030 MADC"
234 depends on TWL4030_CORE
236 This driver provides support for triton TWL4030-MADC. The
237 driver supports both RT and SW conversion methods.
239 This driver can be built as a module. If so it will be
243 bool "Support power resources on TWL4030 family chips"
244 depends on TWL4030_CORE && ARM
246 Say yes here if you want to use the power resources on the
247 TWL4030 family chips. Most of these resources are regulators,
248 which have a separate driver; some are control signals, such
249 as clock request handshaking.
251 This driver uses board-specific data to initialize the resources
252 and load scripts controlling which resources are switched off/on
253 or reset when a sleep, wakeup or warm reset event occurs.
255 config MFD_TWL4030_AUDIO
257 depends on TWL4030_CORE
262 tristate "TWL6030 PWM (Pulse Width Modulator) Support"
263 depends on TWL4030_CORE
267 Say yes here if you want support for TWL6030 PWM.
268 This is used to control charging LED brightness.
272 depends on TWL4030_CORE && GENERIC_HARDIRQS
277 bool "Support STMicroelectronics STMPE"
278 depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
281 Support for the STMPE family of I/O Expanders from
284 Currently supported devices are:
286 STMPE811: GPIO, Touchscreen
287 STMPE1601: GPIO, Keypad
288 STMPE2401: GPIO, Keypad
289 STMPE2403: GPIO, Keypad
291 This driver provides common support for accessing the device,
292 additional drivers must be enabled in order to use the functionality
293 of the device. Currently available sub drivers are:
297 Touchscreen: stmpe-ts
299 menu "STMPE Interface Drivers"
303 bool "STMPE I2C Inteface"
307 This is used to enable I2C interface of STMPE
310 bool "STMPE SPI Inteface"
311 depends on SPI_MASTER
313 This is used to enable SPI interface of STMPE
317 bool "Support Toshiba TC35892 and variants"
318 depends on I2C=y && GENERIC_HARDIRQS
321 Support for the Toshiba TC35892 and variants I/O Expander.
323 This driver provides common support for accessing the device,
324 additional drivers must be enabled in order to use the
325 functionality of the device.
332 bool "Support Toshiba T7L66XB"
333 depends on ARM && HAVE_CLK
337 Support for Toshiba Mobile IO Controller T7L66XB
340 bool "Support Toshiba TC6387XB"
341 depends on ARM && HAVE_CLK
345 Support for Toshiba Mobile IO Controller TC6387XB
348 bool "Support Toshiba TC6393XB"
349 depends on GPIOLIB && ARM && HAVE_CLK
353 Support for Toshiba Mobile IO Controller TC6393XB
356 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
359 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
360 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
361 usually found on PXA processors-based platforms. This includes
362 the I2C driver and the core APIs _only_, you have to select
363 individual components like LCD backlight, voltage regulators,
364 LEDs and battery-charger under the corresponding menus.
370 config MFD_DA9052_SPI
371 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI"
375 depends on SPI_MASTER=y
377 Support for the Dialog Semiconductor DA9052 PMIC
378 when controlled using SPI. This driver provides common support
379 for accessing the device, additional drivers must be enabled in
380 order to use the functionality of the device.
382 config MFD_DA9052_I2C
383 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C"
389 Support for the Dialog Semiconductor DA9052 PMIC
390 when controlled using I2C. This driver provides common support
391 for accessing the device, additional drivers must be enabled in
392 order to use the functionality of the device.
395 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
398 Say yes here to add support for Analog Devices AD5520 and ADP5501,
399 Multifunction Power Management IC. This includes
400 the I2C driver and the core APIs _only_, you have to select
401 individual components like LCD backlight, LEDs, GPIOs and Kepad
402 under the corresponding menus.
405 bool "Maxim Semiconductor MAX8925 PMIC Support"
406 depends on I2C=y && GENERIC_HARDIRQS
409 Say yes here to support for Maxim Semiconductor MAX8925. This is
410 a Power Management IC. This driver provies common support for
411 accessing the device, additional drivers must be enabled in order
412 to use the functionality of the device.
415 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
416 depends on I2C=y && GENERIC_HARDIRQS
419 Say yes here to support for Maxim Semiconductor MAX8997/8966.
420 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
421 MUIC controls on chip.
422 This driver provides common support for accessing the device;
423 additional drivers must be enabled in order to use the functionality
427 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
428 depends on I2C=y && GENERIC_HARDIRQS
431 Say yes here to support for Maxim Semiconductor MAX8998 and
432 National Semiconductor LP3974. This is a Power Management IC.
433 This driver provies common support for accessing the device,
434 additional drivers must be enabled in order to use the functionality
438 bool "SAMSUNG S5M Series Support"
439 depends on I2C=y && GENERIC_HARDIRQS
443 Support for the Samsung Electronics S5M MFD series.
444 This driver provies common support for accessing the device,
445 additional drivers must be enabled in order to use the functionality
449 tristate "Support Wolfson Microelectronics WM8400"
454 Support for the Wolfson Microelecronics WM8400 PMIC and audio
455 CODEC. This driver provides common support for accessing
456 the device, additional drivers must be enabled in order to use
457 the functionality of the device.
461 depends on GENERIC_HARDIRQS
463 config MFD_WM831X_I2C
464 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
468 depends on I2C=y && GENERIC_HARDIRQS
470 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
471 when controlled using I2C. This driver provides common support
472 for accessing the device, additional drivers must be enabled in
473 order to use the functionality of the device.
475 config MFD_WM831X_SPI
476 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
480 depends on SPI_MASTER && GENERIC_HARDIRQS
482 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
483 when controlled using SPI. This driver provides common support
484 for accessing the device, additional drivers must be enabled in
485 order to use the functionality of the device.
489 depends on GENERIC_HARDIRQS
491 config MFD_WM8350_CONFIG_MODE_0
493 depends on MFD_WM8350
495 config MFD_WM8350_CONFIG_MODE_1
497 depends on MFD_WM8350
499 config MFD_WM8350_CONFIG_MODE_2
501 depends on MFD_WM8350
503 config MFD_WM8350_CONFIG_MODE_3
505 depends on MFD_WM8350
507 config MFD_WM8351_CONFIG_MODE_0
509 depends on MFD_WM8350
511 config MFD_WM8351_CONFIG_MODE_1
513 depends on MFD_WM8350
515 config MFD_WM8351_CONFIG_MODE_2
517 depends on MFD_WM8350
519 config MFD_WM8351_CONFIG_MODE_3
521 depends on MFD_WM8350
523 config MFD_WM8352_CONFIG_MODE_0
525 depends on MFD_WM8350
527 config MFD_WM8352_CONFIG_MODE_1
529 depends on MFD_WM8350
531 config MFD_WM8352_CONFIG_MODE_2
533 depends on MFD_WM8350
535 config MFD_WM8352_CONFIG_MODE_3
537 depends on MFD_WM8350
539 config MFD_WM8350_I2C
540 bool "Support Wolfson Microelectronics WM8350 with I2C"
542 depends on I2C=y && GENERIC_HARDIRQS
544 The WM8350 is an integrated audio and power management
545 subsystem with watchdog and RTC functionality for embedded
546 systems. This option enables core support for the WM8350 with
547 I2C as the control interface. Additional options must be
548 selected to enable support for the functionality of the chip.
551 bool "Support Wolfson Microelectronics WM8994"
555 depends on I2C=y && GENERIC_HARDIRQS
557 The WM8994 is a highly integrated hi-fi CODEC designed for
558 smartphone applicatiosn. As well as audio functionality it
559 has on board GPIO and regulator functionality which is
560 supported via the relevant subsystems. This driver provides
561 core support for the WM8994, in order to use the actual
562 functionaltiy of the device other drivers must be enabled.
565 tristate "Support for NXP PCF50633"
569 Say yes here if you have NXP PCF50633 chip on your board.
570 This core driver provides register access and IRQ handling
571 facilities, and registers devices for the various functions
572 so that function-specific drivers can bind to them.
575 tristate "Support for NXP PCF50633 ADC"
576 depends on MFD_PCF50633
578 Say yes here if you want to include support for ADC in the
582 tristate "Support for NXP PCF50633 GPIO"
583 depends on MFD_PCF50633
585 Say yes here if you want to include support GPIO for pins on
592 tristate "Support Freescale MC13783 and MC13892"
593 depends on SPI_MASTER
597 Support for the Freescale (Atlas) PMIC and audio CODECs
599 This driver provides common support for accessing the device,
600 additional drivers must be enabled in order to use the
601 functionality of the device.
604 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
605 default y if ARCH_U300 || ARCH_U8500
607 Say yes here if you have the ABX500 Mixed Signal IC family
608 chips. This core driver expose register access functions.
609 Functionality specific drivers using these functions can
610 remain unchanged when IC changes. Binding of the functions to
611 actual register access is done by the IC core driver.
614 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
615 depends on I2C=y && ABX500_CORE
617 default y if ARCH_U300
619 Select this to enable the AB3100 Mixed Signal IC core
620 functionality. This connects to a AB3100 on the I2C bus
621 and expose a number of symbols needed for dependent devices
622 to read and write registers and subscribe to events from
623 this multi-functional IC. This is needed to use other features
624 of the AB3100 such as battery-backed RTC, charging control,
625 LEDs, vibrator, system power and temperature, power management
629 tristate "ST-Ericsson AB3100 OTP functions"
630 depends on AB3100_CORE
631 default y if AB3100_CORE
633 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
634 programmable memory) support. This exposes a sysfs file to read
639 depends on GENERIC_HARDIRQS && SPI_MASTER
641 This enables the PCAP ASIC present on EZX Phones. This is
642 needed for MMC, TouchScreen, Sound, USB, etc..
645 bool "ST-Ericsson AB5500 Mixed Signal Power Management chip"
646 depends on ABX500_CORE && MFD_DB5500_PRCMU
649 Select this option to enable access to AB5500 power management
650 chip. This connects to the db5500 chip via the I2C bus via PRCMU.
651 This chip embeds various other multimedia funtionalities as well.
654 bool "Enable debug info via debugfs"
655 depends on AB5500_CORE && DEBUG_FS
656 default y if DEBUG_FS
658 Select this option if you want debug information from the AB5500
659 using the debug filesystem, debugfs.
662 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
663 depends on GENERIC_HARDIRQS && ABX500_CORE
666 Select this option to enable access to AB8500 power management
667 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
668 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
669 the irq_chip parts for handling the Mixed Signal chip events.
670 This chip embeds various other multimedia funtionalities as well.
672 config AB8500_I2C_CORE
673 bool "AB8500 register access via PRCMU I2C"
674 depends on AB8500_CORE && MFD_DB8500_PRCMU
677 This enables register access to the AB8500 chip via PRCMU I2C.
678 The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
679 the I2C bus is connected to the Power Reset
680 and Mangagement Unit, PRCMU.
683 bool "Enable debug info via debugfs"
684 depends on AB8500_CORE && DEBUG_FS
685 default y if DEBUG_FS
687 Select this option if you want debug information using the debug
691 bool "AB8500 GPADC driver"
692 depends on AB8500_CORE && REGULATOR_AB8500
695 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
697 config MFD_DB8500_PRCMU
698 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
699 depends on UX500_SOC_DB8500
702 Select this option to enable support for the DB8500 Power Reset
703 and Control Management Unit. This is basically an autonomous
704 system controller running an XP70 microprocessor, which is accessed
705 through a register map.
707 config MFD_DB5500_PRCMU
708 bool "ST-Ericsson DB5500 Power Reset Control Management Unit"
709 depends on UX500_SOC_DB5500
712 Select this option to enable support for the DB5500 Power Reset
713 and Control Management Unit. This is basically an autonomous
714 system controller running an XP70 microprocessor, which is accessed
715 through a register map.
718 tristate "Support for CS5535 and CS5536 southbridge core functions"
720 depends on PCI && X86
722 This is the core driver for CS5535/CS5536 MFD functions. This is
723 necessary for using the board's GPIO and MFGPT functionality.
725 config MFD_TIMBERDALE
726 tristate "Support for the Timberdale FPGA"
728 depends on PCI && GPIOLIB
730 This is the core driver for the timberdale FPGA. This device is a
731 multifunction device which exposes numerous platform devices.
733 The timberdale FPGA can be found on the Intel Atom development board
734 for in-vehicle infontainment, called Russellville.
737 tristate "Intel SCH LPC"
741 LPC bridge function of the Intel SCH provides support for
742 System Management Bus and General Purpose I/O.
745 tristate "Support for RDC-R321x southbridge"
749 Say yes here if you want to have support for the RDC R-321x SoC
750 southbridge which provides access to GPIOs and Watchdog using the
751 southbridge PCI device configuration space.
753 config MFD_JANZ_CMODIO
754 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
758 This is the core driver for the Janz CMOD-IO PCI MODULbus
759 carrier board. This device is a PCI to MODULbus bridge which may
760 host many different types of MODULbus daughterboards, including
761 CAN and GPIO controllers.
763 config MFD_JZ4740_ADC
764 bool "Support for the JZ4740 SoC ADC core"
766 select GENERIC_IRQ_CHIP
767 depends on MACH_JZ4740
769 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
770 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
773 tristate "Support for VIA VX855/VX875 integrated south bridge"
777 Say yes here to enable support for various functions of the
778 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
779 and/or vx855_gpio drivers for this to do anything useful.
781 config MFD_WL1273_CORE
782 tristate "Support for TI WL1273 FM radio."
787 This is the core driver for the TI WL1273 FM radio. This MFD
788 driver connects the radio-wl1273 V4L2 module and the wl1273
791 config MFD_OMAP_USB_HOST
792 bool "Support OMAP USBHS core driver"
793 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
796 This is the core driver for the OAMP EHCI and OHCI drivers.
797 This MFD driver does the required setup functionalities for
798 OMAP USB Host drivers.
803 config MFD_PM8921_CORE
804 tristate "Qualcomm PM8921 PMIC chip"
809 If you say yes to this option, support will be included for the
810 built-in PM8921 PMIC chip.
812 This is required if your board has a PM8921 and uses its features,
813 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
815 Say M here if you want to include support for PM8921 chip as a module.
816 This will build a module called "pm8921-core".
818 config MFD_PM8XXX_IRQ
819 bool "Support for Qualcomm PM8xxx IRQ features"
820 depends on MFD_PM8XXX
821 default y if MFD_PM8XXX
823 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
825 This is required to use certain other PM 8xxx features, such as GPIO
828 config TPS65911_COMPARATOR
832 bool "TPS65090 Power Management chips"
833 depends on I2C=y && GENERIC_HARDIRQS
837 If you say yes here you get support for the TPS65090 series of
838 Power Management chips.
839 This driver provides common support for accessing the device,
840 additional drivers must be enabled in order to use the
841 functionality of the device.
843 config MFD_AAT2870_CORE
844 bool "Support for the AnalogicTech AAT2870"
846 depends on I2C=y && GPIOLIB
848 If you say yes here you get support for the AAT2870.
849 This driver provides common support for accessing the device,
850 additional drivers must be enabled in order to use the
851 functionality of the device.
853 config MFD_INTEL_MSIC
854 bool "Support for Intel MSIC"
855 depends on INTEL_SCU_IPC
858 Select this option to enable access to Intel MSIC (Avatele
859 Passage) chip. This chip embeds audio, battery, GPIO, etc.
860 devices used in Intel Medfield platforms.
863 bool "Ricoh RC5T583 Power Management system device"
864 depends on I2C=y && GENERIC_HARDIRQS
868 Select this option to get support for the RICOH583 Power
869 Management system device.
870 This driver provides common support for accessing the device
871 through i2c interface. The device supports multiple sub-devices
872 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
873 Additional drivers must be enabled in order to use the
874 different functionality of the device.
877 bool "Support for Freescale i.MX on-chip ANATOP controller"
880 Select this option to enable Freescale i.MX on-chip ANATOP
881 MFD controller. This controller embeds regulator and
882 thermal devices for Freescale i.MX platforms.
887 menu "Multimedia Capabilities Port drivers"
888 depends on ARCH_SA1100
895 tristate "Support SA11x0 MCP interface"
896 depends on ARCH_SA1100
901 bool "Support for UCB1200 / UCB1300"
902 depends on MCP_SA11X0
905 config MCP_UCB1200_TS
906 tristate "Touchscreen interface support"
907 depends on MCP_UCB1200 && INPUT