| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
Update the touch screen driver for the MT protocol.
Remove reporting all the data. Only report the finger in
the packet
Change-Id: I67d09660b007d1689af5993d627bed00b1b7b3d2
Signed-off-by: Dan Murphy <dmurphy@ti.com>
|
|
|
|
|
|
|
|
|
| |
Update the reporting of the touch points to use the multi touch
api's.
Also report BTN_TCH to report a down condition
Change-Id: I35831c2f12bfe43d7142da73f3ef570209fd30eb
Signed-off-by: Dan Murphy <dmurphy@ti.com>
|
|
|
|
|
|
|
|
|
|
| |
Add the qtouch driver for the mxt224 for the
tablet 2 device.
This is ported from k35.
Change-Id: I4b08f3c1d3964b712cdca1d14ddf994ebef7b8ad
Signed-off-by: Dan Murphy <dmurphy@ti.com>
|
|
|
|
|
|
|
|
|
| |
Update the touch screen driver to the k35 version.
This include adding a controller number and
linux friendly input names.
Signed-off-by: Dan Murphy <dmurphy@ti.com>
|
|
|
|
|
|
| |
Port K35 synaptics touch screen driver from OMAP k35 kernel.
Signed-off-by: Dan Murphy <dmurphy@ti.com>
|
|
|
|
|
|
|
| |
Port BMP085 k39 driver to k3.0
Change-Id: If8173267a795523fb219caa40732ab379a903f20
Signed-off-by: Arthur Philpott <arthur.philpott@ti.com>
|
|
|
|
|
|
|
|
|
| |
Add a suspend resume handler that will allow a
function pointer to be defined on board files to set or
clear a pad wakup bit.
Change-Id: I2264bc8d48f02f69c24fed528759c13fdbb12c60
Signed-off-by: Axel Haslam <axelhaslam@ti.com>
|
|\ |
|
| |\
| | |
| | |
| | | |
Change-Id: I05959ed26f71cf9197df59291e8e13f254b2115c
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
commit a455e2985f57e2a71566bb8850094af38b2c932d upstream.
The driver's timer must be set up before enabling IRQ handler, otherwise
bad things may happen.
Reported-and-tested-by: Fengguang Wu <fengguang.wu@intel.com>
Signed-off-by: Peter Popovec <popovec@fei.tuke.sk>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
commit ad68652412276f68ad4fe3e1ecf5ee6880876783 upstream.
Some MSI laptop BIOSes are broken - INT 15h code uses port 92h to enable A20
line but resume code assumes that KBC was used.
The laptop will not resume from S3 otherwise but powers off after a while
and then powers on again stuck with a blank screen.
Fix it by enabling A20 using KBC in i8042_platform_init for x86.
Fixes https://bugzilla.kernel.org/show_bug.cgi?id=12878
Signed-off-by: Ondrej Zary <linux@rainbow-software.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Rafael J. Wysocki <rjw@sisk.pl>
Link: http://lkml.kernel.org/r/201212112218.06551.linux@rainbow-software.org
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
commit 52965cc012f7a3cf35f06485ec275ebf3b3fddae upstream.
Some bcm5974 trackpads have a physical button beneath the physical surface.
This patch sets the property bit so user space applications can detect the
trackpad type and act accordingly.
Signed-off-by: Jussi Pakkanen <jussi.pakkanen@canonical.com>
Reviewed-by: Henrik Rydberg <rydberg@euromail.se>
Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
Cc: maximilian attems <max@stro.at>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
| |\ \
| | |/
| | |
| | |
| | | |
Change-Id: I9685feb9277b450da10d78a455b3c0674d6cfe18
Signed-off-by: Todd Poynor <toddpoynor@google.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
commit 8669cf6793bb38307a30fb6b9565ddc8840ebd3f upstream.
On Toshiba Satellite C850D, the touchpad and the keyboard might randomly
not work at boot. Preventing MUX mode activation solves this issue.
Signed-off-by: Anisse Astier <anisse@astier.eu>
Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
commit 7b125b94ca16b7e618c6241cb02c4c8060cea5e3 upstream.
They all define their chassis type as "Other" and therefore are not
categorized as "laptops" by the driver, which tries to perform AUX IRQ
delivery test which fails and causes touchpad not working.
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=42620
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
commit 6dc463511d4a690f01a9248df3b384db717e0b1c upstream.
Bamboo One's with ID of 0x6a and 0x6b were added with correct
indication of 1024 pressure levels but the Graphire packet routine
was only looking at 9 bits. Increased to 10 bits.
This bug caused these devices to roll over to zero pressure at half
way mark.
The other devices using this routine only support 256 or 512 range
and look to fix unused bits at zero.
Signed-off-by: Chris Bagwell <chris@cnpbagwell.com>
Reported-by: Tushant Mirchandani <tushantin@gmail.com>
Reviewed-by: Ping Cheng <pingc@wacom.com>
Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
commit e76b8ee25e034ab601b525abb95cea14aa167ed3 upstream.
I couldn't find the vendor ID in any of the online databases, but this
mat has a Pump It Up logo on the top side of the controller compartment,
and a disclaimer stating that Andamiro will not be liable on the bottom.
Signed-off-by: Yuri Khan <yurivkhan@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
| |\ \
| | |/
| | |
| | |
| | | |
Change-Id: Iee820738e53627f5d0447a87ceff34443aa72786
Signed-off-by: Todd Poynor <toddpoynor@google.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Set max x/y to size - 1
Change-Id: I5bf99bfb45d5ae170049cc574694882e62194e60
Signed-off-by: Dima Zavin <dima@android.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit 4ff08e36fda8c309c5ed320c7cd2546cb88f752c
Get rid of the debugging for the release.
Signed-off-by: JP Abgrall <jpa@google.com>
Change-Id: I4dd4cf62f2c574db80c70210771a9bed11dedcab
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Change-Id: I336ba4d61beba035ecc237ccc68b012e48702a87
Signed-off-by: Todd Poynor <toddpoynor@google.com>
|
| |\ \ \
| | |/ /
| |/| /
| | |/
| | | |
Change-Id: I86dcae86b15baab2cb26e2c53faafb57c606a2b5
Signed-off-by: Todd Poynor <toddpoynor@google.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
commit 99c90ab31fad855b9da9dee3a5aa6c27f263e9d6 upstream.
ALPS touchpad detection fails if some buttons of ALPS are pressed.
The reason is that the "E6" query response byte is different from
what is expected.
This was tested on a Toshiba Portege R500.
Signed-off-by: Akio Idehara <zbe64533@gmail.com>
Tested-by: Seth Forshee <seth.forshee@canonical.com>
Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
commit 8521478f67e95ada4e87970c7b41e504c724b2cf upstream.
Synaptics touchpads on several Dell laptops, particularly Vostro V13
systems, may not respond properly to PS/2 commands and queries immediately
after resuming from suspend to RAM. This leads to unresponsive touchpad
after suspend/resume cycle.
Adding a 1-second delay after resetting the device allows touchpad to
finish initializing (calibrating?) and start reacting properly.
Reported-by: Daniel Manrique <daniel.manrique@canonical.com>
Tested-by: Daniel Manrique <daniel.manrique@canonical.com>
Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Some people are complaining that after a resume, they are not getting
touch screen events.
This change only logs 1 event after each enable.
Bug: 6258051
Change-Id: Iad508befde6fafec1b454aa334f8d47a3750a3eb
Signed-off-by: JP Abgrall <jpa@google.com>
|
|\ \ \
| |/ /
| | |
| | |
| | | |
Conflicts:
drivers/misc/Makefile
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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>
|
| | |
| | |
| | |
| | |
| | | |
Change-Id: I3c930f3337ae5c3953a70777d15d95f91945b52c
Signed-off-by: Dima Zavin <dima@android.com>
|
| | |
| | |
| | |
| | |
| | | |
Change-Id: Ic55c18333e960d3848dfd7c1ea389ef6909cfbda
Signed-off-by: tyoony <tyoony.yoon@samsung.com>
|
|\ \ \
| |/ / |
|
| | |
| | |
| | |
| | |
| | | |
Change-Id: I29ccb32e795c5c3e4c51c3d3a209f5b55dfd7d94
Signed-off-by: Dima Zavin <dima@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>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add usleep_range to ensure TSP IC's sleep/wake-up time
Change-Id: Ibf2f14fea9e13d3d90652adef92e33c919c5d302
Signed-off-by: tyoony <tyoony.yoon@samsung.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>
|
| | |
| | |
| | |
| | |
| | |
| | | |
convert to 0 based slot id for reporting.
Change-Id: Ieb2214b7528bbb967a33f4c001e05b9089cb626c
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The board file may ask the driver to load a different firmware
based on the board revision.
Change-Id: I65f1811f36952158a45aeeced53e935c1ee74d3f
Signed-off-by: Dima Zavin <dima@android.com>
|
| | |
| | |
| | |
| | |
| | | |
Change-Id: I2aefa4c2a2b33fbc6ac20b2d9237db45690d9e87
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>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The new firmware image format now includes a header
at the beginning of the data that includes the firmware
version information. So, we no longer have to modify
the driver when we update firmware, unless there is
an API change.
Change-Id: Ib573078144fad5fa99b6ded6d63e43d27fe0623d
Signed-off-by: Dima Zavin <dima@android.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Update some delays to meet timing requirements.
- Verify after every word instead of waiting till the whole image
is written. If verify fails, retry the write several times.
- Upon a failure on retries of rewriting the word, retry firmware reflash
from the beginning.
- If we run out of retries, do not make open()
block anymore, just return an error.
- Update write/erase timings.
- Increase open timeout, up to 90 secs.
Change-Id: I072a2e47e3f8266d4233afd8a34cfef08ba1cf55
Signed-off-by: Dima Zavin <dima@android.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
While flashing the new firmware, the touch IC is booted into a
separate mode and the firmware is bit banged over the
SCL/SDA/nINT(resetb) pins. Some operations are very timing
sensitive, and we just cannot guarantee that we can meet them.
It looks like, with the current delays, we can keep irqs off
for around 150uS-200uS.
This is unfortunate, but it is only done during firmware reflash
on boot.
Change-Id: If74de1931f5fb0ed0f8e5e2e1e636d515e1e77a5
Signed-off-by: Dima Zavin <dima@android.com>
|