2b6a321da9
Synaptics uses the Register Mapped Interface (RMI) protocol as a communications interface for their devices. This driver adds the core functionality needed to interface with RMI4 devices. RMI devices can be connected to the host via several transport protocols and can supports a wide variety of functionality defined by RMI functions. Support for transport protocols and RMI functions are implemented in individual drivers. The RMI4 core driver uses a bus architecture to facilitate the various combinations of transport and function drivers needed by a particular device. Signed-off-by: Andrew Duggan <aduggan@synaptics.com> Signed-off-by: Christopher Heiny <cheiny@synaptics.com> Tested-by: Benjamin Tissoires <benjamin.tissoires@redhat.com> Tested-by: Linus Walleij <linus.walleij@linaro.org> Tested-by: Bjorn Andersson <bjorn.andersson@linaro.org> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
31 lines
909 B
Makefile
31 lines
909 B
Makefile
#
|
|
# Makefile for the input core drivers.
|
|
#
|
|
|
|
# Each configuration option enables a list of files.
|
|
|
|
obj-$(CONFIG_INPUT) += input-core.o
|
|
input-core-y := input.o input-compat.o input-mt.o ff-core.o
|
|
|
|
obj-$(CONFIG_INPUT_FF_MEMLESS) += ff-memless.o
|
|
obj-$(CONFIG_INPUT_POLLDEV) += input-polldev.o
|
|
obj-$(CONFIG_INPUT_SPARSEKMAP) += sparse-keymap.o
|
|
obj-$(CONFIG_INPUT_MATRIXKMAP) += matrix-keymap.o
|
|
|
|
obj-$(CONFIG_INPUT_LEDS) += input-leds.o
|
|
obj-$(CONFIG_INPUT_MOUSEDEV) += mousedev.o
|
|
obj-$(CONFIG_INPUT_JOYDEV) += joydev.o
|
|
obj-$(CONFIG_INPUT_EVDEV) += evdev.o
|
|
obj-$(CONFIG_INPUT_EVBUG) += evbug.o
|
|
|
|
obj-$(CONFIG_INPUT_KEYBOARD) += keyboard/
|
|
obj-$(CONFIG_INPUT_MOUSE) += mouse/
|
|
obj-$(CONFIG_INPUT_JOYSTICK) += joystick/
|
|
obj-$(CONFIG_INPUT_TABLET) += tablet/
|
|
obj-$(CONFIG_INPUT_TOUCHSCREEN) += touchscreen/
|
|
obj-$(CONFIG_INPUT_MISC) += misc/
|
|
|
|
obj-$(CONFIG_INPUT_APMPOWER) += apm-power.o
|
|
|
|
obj-$(CONFIG_RMI4_CORE) += rmi4/
|