| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
android-samsung-30-wip-mergedown
* common/android-3.0:
Input: evdev - fix variable initialisation
Input: evdev - Add ioctl to block suspend while event queue is not empty.
Input: evdev - Don't hold wakelock when no data is available to user-space
net: wireless: bcmdhd: Increase pm_notify callback priority
net: wireless: bcmdhd: Fix crash on dhdsdio_probe_attach() failure
net: wireless: bcmdhd: Daemonize wl_event_handler
net: wireless: bcmdhd: Update to Version 5.90.195.23
net: wireless: bcmdhd: Update to Version 5.90.195.22
net: wireless: bcmdhd: Update to Version 5.90.195.19
net: wireless: bcmdhd: Update to Version 5.90.195.15
net: wireless: bcmdhd: Add WIPHY_FLAG_SUPPORTS_FW_ROAM flag
net: wireless: bcmdhd: Fake PNO event to wake up the wpa_supplicant
usb: gadget: android: Honor CONFIG_USB_GADGET_VBUS_DRAW
usb: gadget: Fix usb string id allocation
nl80211/cfg80211: Make addition of new sinfo fields safer
cfg80211/nl80211: Send AssocReq IEs to user space in AP mode
misc: remove android pmem driver, it's obsolete.
Revert "proc: enable writing to /proc/pid/mem"
ram_console: set CON_ANYTIME console flag
Conflicts:
drivers/misc/Kconfig
Change-Id: I7d64300b228a0fc05e700f283a02f830bcadd371
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Commit 509f87c5f564 (evdev - do not block waiting for an event if
fd
is nonblock) created a code path were it was possible to use retval
uninitialized.
This could lead to the xorg evdev input driver getting corrupt data
and refusing to work with log messages like
AUO-Pixcir touchscreen: Read error: Success
sg060_keys: Read error: Success
AUO-Pixcir touchscreen: Read error: Success
sg060_keys: Read error: Success
(for drivers auo-pixcir-ts and gpio-keys).
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add an ioctl, EVIOCSSUSPENDBLOCK, to enable a wakelock that will block
suspend while the event queue is not empty. This allows userspace code to
process input events while the device appears to be asleep.
The current code holds the wakelock for up 5 seconds for every input
device and client. This can prevent suspend if sensor with a high data
rate is active, even when that sensor is not capable of waking the
device once it is suspended.
Change-Id: I624d66ef30a0b3abb543685c343382b8419b42b9
Signed-off-by: Arve Hjønnevåg <arve@android.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
If there is no SYN_REPORT event in the buffer the buffer data is invisible
to user-space. The wakelock should not be held in this case.
Change-Id: Idae890ff0da8eb46a2cfce61a95b3a97252551ad
Signed-off-by: Arve Hjønnevåg <arve@android.com>
|
| |
| |
| |
| |
| | |
Change-Id: I9cddef63b40cd6bb8887244ac1db9c46713d1db9
Signed-off-by: Arve Hjønnevåg <arve@android.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
If a delay of 0 or some low value is passed from any apps,
then system can lock up.
Change-Id: I543d48a1e02becd1f74cc81e0212909d3e864082
Signed-off-by: Won Hyoung Lee <whlee@sta.samsung.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This makes the sensor quicker to respond when the light level changes,
and reduces the number of events sent when the light level is stable.
Change-Id: I7cc1912ff5f111b4890a38a14acc3f8996d74a66
Signed-off-by: Arve Hjønnevåg <arve@android.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Light sensor was delaying first time read to
poll delay milli seconds. This fix changes the
first time read delay to 50 milli seconds.
This ensures a valid first read with minimum delay.
Change-Id: Idd9ad6d51cf244131777ecab1f5526a952ed7d81
Signed-off-by: Vishnudev Ramakrishnan <vramakri@sta.samsung.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Driver changes to make light sensor value to be reported on
enabling light sensor.
- On enable, push a dummy value -1 to input subsystem
Change-Id: Icd154fc04ef78fcae2eadfde280abe19da6a7b2a
Signed-off-by: Vishnudev Ramakrishnan <vramakri@sta.samsung.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixed the following bugs in light sensor driver:
1. Eliminated error values from being considered as valid light values
2. Fix an off-by-one error in the averaging buffer
Change-Id: I7ec86ab0d3e423a0e736406c4f786d2933cb7e8d
Signed-off-by: Vishnudev Ramakrishnan <vramakri@sta.samsung.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This change fixes a bug in the proximity sensor.
The bug is that proximity sensor did not always report a value
when it turns on.
Change-Id: Ibe68d2b04242318629686fd740c652b7d20b6a33
Signed-off-by: Vishnudev Ramakrishnan <vramakri@sta.samsung.com>
|
| |
| |
| |
| |
| | |
Change-Id: Iee266f3d5ecff77ae6b4fb75c797620c9e29aa30
Signed-off-by: Arve Hjønnevåg <arve@android.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Correctly implement the MT protocol.
Use ABS_MT_PRESSURE for intensity information.
Use ABS_MT_TOUCH_MAJOR for touch width.
Instead of sending ABS_MT_TOUCH_MAJOR with a value of 0 to
indicate finger release, just omit the finger altogether.
If there are no fingers left, then send an empty SYN_MT_REPORT /
SYN_REPORT pair of events.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The gyro data rate should always be above or equal to the requested value.
0 to 105 : 105
106 to 210 : 210
211 to 420 : 420
421 and above : 840
Change-Id: I6185d2cf8c6fef72145229bd51f9bfbdfb5df28c
Signed-off-by: tim.sk.lee <tim.sk.lee@samsung.com>
|
| |
| |
| |
| |
| |
| |
| | |
Firmware a.9 solves an issue with touchkeys getting stuck on
and has increased sensitivity equivalent to rev 8.9.
Signed-off-by: Simon Wilson <simonwilson@google.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Firmware 9.9 has too low a sensitivity for the touchkeys so
stay on the previous revision (8.9) until the new revision
is ready.
Signed-off-by: Simon Wilson <simonwilson@google.com>
|
| |
| |
| |
| |
| |
| |
| | |
Fix the version check that determines which backlight code to use.
Change-Id: I85c5e745dd16b5600be23e05f9e94e1255b511f0
Signed-off-by: Rom Lemarchand <rlemarchand@sta.samsung.com>
|
| |
| |
| |
| |
| |
| |
| | |
Flash the latest firmware onto the touchkey device if needed.
Change-Id: Ia36c1e9a27d5497d1cef6583941f2907d4612d0e
Signed-off-by: Rom Lemarchand <rlemarchand@sta.samsung.com>
|
| |
| |
| |
| |
| |
| |
| | |
response
Change-Id: Ie19869d5228f150850d59e06c9be6e1bedf261de
Signed-off-by: tim.sk.lee <tim.sk.lee@samsung.com>
|
| |
| |
| |
| |
| |
| |
| | |
Adding driver to support the Atmel MaxTouch 224 multi-touch controller.
Change-Id: Ibf8de98c1f102e09f6204e7b57e49bcaf154f0af
Signed-off-by: Rom Lemarchand <rlemarchand@sta.samsung.com>
|
| |
| |
| |
| |
| |
| | |
Change-Id: I7cb7322e8028e6ce3af27cdf81e16393e1fe97e8
Signed-off-by: tim.sk.lee <tim.sk.lee@samsung.com>
Signed-off-by: Mathias Agopian <mathias@google.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fix enable_irq imbalance, start with irq disabled until driver
is enabled. Make irq_wake follow irq_enable so we don't block
sleep. Some other cleanups.
Change-Id: Ieee8c78034b79b94b625f82a1fd5c2cf2a35f825
Signed-off-by: Mike J. Chen <mjchen@sta.samsung.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
The IC provides both promixity and ambient light readings.
The driver provides output to userland via the input frameowork.
Change-Id: I40e1733d26e3fc035f73b47cb52d8750b4be8193
Signed-off-by: Mike J. Chen <mjchen@sta.samsung.com>
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Change-Id: Ib8744466edda655e7e4eec921ec55b98b7710ee7
Signed-off-by: Sang-Jun Park <sj2202.park@samsung.com
Signed-off-by: Jinho Kim <jinho96.kim@samsung.com>
Signed-off-by: Rom Lemarchand <rlemarchand@sta.samsung.com>
General cleanup of the driver, removing unused functions and sysfs interface
since it was agreed upon that userspace wouldn't control the backlight.
Adding delay when turning on the microcontroller to wait for the chip to be
ready.
Signed-off-by: Rom Lemarchand <rlemarchand@sta.samsung.com>
Switching to edge triggered interrupt.
This requires extra code to ignore spurious interrupts while powering on.
Signed-off-by: Rom Lemarchand <rlemarchand@sta.samsung.com>
Cypress made this change to ensure reported key statuses don't get out of
sync between user-space and the controller.
The basic idea is to read the status of all the keys at once on each read and
send all the relevant key states to user-space.
Signed-off-by: Rom Lemarchand <rlemarchand@sta.samsung.com>
Fixing the version check in the touchkey driver to account for older firmware
revs 0xc4 and above.
Signed-off-by: Rom Lemarchand <rlemarchand@sta.samsung.com>
|
|
|
|
|
| |
Change-Id: I29ccb32e795c5c3e4c51c3d3a209f5b55dfd7d94
Signed-off-by: Dima Zavin <dima@android.com>
|
|
|
|
|
|
|
|
|
|
| |
If there is a full packet in the buffer, and we overflow that buffer
right after checking for that condition, it would have been possible
for us to block indefinitely (rather, until the next full packet) even if
the file was marked as O_NONBLOCK.
Change-Id: Icd0f59f8cc98392be4c4d13bd45b5cf94317eb5a
Signed-off-by: Dima Zavin <dima@android.com>
|
|
|
|
|
| |
Change-Id: I5f0da721f74e5de111cffc7e7b375b72dd80e530
Signed-off-by: Dima Zavin <dima@android.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Without this, it was possible for the reader to get ahead of packet_head.
If the the input device generated a partial packet *right* after the
reader got ahead, then we can get into a situation where the device is
marked readable but read always returns 0 until the next packet is
finished (i.e a SYN is generated by the input driver).
This situation can also happen if we overflow the buffer while a reader
is trying to read an event out.
Change-Id: If01ab371bc7de1bf1f90c122dcc5a29242b01a09
Signed-off-by: Dima Zavin <dima@android.com>
|
|
|
|
|
|
|
|
|
| |
Add a board file option to gpio_input devices to make
calling enable_irq_wake conditional. Also disable the
wake irq when removing the device.
Change-Id: If933b9d3a751d89fa95ae3b7f739dfe70fcb23c8
Signed-off-by: Mike J. Chen <mjchen@sta.samsung.com>
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
mfd_get_data() has been removed from the MFD API.
Cc: Anirudh Ghayal <aghayal@codeaurora.org>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
|
| |
| |
| |
| |
| |
| |
| | |
mfd_get_data() has been removed from the MFD API.
Cc: Anirudh Ghayal <aghayal@codeaurora.org>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
|
|\ \
| |/ |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input
* 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input:
Input: sh_keysc - 8x8 MODE_6 fix
Input: omap-keypad - add missing input_sync()
Input: evdev - try to wake up readers only if we have full packet
Input: properly assign return value of clamp() macro.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
According to the data sheet for G4, AP4 and AG5 KEYSC MODE_6 is 8x8 keys.
Bump up MAXKEYS to 64 too.
Signed-off-by: Magnus Damm <damm@opensource.se>
Reviewed-by: Simon Horman <horms@verge.net.au>
Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Otherwise the updated evdev driver (commit cdda911c34006f1089f3c87b1a1f,
"Input: evdev - only signal polls on full packets") no longer works on
top of omap-keypad.
Tested on Amstrad Delta.
Signed-off-by: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
Reviewed-by: Henrik Rydberg <rydberg@euromail.se>
Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We should only wake waiters on the event device when we actually post
an EV_SYN/SYN_REPORT to the queue. Otherwise we end up making waiting
threads runnable only to go right back to sleep because the device
still isn't readable.
Reported-by: Jeffrey Brown <jeffbrown@android.com>
Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
[dtor@mail.ru: added mousedev changes]
Signed-off-by: Hans Petter Selasky <hselasky@c2i.net>
Cc: stable@kernel.org
Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
|
| | |
| | |
| | |
| | |
| | | |
Signed-off-by: jeffbrown@android.com
Change-Id: Ie170960df3c8ab4833ed686135dc8575cb9f2d48
|
| | |
| | |
| | |
| | |
| | | |
Signed-off-by: jeffbrown@android.com
Change-Id: I9bd2437503b48bf37f4d93505ccd2806e4aab977
|
| | |
| | |
| | |
| | |
| | | |
Change-Id: Ib8dd0ab6554e6b0e3798bf75d41f77ea0b20b8de
Signed-off-by: Colin Cross <ccross@android.com>
|
| | |
| | |
| | |
| | |
| | | |
Change-Id: I68e5451fef2e6f08bf1035077ea999e34a619f87
Signed-off-by: Colin Cross <ccross@android.com>
|
| | |
| | |
| | |
| | |
| | | |
Change-Id: Ief1ef44d98a197e5b457f5e8617c413e76e3c6d2
Signed-off-by: Benoit Goby <benoit@android.com>
|
| | |
| | |
| | |
| | |
| | | |
Change-Id: Ibb3dda05772b2e89d7b2646689944d309cb1f74e
Signed-off-by: Colin Cross <ccross@android.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
lvl trigger irqs
Change-Id: Ie378600668500dcffeaaddeaba3628e5c2141aa4
Signed-off-by: Dima Zavin <dima@android.com>
|
| | |
| | |
| | |
| | |
| | |
| | | |
If the gpio did not exist it would crash in gpiolib.
Signed-off-by: Arve Hjønnevåg <arve@android.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
to driver
Signed-off-by: Rebecca Schultz Zavin <rebecca@android.com>
Signed-off-by: Arve Hjønnevåg <arve@android.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Send both fingers using the new multitouch protocol in addition to
the old single finger event and second finger ABS_HAT* hack.
The new protocol does not specify how to report up events. To make
sure the user-space frameworks can generate up events, we send at
least one event where ABS_MT_TOUCH_MAJOR is zero before we stop
sending events for a finger.
Signed-off-by: Arve Hjønnevåg <arve@android.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Arve Hjønnevåg <arve@android.com>
|