forked from Minki/linux
6252547b8a
In commit aeb5032b3f, a dependency on IRQ_DOMAIN was added, which causes
regressions on previously working setups: a previously working non-DT
kernel configuration now loses its PMIC support. The lack of PMIC
support in turn causes the loss of other functionality the kernel had.
This dependency was added because the driver now registers its
interrupts with the IRQ domain code, presumably to prevent a build error.
The result is that OMAP3 oopses in the vp.c code (fixed by a previous
commit) due to the lack of PMIC support.
However, even with IRQ_DOMAIN enabled, the driver oopses:
Unable to handle kernel NULL pointer dereference at virtual address 00000000
pgd = c0004000
[00000000] *pgd=00000000
Internal error: Oops: 5 [#1] SMP
Modules linked in:
CPU: 1 Not tainted (3.3.0-rc2+ #271)
PC is at irq_domain_add+0x1c/0x134
LR is at twl_probe+0xd0/0x370
pc : [<c007bad0>] lr : [<c029baac>] psr: 00000113
sp : df843c48 ip : df843c68 fp : df843c64
r10: c02b93e4 r9 : 00000000 r8 : c029b9dc
r7 : df9d8a00 r6 : c03bef90 r5 : 00000000 r4 : c03f5240
r3 : 00000000 r2 : c03f5240 r1 : 00000015 r0 : c03f5240
Flags: nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
Control: 10c5387d Table: 8000404a DAC: 00000015
Process swapper/0 (pid: 1, stack limit = 0xdf8422f0)
Stack: (0xdf843c48 to 0xdf844000)
3c40: 00000014 00000170 00000014 c03bef90 df843c9c df843c68
3c60: c029baac c007bac0 00000000 df9d8a20 00000001 c03cd238 c02b93e4 df9d8a20
3c80: df9d8a04 df9d8a00 c029b9dc df8cae08 df843cc4 df843ca0 c01eee70 c029b9e8
...
Backtrace:
[<c007bab4>] (irq_domain_add+0x0/0x134) from [<c029baac>] (twl_probe+0xd0/0x370)
r6:c03bef90 r5:00000014 r4:00000170
[<c029b9dc>] (twl_probe+0x0/0x370) from [<c01eee70>] (i2c_device_probe+0xb0/0xe4)
[<c01eedc0>] (i2c_device_probe+0x0/0xe4) from [<c01d1f34>] (really_probe+0xa0/0x178)
r8:df8f0070 r7:c03cd238 r6:df9d8a20 r5:df9d8a20 r4:df9d8a20
[<c01d1e94>] (really_probe+0x0/0x178) from [<c01d205c>] (driver_probe_device+0x50/0x68)
r7:df843d18 r6:df9d8a20 r5:c03cd238 r4:df9d8a20
[<c01d200c>] (driver_probe_device+0x0/0x68) from [<c01d2148>] (__device_attach+0x44/0x48)
r5:df9d8a20 r4:c03cd238
[<c01d2104>] (__device_attach+0x0/0x48) from [<c01d0840>] (bus_for_each_drv+0x58/0x98)
r5:c01d2104 r4:00000000
[<c01d07e8>] (bus_for_each_drv+0x0/0x98) from [<c01d21f8>] (device_attach+0x80/0xac)
r7:df9d8a28 r6:df9d8a54 r5:c03cd978 r4:df9d8a20
[<c01d2178>] (device_attach+0x0/0xac) from [<c01d1430>] (bus_probe_device+0x34/0xa4)
r6:df9d8a20 r5:c03cd978 r4:df9d8a20
[<c01d13fc>] (bus_probe_device+0x0/0xa4) from [<c01cffb0>] (device_add+0x2a0/0x420)
r6:00000000 r5:df9d8a20 r4:df9d8a20
[<c01cfd10>] (device_add+0x0/0x420) from [<c01d0150>] (device_register+0x20/0x24)
r8:df9d8a00 r7:df9d8a04 r6:df8f0048 r5:df9d8a00 r4:df9d8a20
[<c01d0130>] (device_register+0x0/0x24) from [<c01ef8d4>] (i2c_new_device+0x118/0x180)
r4:df9d8a20
[<c01ef7bc>] (i2c_new_device+0x0/0x180) from [<c01efc88>] (i2c_register_adapter+0x140/0x204)
r8:c03cd970 r7:00000000 r6:df8f0070 r5:df8a6300 r4:df8f0048
[<c01efb48>] (i2c_register_adapter+0x0/0x204) from [<c01efe9c>] (i2c_add_numbered_adapter+0xb4/0xcc)
r8:df8a4c54 r7:df8cae00 r6:df843e2c r5:df8f0048 r4:00000000
[<c01efde8>] (i2c_add_numbered_adapter+0x0/0xcc) from [<c029ce1c>] (omap_i2c_probe+0x2f8/0x3b4)
r6:00000000 r5:df8f0000 r4:df8f0070
[<c029cb24>] (omap_i2c_probe+0x0/0x3b4) from [<c01d3484>] (platform_drv_probe+0x20/0x24)
[<c01d3464>] (platform_drv_probe+0x0/0x24) from [<c01d1f34>] (really_probe+0xa0/0x178)
[<c01d1e94>] (really_probe+0x0/0x178) from [<c01d205c>] (driver_probe_device+0x50/0x68)
r7:df843ef0 r6:c03cdb2c r5:c03cdb2c r4:df8cae08
[<c01d200c>] (driver_probe_device+0x0/0x68) from [<c01d20e0>] (__driver_attach+0x6c/0x90)
r5:df8cae3c r4:df8cae08
[<c01d2074>] (__driver_attach+0x0/0x90) from [<c01d08d8>] (bus_for_each_dev+0x58/0x98)
r6:c03cdb2c r5:c01d2074 r4:00000000
[<c01d0880>] (bus_for_each_dev+0x0/0x98) from [<c01d1d80>] (driver_attach+0x20/0x28)
r7:df880b80 r6:c03cdb2c r5:c03cdb2c r4:c0394f28
[<c01d1d60>] (driver_attach+0x0/0x28) from [<c01d115c>] (bus_add_driver+0xb4/0x230)
[<c01d10a8>] (bus_add_driver+0x0/0x230) from [<c01d278c>] (driver_register+0xc8/0x154)
[<c01d26c4>] (driver_register+0x0/0x154) from [<c01d37e4>] (platform_driver_register+0x4c/0x60)
r8:00000000 r7:00000013 r6:c00384c8 r5:c0395180 r4:c0394f28
[<c01d3798>] (platform_driver_register+0x0/0x60) from [<c038626c>] (omap_i2c_init_driver+0x14/0x1c)
[<c0386258>] (omap_i2c_init_driver+0x0/0x1c) from [<c00087b8>] (do_one_initcall+0x9c/0x164)
[<c000871c>] (do_one_initcall+0x0/0x164) from [<c036c2f4>] (kernel_init+0x90/0x138)
[<c036c264>] (kernel_init+0x0/0x138) from [<c00384c8>] (do_exit+0x0/0x2ec)
r5:c036c264 r4:00000000
<0>Code: e24dd004 e5903014 e1a04000 e5905010 (e5933000)
<4>---[ end trace 1b75b31a2719ed1c ]---
This happens because we try to register an IRQ domain with a NULL ops
structure, and the first thing irq_domain_add() does is try to
dereference this ops structure.
So, fix the problem by getting rid of the incorrect OF_IRQ ifdef and
wrapping the IRQ domain bits of the driver with an IRQ_DOMAIN ifdef
instead.
Acked-by: Tony Lindgren <tony@atomide.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
858 lines
26 KiB
Plaintext
858 lines
26 KiB
Plaintext
#
|
|
# Multifunction miscellaneous devices
|
|
#
|
|
|
|
if HAS_IOMEM
|
|
menu "Multifunction device drivers"
|
|
|
|
config MFD_CORE
|
|
tristate
|
|
default n
|
|
|
|
config MFD_88PM860X
|
|
bool "Support Marvell 88PM8606/88PM8607"
|
|
depends on I2C=y && GENERIC_HARDIRQS
|
|
select REGMAP_I2C
|
|
select MFD_CORE
|
|
help
|
|
This supports for Marvell 88PM8606/88PM8607 Power Management IC.
|
|
This includes the I2C driver and the core APIs _only_, you have to
|
|
select individual components like voltage regulators, RTC and
|
|
battery-charger under the corresponding menus.
|
|
|
|
config MFD_SM501
|
|
tristate "Support for Silicon Motion SM501"
|
|
---help---
|
|
This is the core driver for the Silicon Motion SM501 multimedia
|
|
companion chip. This device is a multifunction device which may
|
|
provide numerous interfaces including USB host controller, USB gadget,
|
|
asynchronous serial ports, audio functions, and a dual display video
|
|
interface. The device may be connected by PCI or local bus with
|
|
varying functions enabled.
|
|
|
|
config MFD_SM501_GPIO
|
|
bool "Export GPIO via GPIO layer"
|
|
depends on MFD_SM501 && GPIOLIB
|
|
---help---
|
|
This option uses the gpio library layer to export the 64 GPIO
|
|
lines on the SM501. The platform data is used to supply the
|
|
base number for the first GPIO line to register.
|
|
|
|
config MFD_ASIC3
|
|
bool "Support for Compaq ASIC3"
|
|
depends on GENERIC_HARDIRQS && GPIOLIB && ARM
|
|
select MFD_CORE
|
|
---help---
|
|
This driver supports the ASIC3 multifunction chip found on many
|
|
PDAs (mainly iPAQ and HTC based ones)
|
|
|
|
config MFD_DAVINCI_VOICECODEC
|
|
tristate
|
|
select MFD_CORE
|
|
|
|
config MFD_DM355EVM_MSP
|
|
bool "DaVinci DM355 EVM microcontroller"
|
|
depends on I2C=y && MACH_DAVINCI_DM355_EVM
|
|
help
|
|
This driver supports the MSP430 microcontroller used on these
|
|
boards. MSP430 firmware manages resets and power sequencing,
|
|
inputs from buttons and the IR remote, LEDs, an RTC, and more.
|
|
|
|
config MFD_TI_SSP
|
|
tristate "TI Sequencer Serial Port support"
|
|
depends on ARCH_DAVINCI_TNETV107X
|
|
select MFD_CORE
|
|
---help---
|
|
Say Y here if you want support for the Sequencer Serial Port
|
|
in a Texas Instruments TNETV107X SoC.
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
module will be called ti-ssp.
|
|
|
|
config HTC_EGPIO
|
|
bool "HTC EGPIO support"
|
|
depends on GENERIC_HARDIRQS && GPIOLIB && ARM
|
|
help
|
|
This driver supports the CPLD egpio chip present on
|
|
several HTC phones. It provides basic support for input
|
|
pins, output pins, and irqs.
|
|
|
|
config HTC_PASIC3
|
|
tristate "HTC PASIC3 LED/DS1WM chip support"
|
|
select MFD_CORE
|
|
help
|
|
This core driver provides register access for the LED/DS1WM
|
|
chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
|
|
HTC Magician devices, respectively. Actual functionality is
|
|
handled by the leds-pasic3 and ds1wm drivers.
|
|
|
|
config HTC_I2CPLD
|
|
bool "HTC I2C PLD chip support"
|
|
depends on I2C=y && GPIOLIB
|
|
help
|
|
If you say yes here you get support for the supposed CPLD
|
|
found on omap850 HTC devices like the HTC Wizard and HTC Herald.
|
|
This device provides input and output GPIOs through an I2C
|
|
interface to one or more sub-chips.
|
|
|
|
config UCB1400_CORE
|
|
tristate "Philips UCB1400 Core driver"
|
|
depends on AC97_BUS
|
|
depends on GPIOLIB
|
|
help
|
|
This enables support for the Philips UCB1400 core functions.
|
|
The UCB1400 is an AC97 audio codec.
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
module will be called ucb1400_core.
|
|
|
|
config TPS6105X
|
|
tristate "TPS61050/61052 Boost Converters"
|
|
depends on I2C
|
|
select REGULATOR
|
|
select MFD_CORE
|
|
select REGULATOR_FIXED_VOLTAGE
|
|
help
|
|
This option enables a driver for the TP61050/TPS61052
|
|
high-power "white LED driver". This boost converter is
|
|
sometimes used for other things than white LEDs, and
|
|
also contains a GPIO pin.
|
|
|
|
config TPS65010
|
|
tristate "TPS6501x Power Management chips"
|
|
depends on I2C && GPIOLIB
|
|
default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
|
|
help
|
|
If you say yes here you get support for the TPS6501x series of
|
|
Power Management chips. These include voltage regulators,
|
|
lithium ion/polymer battery charging, and other features that
|
|
are often used in portable devices like cell phones and cameras.
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
will be called tps65010.
|
|
|
|
config TPS6507X
|
|
tristate "TPS6507x Power Management / Touch Screen chips"
|
|
select MFD_CORE
|
|
depends on I2C
|
|
help
|
|
If you say yes here you get support for the TPS6507x series of
|
|
Power Management / Touch Screen chips. These include voltage
|
|
regulators, lithium ion/polymer battery charging, touch screen
|
|
and other features that are often used in portable devices.
|
|
This driver can also be built as a module. If so, the module
|
|
will be called tps6507x.
|
|
|
|
config MFD_TPS6586X
|
|
bool "TPS6586x Power Management chips"
|
|
depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
|
|
select MFD_CORE
|
|
help
|
|
If you say yes here you get support for the TPS6586X series of
|
|
Power Management chips.
|
|
This driver provides common support for accessing the device,
|
|
additional drivers must be enabled in order to use the
|
|
functionality of the device.
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
will be called tps6586x.
|
|
|
|
config MFD_TPS65910
|
|
bool "TPS65910 Power Management chip"
|
|
depends on I2C=y && GPIOLIB
|
|
select MFD_CORE
|
|
select GPIO_TPS65910
|
|
help
|
|
if you say yes here you get support for the TPS65910 series of
|
|
Power Management chips.
|
|
|
|
config MFD_TPS65912
|
|
bool
|
|
depends on GPIOLIB
|
|
|
|
config MFD_TPS65912_I2C
|
|
bool "TPS95612 Power Management chip with I2C"
|
|
select MFD_CORE
|
|
select MFD_TPS65912
|
|
depends on I2C=y && GPIOLIB
|
|
help
|
|
If you say yes here you get support for the TPS65912 series of
|
|
PM chips with I2C interface.
|
|
|
|
config MFD_TPS65912_SPI
|
|
bool "TPS65912 Power Management chip with SPI"
|
|
select MFD_CORE
|
|
select MFD_TPS65912
|
|
depends on SPI_MASTER && GPIOLIB
|
|
help
|
|
If you say yes here you get support for the TPS65912 series of
|
|
PM chips with SPI interface.
|
|
|
|
config MENELAUS
|
|
bool "Texas Instruments TWL92330/Menelaus PM chip"
|
|
depends on I2C=y && ARCH_OMAP2
|
|
help
|
|
If you say yes here you get support for the Texas Instruments
|
|
TWL92330/Menelaus Power Management chip. This include voltage
|
|
regulators, Dual slot memory card transceivers, real-time clock
|
|
and other features that are often used in portable devices like
|
|
cell phones and PDAs.
|
|
|
|
config TWL4030_CORE
|
|
bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
|
|
depends on I2C=y && GENERIC_HARDIRQS
|
|
help
|
|
Say yes here if you have TWL4030 / TWL6030 family chip on your board.
|
|
This core driver provides register access and IRQ handling
|
|
facilities, and registers devices for the various functions
|
|
so that function-specific drivers can bind to them.
|
|
|
|
These multi-function chips are found on many OMAP2 and OMAP3
|
|
boards, providing power management, RTC, GPIO, keypad, a
|
|
high speed USB OTG transceiver, an audio codec (on most
|
|
versions) and many other features.
|
|
|
|
config TWL4030_MADC
|
|
tristate "Texas Instruments TWL4030 MADC"
|
|
depends on TWL4030_CORE
|
|
help
|
|
This driver provides support for triton TWL4030-MADC. The
|
|
driver supports both RT and SW conversion methods.
|
|
|
|
This driver can be built as a module. If so it will be
|
|
named twl4030-madc
|
|
|
|
config TWL4030_POWER
|
|
bool "Support power resources on TWL4030 family chips"
|
|
depends on TWL4030_CORE && ARM
|
|
help
|
|
Say yes here if you want to use the power resources on the
|
|
TWL4030 family chips. Most of these resources are regulators,
|
|
which have a separate driver; some are control signals, such
|
|
as clock request handshaking.
|
|
|
|
This driver uses board-specific data to initialize the resources
|
|
and load scripts controlling which resources are switched off/on
|
|
or reset when a sleep, wakeup or warm reset event occurs.
|
|
|
|
config MFD_TWL4030_AUDIO
|
|
bool
|
|
depends on TWL4030_CORE
|
|
select MFD_CORE
|
|
default n
|
|
|
|
config TWL6030_PWM
|
|
tristate "TWL6030 PWM (Pulse Width Modulator) Support"
|
|
depends on TWL4030_CORE
|
|
select HAVE_PWM
|
|
default n
|
|
help
|
|
Say yes here if you want support for TWL6030 PWM.
|
|
This is used to control charging LED brightness.
|
|
|
|
config TWL6040_CORE
|
|
bool
|
|
depends on TWL4030_CORE && GENERIC_HARDIRQS
|
|
select MFD_CORE
|
|
default n
|
|
|
|
config MFD_STMPE
|
|
bool "Support STMicroelectronics STMPE"
|
|
depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
|
|
select MFD_CORE
|
|
help
|
|
Support for the STMPE family of I/O Expanders from
|
|
STMicroelectronics.
|
|
|
|
Currently supported devices are:
|
|
|
|
STMPE811: GPIO, Touchscreen
|
|
STMPE1601: GPIO, Keypad
|
|
STMPE2401: GPIO, Keypad
|
|
STMPE2403: GPIO, Keypad
|
|
|
|
This driver provides common support for accessing the device,
|
|
additional drivers must be enabled in order to use the functionality
|
|
of the device. Currently available sub drivers are:
|
|
|
|
GPIO: stmpe-gpio
|
|
Keypad: stmpe-keypad
|
|
Touchscreen: stmpe-ts
|
|
|
|
menu "STMPE Interface Drivers"
|
|
depends on MFD_STMPE
|
|
|
|
config STMPE_I2C
|
|
bool "STMPE I2C Inteface"
|
|
depends on I2C=y
|
|
default y
|
|
help
|
|
This is used to enable I2C interface of STMPE
|
|
|
|
config STMPE_SPI
|
|
bool "STMPE SPI Inteface"
|
|
depends on SPI_MASTER
|
|
help
|
|
This is used to enable SPI interface of STMPE
|
|
endmenu
|
|
|
|
config MFD_TC3589X
|
|
bool "Support Toshiba TC35892 and variants"
|
|
depends on I2C=y && GENERIC_HARDIRQS
|
|
select MFD_CORE
|
|
help
|
|
Support for the Toshiba TC35892 and variants I/O Expander.
|
|
|
|
This driver provides common support for accessing the device,
|
|
additional drivers must be enabled in order to use the
|
|
functionality of the device.
|
|
|
|
config MFD_TMIO
|
|
bool
|
|
default n
|
|
|
|
config MFD_T7L66XB
|
|
bool "Support Toshiba T7L66XB"
|
|
depends on ARM && HAVE_CLK
|
|
select MFD_CORE
|
|
select MFD_TMIO
|
|
help
|
|
Support for Toshiba Mobile IO Controller T7L66XB
|
|
|
|
config MFD_TC6387XB
|
|
bool "Support Toshiba TC6387XB"
|
|
depends on ARM && HAVE_CLK
|
|
select MFD_CORE
|
|
select MFD_TMIO
|
|
help
|
|
Support for Toshiba Mobile IO Controller TC6387XB
|
|
|
|
config MFD_TC6393XB
|
|
bool "Support Toshiba TC6393XB"
|
|
depends on GPIOLIB && ARM && HAVE_CLK
|
|
select MFD_CORE
|
|
select MFD_TMIO
|
|
help
|
|
Support for Toshiba Mobile IO Controller TC6393XB
|
|
|
|
config PMIC_DA903X
|
|
bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
|
|
depends on I2C=y
|
|
help
|
|
Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
|
|
ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
|
|
usually found on PXA processors-based platforms. This includes
|
|
the I2C driver and the core APIs _only_, you have to select
|
|
individual components like LCD backlight, voltage regulators,
|
|
LEDs and battery-charger under the corresponding menus.
|
|
|
|
config PMIC_DA9052
|
|
bool
|
|
select MFD_CORE
|
|
|
|
config MFD_DA9052_SPI
|
|
bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI"
|
|
select REGMAP_SPI
|
|
select REGMAP_IRQ
|
|
select PMIC_DA9052
|
|
depends on SPI_MASTER=y
|
|
help
|
|
Support for the Dialog Semiconductor DA9052 PMIC
|
|
when controlled using SPI. This driver provides common support
|
|
for accessing the device, additional drivers must be enabled in
|
|
order to use the functionality of the device.
|
|
|
|
config MFD_DA9052_I2C
|
|
bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C"
|
|
select REGMAP_I2C
|
|
select REGMAP_IRQ
|
|
select PMIC_DA9052
|
|
depends on I2C=y
|
|
help
|
|
Support for the Dialog Semiconductor DA9052 PMIC
|
|
when controlled using I2C. This driver provides common support
|
|
for accessing the device, additional drivers must be enabled in
|
|
order to use the functionality of the device.
|
|
|
|
config PMIC_ADP5520
|
|
bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
|
|
depends on I2C=y
|
|
help
|
|
Say yes here to add support for Analog Devices AD5520 and ADP5501,
|
|
Multifunction Power Management IC. This includes
|
|
the I2C driver and the core APIs _only_, you have to select
|
|
individual components like LCD backlight, LEDs, GPIOs and Kepad
|
|
under the corresponding menus.
|
|
|
|
config MFD_MAX8925
|
|
bool "Maxim Semiconductor MAX8925 PMIC Support"
|
|
depends on I2C=y && GENERIC_HARDIRQS
|
|
select MFD_CORE
|
|
help
|
|
Say yes here to support for Maxim Semiconductor MAX8925. This is
|
|
a Power Management IC. This driver provies common support for
|
|
accessing the device, additional drivers must be enabled in order
|
|
to use the functionality of the device.
|
|
|
|
config MFD_MAX8997
|
|
bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
|
|
depends on I2C=y && GENERIC_HARDIRQS
|
|
select MFD_CORE
|
|
help
|
|
Say yes here to support for Maxim Semiconductor MAX8998/8966.
|
|
This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
|
|
MUIC controls on chip.
|
|
This driver provides common support for accessing the device;
|
|
additional drivers must be enabled in order to use the functionality
|
|
of the device.
|
|
|
|
config MFD_MAX8998
|
|
bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
|
|
depends on I2C=y && GENERIC_HARDIRQS
|
|
select MFD_CORE
|
|
help
|
|
Say yes here to support for Maxim Semiconductor MAX8998 and
|
|
National Semiconductor LP3974. This is a Power Management IC.
|
|
This driver provies common support for accessing the device,
|
|
additional drivers must be enabled in order to use the functionality
|
|
of the device.
|
|
|
|
config MFD_S5M_CORE
|
|
bool "SAMSUNG S5M Series Support"
|
|
depends on I2C=y && GENERIC_HARDIRQS
|
|
select MFD_CORE
|
|
select REGMAP_I2C
|
|
help
|
|
Support for the Samsung Electronics S5M MFD series.
|
|
This driver provies common support for accessing the device,
|
|
additional drivers must be enabled in order to use the functionality
|
|
of the device
|
|
|
|
config MFD_WM8400
|
|
tristate "Support Wolfson Microelectronics WM8400"
|
|
select MFD_CORE
|
|
depends on I2C
|
|
select REGMAP_I2C
|
|
help
|
|
Support for the Wolfson Microelecronics WM8400 PMIC and audio
|
|
CODEC. This driver provides common support for accessing
|
|
the device, additional drivers must be enabled in order to use
|
|
the functionality of the device.
|
|
|
|
config MFD_WM831X
|
|
bool
|
|
depends on GENERIC_HARDIRQS
|
|
|
|
config MFD_WM831X_I2C
|
|
bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
|
|
select MFD_CORE
|
|
select MFD_WM831X
|
|
select REGMAP_I2C
|
|
depends on I2C=y && GENERIC_HARDIRQS
|
|
help
|
|
Support for the Wolfson Microelecronics WM831x and WM832x PMICs
|
|
when controlled using I2C. This driver provides common support
|
|
for accessing the device, additional drivers must be enabled in
|
|
order to use the functionality of the device.
|
|
|
|
config MFD_WM831X_SPI
|
|
bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
|
|
select MFD_CORE
|
|
select MFD_WM831X
|
|
select REGMAP_SPI
|
|
depends on SPI_MASTER && GENERIC_HARDIRQS
|
|
help
|
|
Support for the Wolfson Microelecronics WM831x and WM832x PMICs
|
|
when controlled using SPI. This driver provides common support
|
|
for accessing the device, additional drivers must be enabled in
|
|
order to use the functionality of the device.
|
|
|
|
config MFD_WM8350
|
|
bool
|
|
depends on GENERIC_HARDIRQS
|
|
|
|
config MFD_WM8350_CONFIG_MODE_0
|
|
bool
|
|
depends on MFD_WM8350
|
|
|
|
config MFD_WM8350_CONFIG_MODE_1
|
|
bool
|
|
depends on MFD_WM8350
|
|
|
|
config MFD_WM8350_CONFIG_MODE_2
|
|
bool
|
|
depends on MFD_WM8350
|
|
|
|
config MFD_WM8350_CONFIG_MODE_3
|
|
bool
|
|
depends on MFD_WM8350
|
|
|
|
config MFD_WM8351_CONFIG_MODE_0
|
|
bool
|
|
depends on MFD_WM8350
|
|
|
|
config MFD_WM8351_CONFIG_MODE_1
|
|
bool
|
|
depends on MFD_WM8350
|
|
|
|
config MFD_WM8351_CONFIG_MODE_2
|
|
bool
|
|
depends on MFD_WM8350
|
|
|
|
config MFD_WM8351_CONFIG_MODE_3
|
|
bool
|
|
depends on MFD_WM8350
|
|
|
|
config MFD_WM8352_CONFIG_MODE_0
|
|
bool
|
|
depends on MFD_WM8350
|
|
|
|
config MFD_WM8352_CONFIG_MODE_1
|
|
bool
|
|
depends on MFD_WM8350
|
|
|
|
config MFD_WM8352_CONFIG_MODE_2
|
|
bool
|
|
depends on MFD_WM8350
|
|
|
|
config MFD_WM8352_CONFIG_MODE_3
|
|
bool
|
|
depends on MFD_WM8350
|
|
|
|
config MFD_WM8350_I2C
|
|
bool "Support Wolfson Microelectronics WM8350 with I2C"
|
|
select MFD_WM8350
|
|
depends on I2C=y && GENERIC_HARDIRQS
|
|
help
|
|
The WM8350 is an integrated audio and power management
|
|
subsystem with watchdog and RTC functionality for embedded
|
|
systems. This option enables core support for the WM8350 with
|
|
I2C as the control interface. Additional options must be
|
|
selected to enable support for the functionality of the chip.
|
|
|
|
config MFD_WM8994
|
|
bool "Support Wolfson Microelectronics WM8994"
|
|
select MFD_CORE
|
|
select REGMAP_I2C
|
|
select REGMAP_IRQ
|
|
depends on I2C=y && GENERIC_HARDIRQS
|
|
help
|
|
The WM8994 is a highly integrated hi-fi CODEC designed for
|
|
smartphone applicatiosn. As well as audio functionality it
|
|
has on board GPIO and regulator functionality which is
|
|
supported via the relevant subsystems. This driver provides
|
|
core support for the WM8994, in order to use the actual
|
|
functionaltiy of the device other drivers must be enabled.
|
|
|
|
config MFD_PCF50633
|
|
tristate "Support for NXP PCF50633"
|
|
depends on I2C
|
|
select REGMAP_I2C
|
|
help
|
|
Say yes here if you have NXP PCF50633 chip on your board.
|
|
This core driver provides register access and IRQ handling
|
|
facilities, and registers devices for the various functions
|
|
so that function-specific drivers can bind to them.
|
|
|
|
config PCF50633_ADC
|
|
tristate "Support for NXP PCF50633 ADC"
|
|
depends on MFD_PCF50633
|
|
help
|
|
Say yes here if you want to include support for ADC in the
|
|
NXP PCF50633 chip.
|
|
|
|
config PCF50633_GPIO
|
|
tristate "Support for NXP PCF50633 GPIO"
|
|
depends on MFD_PCF50633
|
|
help
|
|
Say yes here if you want to include support GPIO for pins on
|
|
the PCF50633 chip.
|
|
|
|
config MFD_MC13783
|
|
tristate
|
|
|
|
config MFD_MC13XXX
|
|
tristate "Support Freescale MC13783 and MC13892"
|
|
depends on SPI_MASTER
|
|
select MFD_CORE
|
|
select MFD_MC13783
|
|
help
|
|
Support for the Freescale (Atlas) PMIC and audio CODECs
|
|
MC13783 and MC13892.
|
|
This driver provides common support for accessing the device,
|
|
additional drivers must be enabled in order to use the
|
|
functionality of the device.
|
|
|
|
config ABX500_CORE
|
|
bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
|
|
default y if ARCH_U300 || ARCH_U8500
|
|
help
|
|
Say yes here if you have the ABX500 Mixed Signal IC family
|
|
chips. This core driver expose register access functions.
|
|
Functionality specific drivers using these functions can
|
|
remain unchanged when IC changes. Binding of the functions to
|
|
actual register access is done by the IC core driver.
|
|
|
|
config AB3100_CORE
|
|
bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
|
|
depends on I2C=y && ABX500_CORE
|
|
select MFD_CORE
|
|
default y if ARCH_U300
|
|
help
|
|
Select this to enable the AB3100 Mixed Signal IC core
|
|
functionality. This connects to a AB3100 on the I2C bus
|
|
and expose a number of symbols needed for dependent devices
|
|
to read and write registers and subscribe to events from
|
|
this multi-functional IC. This is needed to use other features
|
|
of the AB3100 such as battery-backed RTC, charging control,
|
|
LEDs, vibrator, system power and temperature, power management
|
|
and ALSA sound.
|
|
|
|
config AB3100_OTP
|
|
tristate "ST-Ericsson AB3100 OTP functions"
|
|
depends on AB3100_CORE
|
|
default y if AB3100_CORE
|
|
help
|
|
Select this to enable the AB3100 Mixed Signal IC OTP (one-time
|
|
programmable memory) support. This exposes a sysfs file to read
|
|
out OTP values.
|
|
|
|
config EZX_PCAP
|
|
bool "PCAP Support"
|
|
depends on GENERIC_HARDIRQS && SPI_MASTER
|
|
help
|
|
This enables the PCAP ASIC present on EZX Phones. This is
|
|
needed for MMC, TouchScreen, Sound, USB, etc..
|
|
|
|
config AB5500_CORE
|
|
bool "ST-Ericsson AB5500 Mixed Signal Power Management chip"
|
|
depends on ABX500_CORE && MFD_DB5500_PRCMU
|
|
select MFD_CORE
|
|
help
|
|
Select this option to enable access to AB5500 power management
|
|
chip. This connects to the db5500 chip via the I2C bus via PRCMU.
|
|
This chip embeds various other multimedia funtionalities as well.
|
|
|
|
config AB5500_DEBUG
|
|
bool "Enable debug info via debugfs"
|
|
depends on AB5500_CORE && DEBUG_FS
|
|
default y if DEBUG_FS
|
|
help
|
|
Select this option if you want debug information from the AB5500
|
|
using the debug filesystem, debugfs.
|
|
|
|
config AB8500_CORE
|
|
bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
|
|
depends on GENERIC_HARDIRQS && ABX500_CORE
|
|
select MFD_CORE
|
|
help
|
|
Select this option to enable access to AB8500 power management
|
|
chip. This connects to U8500 either on the SSP/SPI bus (deprecated
|
|
since hardware version v1.0) or the I2C bus via PRCMU. It also adds
|
|
the irq_chip parts for handling the Mixed Signal chip events.
|
|
This chip embeds various other multimedia funtionalities as well.
|
|
|
|
config AB8500_I2C_CORE
|
|
bool "AB8500 register access via PRCMU I2C"
|
|
depends on AB8500_CORE && MFD_DB8500_PRCMU
|
|
default y
|
|
help
|
|
This enables register access to the AB8500 chip via PRCMU I2C.
|
|
The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
|
|
the I2C bus is connected to the Power Reset
|
|
and Mangagement Unit, PRCMU.
|
|
|
|
config AB8500_DEBUG
|
|
bool "Enable debug info via debugfs"
|
|
depends on AB8500_CORE && DEBUG_FS
|
|
default y if DEBUG_FS
|
|
help
|
|
Select this option if you want debug information using the debug
|
|
filesystem, debugfs.
|
|
|
|
config AB8500_GPADC
|
|
bool "AB8500 GPADC driver"
|
|
depends on AB8500_CORE && REGULATOR_AB8500
|
|
default y
|
|
help
|
|
AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
|
|
|
|
config MFD_DB8500_PRCMU
|
|
bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
|
|
depends on UX500_SOC_DB8500
|
|
select MFD_CORE
|
|
help
|
|
Select this option to enable support for the DB8500 Power Reset
|
|
and Control Management Unit. This is basically an autonomous
|
|
system controller running an XP70 microprocessor, which is accessed
|
|
through a register map.
|
|
|
|
config MFD_DB5500_PRCMU
|
|
bool "ST-Ericsson DB5500 Power Reset Control Management Unit"
|
|
depends on UX500_SOC_DB5500
|
|
select MFD_CORE
|
|
help
|
|
Select this option to enable support for the DB5500 Power Reset
|
|
and Control Management Unit. This is basically an autonomous
|
|
system controller running an XP70 microprocessor, which is accessed
|
|
through a register map.
|
|
|
|
config MFD_CS5535
|
|
tristate "Support for CS5535 and CS5536 southbridge core functions"
|
|
select MFD_CORE
|
|
depends on PCI && X86
|
|
---help---
|
|
This is the core driver for CS5535/CS5536 MFD functions. This is
|
|
necessary for using the board's GPIO and MFGPT functionality.
|
|
|
|
config MFD_TIMBERDALE
|
|
tristate "Support for the Timberdale FPGA"
|
|
select MFD_CORE
|
|
depends on PCI && GPIOLIB
|
|
---help---
|
|
This is the core driver for the timberdale FPGA. This device is a
|
|
multifunction device which exposes numerous platform devices.
|
|
|
|
The timberdale FPGA can be found on the Intel Atom development board
|
|
for in-vehicle infontainment, called Russellville.
|
|
|
|
config LPC_SCH
|
|
tristate "Intel SCH LPC"
|
|
depends on PCI
|
|
select MFD_CORE
|
|
help
|
|
LPC bridge function of the Intel SCH provides support for
|
|
System Management Bus and General Purpose I/O.
|
|
|
|
config MFD_RDC321X
|
|
tristate "Support for RDC-R321x southbridge"
|
|
select MFD_CORE
|
|
depends on PCI
|
|
help
|
|
Say yes here if you want to have support for the RDC R-321x SoC
|
|
southbridge which provides access to GPIOs and Watchdog using the
|
|
southbridge PCI device configuration space.
|
|
|
|
config MFD_JANZ_CMODIO
|
|
tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
|
|
select MFD_CORE
|
|
depends on PCI
|
|
help
|
|
This is the core driver for the Janz CMOD-IO PCI MODULbus
|
|
carrier board. This device is a PCI to MODULbus bridge which may
|
|
host many different types of MODULbus daughterboards, including
|
|
CAN and GPIO controllers.
|
|
|
|
config MFD_JZ4740_ADC
|
|
bool "Support for the JZ4740 SoC ADC core"
|
|
select MFD_CORE
|
|
select GENERIC_IRQ_CHIP
|
|
depends on MACH_JZ4740
|
|
help
|
|
Say yes here if you want support for the ADC unit in the JZ4740 SoC.
|
|
This driver is necessary for jz4740-battery and jz4740-hwmon driver.
|
|
|
|
config MFD_VX855
|
|
tristate "Support for VIA VX855/VX875 integrated south bridge"
|
|
depends on PCI
|
|
select MFD_CORE
|
|
help
|
|
Say yes here to enable support for various functions of the
|
|
VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
|
|
and/or vx855_gpio drivers for this to do anything useful.
|
|
|
|
config MFD_WL1273_CORE
|
|
tristate "Support for TI WL1273 FM radio."
|
|
depends on I2C
|
|
select MFD_CORE
|
|
default n
|
|
help
|
|
This is the core driver for the TI WL1273 FM radio. This MFD
|
|
driver connects the radio-wl1273 V4L2 module and the wl1273
|
|
audio codec.
|
|
|
|
config MFD_OMAP_USB_HOST
|
|
bool "Support OMAP USBHS core driver"
|
|
depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
|
|
default y
|
|
help
|
|
This is the core driver for the OAMP EHCI and OHCI drivers.
|
|
This MFD driver does the required setup functionalities for
|
|
OMAP USB Host drivers.
|
|
|
|
config MFD_PM8XXX
|
|
tristate
|
|
|
|
config MFD_PM8921_CORE
|
|
tristate "Qualcomm PM8921 PMIC chip"
|
|
depends on MSM_SSBI
|
|
select MFD_CORE
|
|
select MFD_PM8XXX
|
|
help
|
|
If you say yes to this option, support will be included for the
|
|
built-in PM8921 PMIC chip.
|
|
|
|
This is required if your board has a PM8921 and uses its features,
|
|
such as: MPPs, GPIOs, regulators, interrupts, and PWM.
|
|
|
|
Say M here if you want to include support for PM8921 chip as a module.
|
|
This will build a module called "pm8921-core".
|
|
|
|
config MFD_PM8XXX_IRQ
|
|
bool "Support for Qualcomm PM8xxx IRQ features"
|
|
depends on MFD_PM8XXX
|
|
default y if MFD_PM8XXX
|
|
help
|
|
This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
|
|
|
|
This is required to use certain other PM 8xxx features, such as GPIO
|
|
and MPP.
|
|
|
|
config TPS65911_COMPARATOR
|
|
tristate
|
|
|
|
config MFD_AAT2870_CORE
|
|
bool "Support for the AnalogicTech AAT2870"
|
|
select MFD_CORE
|
|
depends on I2C=y && GPIOLIB
|
|
help
|
|
If you say yes here you get support for the AAT2870.
|
|
This driver provides common support for accessing the device,
|
|
additional drivers must be enabled in order to use the
|
|
functionality of the device.
|
|
|
|
config MFD_INTEL_MSIC
|
|
bool "Support for Intel MSIC"
|
|
depends on INTEL_SCU_IPC
|
|
select MFD_CORE
|
|
help
|
|
Select this option to enable access to Intel MSIC (Avatele
|
|
Passage) chip. This chip embeds audio, battery, GPIO, etc.
|
|
devices used in Intel Medfield platforms.
|
|
|
|
endmenu
|
|
endif
|
|
|
|
menu "Multimedia Capabilities Port drivers"
|
|
depends on ARCH_SA1100
|
|
|
|
config MCP
|
|
tristate
|
|
|
|
# Interface drivers
|
|
config MCP_SA11X0
|
|
tristate "Support SA11x0 MCP interface"
|
|
depends on ARCH_SA1100
|
|
select MCP
|
|
|
|
# Chip drivers
|
|
config MCP_UCB1200
|
|
tristate "Support for UCB1200 / UCB1300"
|
|
depends on MCP
|
|
|
|
config MCP_UCB1200_TS
|
|
tristate "Touchscreen interface support"
|
|
depends on MCP_UCB1200 && INPUT
|
|
|
|
endmenu
|