Skip to contentSkip to conversation

DA9055 Onkey driver

PATCH In review Ashish Jangam 2 participants 2 messages Sep 14, 2012

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH 7/7 DA9055 Onkey driver

This is the ONKEY driver of the Dialog DA9055 PMIC and depends on the DA9055 MFD core driver.

This patch is functionally tested on SMDK6410 board.

---
 drivers/input/misc/Kconfig        |   10 +++
 drivers/input/misc/Makefile       |    1 +
 drivers/input/misc/da9055_onkey.c |  121 +++++++++++++++++++++++++++++++++++++
 3 files changed, 132 insertions(+), 0 deletions(-)
 create mode 100644 drivers/input/misc/da9055_onkey.c
drivers/input/misc/Kconfig +10 -0
index 7c0f1ec..6a45cb8 100644
@@ -486,6 +486,16 @@ config INPUT_DA9052_ONKEY
 	  To compile this driver as a module, choose M here: the
 	  module will be called da9052_onkey.
 
+config INPUT_DA9055_ONKEY
+	tristate "Dialog Semiconductor DA9055 ONKEY"
+	depends on MFD_DA9055
+	help
+	  Support the ONKEY of DA9055 PMICs as an input device
+	  reporting power button status.
+
+	  To compile this driver as a module, choose M here: the module
+	  will be called da9055_onkey.
+
 config INPUT_DM355EVM
 	tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
 	depends on MFD_DM355EVM_MSP
drivers/input/misc/Makefile +1 -0
index 83fe6f5..23347e3 100644
@@ -23,6 +23,7 @@ obj-$(CONFIG_INPUT_CMA3000)		+= cma3000_d0x.o
 obj-$(CONFIG_INPUT_CMA3000_I2C)		+= cma3000_d0x_i2c.o
 obj-$(CONFIG_INPUT_COBALT_BTNS)		+= cobalt_btns.o
 obj-$(CONFIG_INPUT_DA9052_ONKEY)	+= da9052_onkey.o
+obj-$(CONFIG_INPUT_DA9055_ONKEY)	+= da9055_onkey.o
 obj-$(CONFIG_INPUT_DM355EVM)		+= dm355evm_keys.o
 obj-$(CONFIG_INPUT_GP2A)		+= gp2ap002a00f.o
 obj-$(CONFIG_INPUT_GPIO_TILT_POLLED)	+= gpio_tilt_polled.o
drivers/input/misc/da9055_onkey.c new file +121 -0

121 lines not on this page · raw message

Signature · 1 line
1.7.0.4
#1 lore raw

drivers/input/misc/da9055_onkey.c line 25

Quoted 5 lines · Ashish Jangam
drivers/input/misc/da9055_onkey.c new file +5 -0
+static irqreturn_t da9055_onkey_irq(int irq, void *data)
+{
+	struct input_dev *input_dev = data;
+
+	input_report_key(input_dev, KEY_POWER, 1);

When do you send the release key event?

Overall driver looks like you can use the gpio-key driver with passing irq number, without passing gpio.

-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------