Re: [RFC PATCH 04/06] input/rmi4: Config files and makefiles
On Sat, Nov 17, 2012 at 4:58 AM, Christopher Heiny wrote: > Infrastructure files for configuration and building. > > > Signed-off-by: Christopher Heiny > Cut blank line. > Cc: Dmitry Torokhov > Cc: Linus Walleij > Cc: Naveen Kumar Gaddipati > Cc: Joeri de Gram (...) > +++ b/drivers/input/rmi4/Makefile > @@ -0,0 +1,22 @@ > +obj-$(CONFIG_RMI4_BUS) += rmi_bus.o > +obj-$(CONFIG_RMI4_I2C) += rmi_i2c.o > +obj-$(CONFIG_RMI4_GENERIC) += rmi_driver.o rmi_f01.o > +obj-$(CONFIG_RMI4_F11) += rmi_f11.o > + > +ccflags-$(CONFIG_RMI4_DEBUG) += -DDEBUG > + >From here: > +ifeq ($(KERNELRELEASE),) > + > +# KERNELDIR ?= /home/ > +PWD := $(shell pwd) > + > +.PHONY: build clean > + > +build: > + $(MAKE) -C $(KERNELDIR) M=$(PWD) modules > + > +clean: > + rm -rf *.o *~ core .depend .*.cmd *.ko *.mod.c > + > +endif This stuff looks weird. Like some local build rule to just rebuild this part, and the commented-out Android thing is really just cruft. Just delete all this, keep it in your private delta if you need it. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [RFC PATCH 04/06] input/rmi4: Config files and makefiles
On Sat, Nov 17, 2012 at 4:58 AM, Christopher Heiny che...@synaptics.com wrote: Infrastructure files for configuration and building. Signed-off-by: Christopher Heiny che...@synaptics.com Cut blank line. Cc: Dmitry Torokhov dmitry.torok...@gmail.com Cc: Linus Walleij linus.wall...@stericsson.com Cc: Naveen Kumar Gaddipati naveen.gaddip...@stericsson.com Cc: Joeri de Gram j.de.g...@gmail.com (...) +++ b/drivers/input/rmi4/Makefile @@ -0,0 +1,22 @@ +obj-$(CONFIG_RMI4_BUS) += rmi_bus.o +obj-$(CONFIG_RMI4_I2C) += rmi_i2c.o +obj-$(CONFIG_RMI4_GENERIC) += rmi_driver.o rmi_f01.o +obj-$(CONFIG_RMI4_F11) += rmi_f11.o + +ccflags-$(CONFIG_RMI4_DEBUG) += -DDEBUG + From here: +ifeq ($(KERNELRELEASE),) + +# KERNELDIR ?= /home/AndroidKernelDirectory +PWD := $(shell pwd) + +.PHONY: build clean + +build: + $(MAKE) -C $(KERNELDIR) M=$(PWD) modules + +clean: + rm -rf *.o *~ core .depend .*.cmd *.ko *.mod.c + +endif This stuff looks weird. Like some local build rule to just rebuild this part, and the commented-out Android thing is really just cruft. Just delete all this, keep it in your private delta if you need it. Yours, Linus Walleij -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[RFC PATCH 04/06] input/rmi4: Config files and makefiles
Infrastructure files for configuration and building. Signed-off-by: Christopher Heiny Cc: Dmitry Torokhov Cc: Linus Walleij Cc: Naveen Kumar Gaddipati Cc: Joeri de Gram --- drivers/input/Kconfig |2 + drivers/input/Makefile |3 ++ drivers/input/rmi4/Kconfig | 76 +++ drivers/input/rmi4/Makefile | 22 4 files changed, 103 insertions(+), 0 deletions(-) diff --git a/drivers/input/Kconfig b/drivers/input/Kconfig index 55f7e57..2c543c0 100644 --- a/drivers/input/Kconfig +++ b/drivers/input/Kconfig @@ -188,6 +188,8 @@ source "drivers/input/touchscreen/Kconfig" source "drivers/input/misc/Kconfig" +source "drivers/input/rmi4/Kconfig" + endif menu "Hardware I/O ports" diff --git a/drivers/input/Makefile b/drivers/input/Makefile index 5ca3f63..88354fc 100644 --- a/drivers/input/Makefile +++ b/drivers/input/Makefile @@ -24,4 +24,7 @@ obj-$(CONFIG_INPUT_TABLET)+= tablet/ obj-$(CONFIG_INPUT_TOUCHSCREEN)+= touchscreen/ obj-$(CONFIG_INPUT_MISC) += misc/ +obj-y += rmi4/ + obj-$(CONFIG_INPUT_APMPOWER) += apm-power.o + diff --git a/drivers/input/rmi4/Kconfig b/drivers/input/rmi4/Kconfig new file mode 100644 index 000..41cbbee --- /dev/null +++ b/drivers/input/rmi4/Kconfig @@ -0,0 +1,76 @@ +# +# RMI4 configuration +# +config RMI4_BUS + bool "Synaptics RMI4 bus support" + help + Say Y here if you want to support the Synaptics RMI4 bus. This is + required for all RMI4 device support. + + If unsure, say Y. + + This feature is not currently available as a loadable module. + +config RMI4_DEBUG + bool "RMI4 Debugging" + depends on RMI4_BUS + select DEBUG_FS + help + Say Y here to enable debug feature in the RMI4 driver. + + Note that the RMI4 driver debug features can generate a lot of + output (potentially clogging up your dmesg output) and generally + slow down driver operation. It's recommended to enable them only + if you are actively developing/debugging RMI4 features. + + If unsure, say N. + +config RMI4_I2C + bool "RMI4 I2C Support" + depends on RMI4_BUS && I2C + help + Say Y here if you want to support RMI4 devices connected to an I2C + bus. + + If unsure, say Y. + + This feature is not currently available as a loadable module. + +config RMI4_GENERIC + bool "RMI4 Generic driver" + depends on RMI4_BUS + help + Say Y here if you want to support generic RMI4 devices. + + This is pretty much required if you want to do anything useful with + your RMI device. + + This feature is not currently available as a loadable module. + +config RMI4_F11 + tristate "RMI4 Function 11 (2D pointing)" + depends on RMI4_BUS && RMI4_GENERIC + help + Say Y here if you want to add support for RMI4 function 11. + + Function 11 provides 2D multifinger pointing for touchscreens and + touchpads. For sensors that support relative pointing, F11 also + provides mouse input. + + To compile this driver as a module, choose M here: the + module will be called rmi-f11. + +config RMI4_F11_PEN + bool "RMI4 F11 Pen Support" + depends on RMI4_F11 + help + Say Y here to add support for pen input to RMI4 function 11. + + If this feature is enabled, when pen inputs are detected they + will be reported to the input stream as MT_TOOL_PEN. Otherwise, + pens will be treated the same as fingers. + + Not all UI implementations deal gracefully with pen discrimination. + If your system is not recognizing pen touches and you know your + sensor supports pen input, you probably want to turn this feature + off. diff --git a/drivers/input/rmi4/Makefile b/drivers/input/rmi4/Makefile new file mode 100644 index 000..8882c3d --- /dev/null +++ b/drivers/input/rmi4/Makefile @@ -0,0 +1,22 @@ +obj-$(CONFIG_RMI4_BUS) += rmi_bus.o +obj-$(CONFIG_RMI4_I2C) += rmi_i2c.o +obj-$(CONFIG_RMI4_GENERIC) += rmi_driver.o rmi_f01.o +obj-$(CONFIG_RMI4_F11) += rmi_f11.o + +ccflags-$(CONFIG_RMI4_DEBUG) += -DDEBUG + +ifeq ($(KERNELRELEASE),) + +# KERNELDIR ?= /home/ +PWD := $(shell pwd) + +.PHONY: build clean + +build: + $(MAKE) -C $(KERNELDIR) M=$(PWD) modules + +clean: + rm -rf *.o *~ core .depend .*.cmd *.ko *.mod.c + +endif + -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[RFC PATCH 04/06] input/rmi4: Config files and makefiles
Infrastructure files for configuration and building. Signed-off-by: Christopher Heiny che...@synaptics.com Cc: Dmitry Torokhov dmitry.torok...@gmail.com Cc: Linus Walleij linus.wall...@stericsson.com Cc: Naveen Kumar Gaddipati naveen.gaddip...@stericsson.com Cc: Joeri de Gram j.de.g...@gmail.com --- drivers/input/Kconfig |2 + drivers/input/Makefile |3 ++ drivers/input/rmi4/Kconfig | 76 +++ drivers/input/rmi4/Makefile | 22 4 files changed, 103 insertions(+), 0 deletions(-) diff --git a/drivers/input/Kconfig b/drivers/input/Kconfig index 55f7e57..2c543c0 100644 --- a/drivers/input/Kconfig +++ b/drivers/input/Kconfig @@ -188,6 +188,8 @@ source drivers/input/touchscreen/Kconfig source drivers/input/misc/Kconfig +source drivers/input/rmi4/Kconfig + endif menu Hardware I/O ports diff --git a/drivers/input/Makefile b/drivers/input/Makefile index 5ca3f63..88354fc 100644 --- a/drivers/input/Makefile +++ b/drivers/input/Makefile @@ -24,4 +24,7 @@ obj-$(CONFIG_INPUT_TABLET)+= tablet/ obj-$(CONFIG_INPUT_TOUCHSCREEN)+= touchscreen/ obj-$(CONFIG_INPUT_MISC) += misc/ +obj-y += rmi4/ + obj-$(CONFIG_INPUT_APMPOWER) += apm-power.o + diff --git a/drivers/input/rmi4/Kconfig b/drivers/input/rmi4/Kconfig new file mode 100644 index 000..41cbbee --- /dev/null +++ b/drivers/input/rmi4/Kconfig @@ -0,0 +1,76 @@ +# +# RMI4 configuration +# +config RMI4_BUS + bool Synaptics RMI4 bus support + help + Say Y here if you want to support the Synaptics RMI4 bus. This is + required for all RMI4 device support. + + If unsure, say Y. + + This feature is not currently available as a loadable module. + +config RMI4_DEBUG + bool RMI4 Debugging + depends on RMI4_BUS + select DEBUG_FS + help + Say Y here to enable debug feature in the RMI4 driver. + + Note that the RMI4 driver debug features can generate a lot of + output (potentially clogging up your dmesg output) and generally + slow down driver operation. It's recommended to enable them only + if you are actively developing/debugging RMI4 features. + + If unsure, say N. + +config RMI4_I2C + bool RMI4 I2C Support + depends on RMI4_BUS I2C + help + Say Y here if you want to support RMI4 devices connected to an I2C + bus. + + If unsure, say Y. + + This feature is not currently available as a loadable module. + +config RMI4_GENERIC + bool RMI4 Generic driver + depends on RMI4_BUS + help + Say Y here if you want to support generic RMI4 devices. + + This is pretty much required if you want to do anything useful with + your RMI device. + + This feature is not currently available as a loadable module. + +config RMI4_F11 + tristate RMI4 Function 11 (2D pointing) + depends on RMI4_BUS RMI4_GENERIC + help + Say Y here if you want to add support for RMI4 function 11. + + Function 11 provides 2D multifinger pointing for touchscreens and + touchpads. For sensors that support relative pointing, F11 also + provides mouse input. + + To compile this driver as a module, choose M here: the + module will be called rmi-f11. + +config RMI4_F11_PEN + bool RMI4 F11 Pen Support + depends on RMI4_F11 + help + Say Y here to add support for pen input to RMI4 function 11. + + If this feature is enabled, when pen inputs are detected they + will be reported to the input stream as MT_TOOL_PEN. Otherwise, + pens will be treated the same as fingers. + + Not all UI implementations deal gracefully with pen discrimination. + If your system is not recognizing pen touches and you know your + sensor supports pen input, you probably want to turn this feature + off. diff --git a/drivers/input/rmi4/Makefile b/drivers/input/rmi4/Makefile new file mode 100644 index 000..8882c3d --- /dev/null +++ b/drivers/input/rmi4/Makefile @@ -0,0 +1,22 @@ +obj-$(CONFIG_RMI4_BUS) += rmi_bus.o +obj-$(CONFIG_RMI4_I2C) += rmi_i2c.o +obj-$(CONFIG_RMI4_GENERIC) += rmi_driver.o rmi_f01.o +obj-$(CONFIG_RMI4_F11) += rmi_f11.o + +ccflags-$(CONFIG_RMI4_DEBUG) += -DDEBUG + +ifeq ($(KERNELRELEASE),) + +# KERNELDIR ?= /home/AndroidKernelDirectory +PWD := $(shell pwd) + +.PHONY: build clean + +build: + $(MAKE) -C $(KERNELDIR) M=$(PWD) modules + +clean: + rm -rf *.o *~ core .depend .*.cmd *.ko *.mod.c + +endif + -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: [RFC PATCH 04/06] input/rmi4: Config files and makefiles
Linus Walleij wrote: > On Sat, Oct 6, 2012 at 6:10 AM, Christopher Heiny > wrote: > > (...) > > > diff --git a/drivers/input/rmi4/Kconfig b/drivers/input/rmi4/Kconfig > > (...) > > > +config RMI4_DEBUG > > + bool "RMI4 Debugging" > > + depends on RMI4_BUS > > select DEBUG_FS > > This has been illustrated many times in the review. You definatley > have code depending on debugfs when this is selected. Agreed.-- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: [RFC PATCH 04/06] input/rmi4: Config files and makefiles
Linus Walleij wrote: On Sat, Oct 6, 2012 at 6:10 AM, Christopher Heiny che...@synaptics.com wrote: (...) diff --git a/drivers/input/rmi4/Kconfig b/drivers/input/rmi4/Kconfig (...) +config RMI4_DEBUG + bool RMI4 Debugging + depends on RMI4_BUS select DEBUG_FS This has been illustrated many times in the review. You definatley have code depending on debugfs when this is selected. Agreed.-- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [RFC PATCH 04/06] input/rmi4: Config files and makefiles
On Sat, Oct 6, 2012 at 6:10 AM, Christopher Heiny wrote: (...) > diff --git a/drivers/input/rmi4/Kconfig b/drivers/input/rmi4/Kconfig (...) > +config RMI4_DEBUG > + bool "RMI4 Debugging" > + depends on RMI4_BUS select DEBUG_FS This has been illustrated many times in the review. You definatley have code depending on debugfs when this is selected. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [RFC PATCH 04/06] input/rmi4: Config files and makefiles
On Sat, Oct 6, 2012 at 6:10 AM, Christopher Heiny che...@synaptics.com wrote: (...) diff --git a/drivers/input/rmi4/Kconfig b/drivers/input/rmi4/Kconfig (...) +config RMI4_DEBUG + bool RMI4 Debugging + depends on RMI4_BUS select DEBUG_FS This has been illustrated many times in the review. You definatley have code depending on debugfs when this is selected. Yours, Linus Walleij -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[RFC PATCH 04/06] input/rmi4: Config files and makefiles
Not much to say here, except that we've reduced the number of different Kconfig options, which will hopefully make it easier to configure RMI4 support in kernels. Signed-off-by: Christopher Heiny Cc: Dmitry Torokhov Cc: Linus Walleij Cc: Naveen Kumar Gaddipati Cc: Joeri de Gram --- drivers/input/Kconfig |2 + drivers/input/Makefile |2 + drivers/input/rmi4/Kconfig | 86 +++ drivers/input/rmi4/Makefile | 26 + 4 files changed, 116 insertions(+), 0 deletions(-) diff --git a/drivers/input/Kconfig b/drivers/input/Kconfig index 55f7e57..2c543c0 100644 --- a/drivers/input/Kconfig +++ b/drivers/input/Kconfig @@ -188,6 +188,8 @@ source "drivers/input/touchscreen/Kconfig" source "drivers/input/misc/Kconfig" +source "drivers/input/rmi4/Kconfig" + endif menu "Hardware I/O ports" diff --git a/drivers/input/Makefile b/drivers/input/Makefile index 5ca3f63..571515a 100644 --- a/drivers/input/Makefile +++ b/drivers/input/Makefile @@ -24,4 +24,6 @@ obj-$(CONFIG_INPUT_TABLET)+= tablet/ obj-$(CONFIG_INPUT_TOUCHSCREEN)+= touchscreen/ obj-$(CONFIG_INPUT_MISC) += misc/ +obj-y += rmi4/ + obj-$(CONFIG_INPUT_APMPOWER) += apm-power.o diff --git a/drivers/input/rmi4/Kconfig b/drivers/input/rmi4/Kconfig new file mode 100644 index 000..fa12638 --- /dev/null +++ b/drivers/input/rmi4/Kconfig @@ -0,0 +1,86 @@ +# +# RMI4 configuration +# +config RMI4_BUS + bool "Synaptics RMI4 bus support" + help + Say Y here if you want to support the Synaptics RMI4 bus. This is + required for all RMI4 device support. + + If unsure, say Y. + + This feature is not currently available as a loadable module. + +config RMI4_DEBUG + bool "RMI4 Debugging" + depends on RMI4_BUS + help + Say Y here to enable debug feature in the RMI4 driver. + + Note that the RMI4 driver debug features can generate a lot of + output (potentially clogging up your dmesg output) and generally + slow down driver operation. It's recommended to enable them only + if you are actively developing/debugging RMI4 features. + + If unsure, say N. + +config RMI4_I2C + bool "RMI4 I2C Support" + depends on RMI4_BUS && I2C + help + Say Y here if you want to support RMI4 devices connected to an I2C + bus. + + If unsure, say Y. + + This feature is not currently available as a loadable module. + +config RMI4_GENERIC + bool "RMI4 Generic driver" + depends on RMI4_BUS + help + Say Y here if you want to support generic RMI4 devices. + + This is pretty much required if you want to do anything useful with + your RMI device. + + This feature is not currently available as a loadable module. + +config RMI4_F11 + tristate "RMI4 Function 11 (2D pointing)" + depends on RMI4_BUS && RMI4_GENERIC + help + Say Y here if you want to add support for RMI4 function 11. + + Function 11 provides 2D multifinger pointing for touchscreens and + touchpads. For sensors that support relative pointing, F11 also + provides mouse input. + + To compile this driver as a module, choose M here: the + module will be called rmi-f11. + +config RMI4_F11_PEN + bool "RMI4 F11 Pen Support" + depends on RMI4_F11 + help + Say Y here to add support for pen input to RMI4 function 11. + + If this feature is enabled, when pen inputs are detected they + will be reported to the input stream as MT_TOOL_PEN. Otherwise, + pens will be treated the same as fingers. + + Not all UI implementations deal gracefully with pen discrimination. + If your system is not recognizing pen touches and you know your + sensor supports pen input, you probably want to turn this feature + off. + +config RMI4_VIRTUAL_BUTTON + tristate "RMI4 Vitual Button" + depends on RMI4_F11 + help + Say Y here if you want to add support for RMI4 virtual button to F11. + + The virtual button feature implement the virtual button device in + certain RMI4 touch sensors. + + This works only if your sensor supports F11 gestures. diff --git a/drivers/input/rmi4/Makefile b/drivers/input/rmi4/Makefile new file mode 100644 index 000..1480689 --- /dev/null +++ b/drivers/input/rmi4/Makefile @@ -0,0 +1,26 @@ +obj-$(CONFIG_RMI4_BUS) += rmi_bus.o +obj-$(CONFIG_RMI4_I2C) += rmi_i2c.o +obj-$(CONFIG_RMI4_GENERIC) += rmi_driver.o rmi_f01.o +obj-$(CONFIG_RMI4_F11) += rmi_f11.o + +ccflags-$(CONFIG_RMI4_DEBUG) += -DDEBUG + +ifeq ($(KERNELRELEASE),) + +# KERNELDIR ?= /home/ +PWD := $(shell pwd) + +.PHONY: build clean + +build: + $(MAKE) -C $(KERNELDIR) M=$(PWD) modules + +clean: + rm -rf *.o *~ core .depend .*.cmd *.ko *.mod.c +else + +$(info Building with
[RFC PATCH 04/06] input/rmi4: Config files and makefiles
Not much to say here, except that we've reduced the number of different Kconfig options, which will hopefully make it easier to configure RMI4 support in kernels. Signed-off-by: Christopher Heiny che...@synaptics.com Cc: Dmitry Torokhov dmitry.torok...@gmail.com Cc: Linus Walleij linus.wall...@stericsson.com Cc: Naveen Kumar Gaddipati naveen.gaddip...@stericsson.com Cc: Joeri de Gram j.de.g...@gmail.com --- drivers/input/Kconfig |2 + drivers/input/Makefile |2 + drivers/input/rmi4/Kconfig | 86 +++ drivers/input/rmi4/Makefile | 26 + 4 files changed, 116 insertions(+), 0 deletions(-) diff --git a/drivers/input/Kconfig b/drivers/input/Kconfig index 55f7e57..2c543c0 100644 --- a/drivers/input/Kconfig +++ b/drivers/input/Kconfig @@ -188,6 +188,8 @@ source drivers/input/touchscreen/Kconfig source drivers/input/misc/Kconfig +source drivers/input/rmi4/Kconfig + endif menu Hardware I/O ports diff --git a/drivers/input/Makefile b/drivers/input/Makefile index 5ca3f63..571515a 100644 --- a/drivers/input/Makefile +++ b/drivers/input/Makefile @@ -24,4 +24,6 @@ obj-$(CONFIG_INPUT_TABLET)+= tablet/ obj-$(CONFIG_INPUT_TOUCHSCREEN)+= touchscreen/ obj-$(CONFIG_INPUT_MISC) += misc/ +obj-y += rmi4/ + obj-$(CONFIG_INPUT_APMPOWER) += apm-power.o diff --git a/drivers/input/rmi4/Kconfig b/drivers/input/rmi4/Kconfig new file mode 100644 index 000..fa12638 --- /dev/null +++ b/drivers/input/rmi4/Kconfig @@ -0,0 +1,86 @@ +# +# RMI4 configuration +# +config RMI4_BUS + bool Synaptics RMI4 bus support + help + Say Y here if you want to support the Synaptics RMI4 bus. This is + required for all RMI4 device support. + + If unsure, say Y. + + This feature is not currently available as a loadable module. + +config RMI4_DEBUG + bool RMI4 Debugging + depends on RMI4_BUS + help + Say Y here to enable debug feature in the RMI4 driver. + + Note that the RMI4 driver debug features can generate a lot of + output (potentially clogging up your dmesg output) and generally + slow down driver operation. It's recommended to enable them only + if you are actively developing/debugging RMI4 features. + + If unsure, say N. + +config RMI4_I2C + bool RMI4 I2C Support + depends on RMI4_BUS I2C + help + Say Y here if you want to support RMI4 devices connected to an I2C + bus. + + If unsure, say Y. + + This feature is not currently available as a loadable module. + +config RMI4_GENERIC + bool RMI4 Generic driver + depends on RMI4_BUS + help + Say Y here if you want to support generic RMI4 devices. + + This is pretty much required if you want to do anything useful with + your RMI device. + + This feature is not currently available as a loadable module. + +config RMI4_F11 + tristate RMI4 Function 11 (2D pointing) + depends on RMI4_BUS RMI4_GENERIC + help + Say Y here if you want to add support for RMI4 function 11. + + Function 11 provides 2D multifinger pointing for touchscreens and + touchpads. For sensors that support relative pointing, F11 also + provides mouse input. + + To compile this driver as a module, choose M here: the + module will be called rmi-f11. + +config RMI4_F11_PEN + bool RMI4 F11 Pen Support + depends on RMI4_F11 + help + Say Y here to add support for pen input to RMI4 function 11. + + If this feature is enabled, when pen inputs are detected they + will be reported to the input stream as MT_TOOL_PEN. Otherwise, + pens will be treated the same as fingers. + + Not all UI implementations deal gracefully with pen discrimination. + If your system is not recognizing pen touches and you know your + sensor supports pen input, you probably want to turn this feature + off. + +config RMI4_VIRTUAL_BUTTON + tristate RMI4 Vitual Button + depends on RMI4_F11 + help + Say Y here if you want to add support for RMI4 virtual button to F11. + + The virtual button feature implement the virtual button device in + certain RMI4 touch sensors. + + This works only if your sensor supports F11 gestures. diff --git a/drivers/input/rmi4/Makefile b/drivers/input/rmi4/Makefile new file mode 100644 index 000..1480689 --- /dev/null +++ b/drivers/input/rmi4/Makefile @@ -0,0 +1,26 @@ +obj-$(CONFIG_RMI4_BUS) += rmi_bus.o +obj-$(CONFIG_RMI4_I2C) += rmi_i2c.o +obj-$(CONFIG_RMI4_GENERIC) += rmi_driver.o rmi_f01.o +obj-$(CONFIG_RMI4_F11) += rmi_f11.o + +ccflags-$(CONFIG_RMI4_DEBUG) += -DDEBUG + +ifeq ($(KERNELRELEASE),) + +# KERNELDIR ?= /home/AndroidKernelDirectory +PWD := $(shell pwd) + +.PHONY: build clean + +build: + $(MAKE) -C $(KERNELDIR)
