linux-toradex.git/drivers/input/misc/rb532_button.c, branch v4.11-rc6

MIPS: Remove all the uses of custom gpio.h

2015-09-03T10:08:02+00:00

Currently CONFIG_ARCH_HAVE_CUSTOM_GPIO_H is defined for all MIPS
machines, and each machine type provides its own gpio.h. However
only a handful really implement the GPIO API, most just forward
everythings to gpiolib.

The Alchemy machine is notable as it provides a system to allow
implementing the GPIO API at the board level. But it is not used by
any board currently supported, so it can also be removed.

For most machine types we can just remove the custom gpio.h, as well
as the custom wrappers if some exists. Some of the code found in
the wrappers must be moved to the respective GPIO driver.

A few more fixes are need in some drivers as they rely on linux/gpio.h
to provides some machine specific definitions, or used asm/gpio.h
instead of linux/gpio.h for the gpio API.

Signed-off-by: Alban Bedel 
Reviewed-by: Linus Walleij 
Cc: linux-mips@linux-mips.org
Cc: Hauke Mehrtens 
Cc: Rafał Miłecki 
Cc: Bartlomiej Zolnierkiewicz 
Cc: Tejun Heo 
Cc: Alexandre Courbot 
Cc: Dmitry Torokhov 
Cc: Florian Fainelli 
Cc: Manuel Lauss 
Cc: Joe Perches 
Cc: Daniel Walter 
Cc: Sergey Ryazanov 
Cc: Huacai Chen 
Cc: James Hartley 
Cc: Andrew Bresticker 
Cc: Paul Burton 
Cc: Jiri Kosina 
Cc: Bjorn Helgaas 
Cc: Wolfram Sang 
Cc: Randy Dunlap 
Cc: Varka Bhadram 
Cc: Masanari Iida 
Cc: Tomi Valkeinen 
Cc: Michael Buesch 
Cc: abdoulaye berthe 
Cc: linux-kernel@vger.kernel.org
Cc: linux-ide@vger.kernel.org
Cc: linux-gpio@vger.kernel.org
Cc: linux-input@vger.kernel.org
Cc: netdev@vger.kernel.org
Patchwork: https://patchwork.linux-mips.org/patch/10828/
Signed-off-by: Ralf Baechle

input: misc: drop owner assignment from platform_drivers

2014-10-20T14:20:40+00:00

A platform_driver does not need to set an owner, it will be populated by the
driver core.

Signed-off-by: Wolfram Sang

Input: rb532_button - remove redundant dev_set_drvdata

2013-09-18T14:53:41+00:00

Driver core sets the data to NULL upon release or probe
failure. Hence explicit setting is not necessary.

Signed-off-by: Sachin Kamat 
Signed-off-by: Dmitry Torokhov

Input: remove use of __devexit

2012-11-24T08:05:38+00:00

CONFIG_HOTPLUG is going away as an option so __devexit is no
longer needed.

Signed-off-by: Bill Pemberton 
Acked-by: Mark Brown 
Signed-off-by: Dmitry Torokhov

Input: remove use of __devinit

2012-11-24T08:05:19+00:00

CONFIG_HOTPLUG is going away as an option so __devinit is no longer
needed.

Signed-off-by: Bill Pemberton 
Acked-by: Mark Brown 
Acked-by: Javier Martinez Canillas 
Signed-off-by: Dmitry Torokhov

Input: remove use of __devexit_p

2012-11-24T08:03:48+00:00

CONFIG_HOTPLUG is going away as an option so __devexit_p is no longer
needed.

Signed-off-by: Bill Pemberton 
Acked-by: Russell King 
Signed-off-by: Dmitry Torokhov

Input: misc - use macro module_platform_driver()

2011-12-01T07:41:42+00:00

Commit 940ab88962bc1aff3273a8356d64577a6e386736 introduced a new macro to
save some platform_driver boilerplate code. Use it.

Signed-off-by: JJ Ding 
Signed-off-by: Dmitry Torokhov

Input: add driver for S1 button of rb532

2009-03-10T03:10:12+00:00

Mikrotik's Routerboard 532 has two builtin buttons, from which one
triggers a hardware reset. The other one is accessible through GPIO
pin 1. Sadly, this pin is being multiplexed with UART0 input, so
enabling it as interrupt source (as implied by the gpio-keys driver)
is not possible unless UART0 has been turned off. The later one though
is a rather bad idea as the Routerboard is an embedded device with
only a single serial port, so it's almost always used as serial
console device.

This patch adds a driver based on INPUT_POLLDEV, which disables the
UART and reconfigures GPIO pin 1 temporarily while reading the button
state.  This procedure works fine and has been tested as part of
another, unpublished driver for this device.

Signed-off-by: Phil Sutter 
Signed-off-by: Dmitry Torokhov