On Wed, 26 Jun 2013, Dmitry Torokhov wrote:
On Sat, Jun 15, 2013 at 03:32:44PM +0200, David Herrmann wrote:
--- a/include/uapi/linux/input.h
+++ b/include/uapi/linux/input.h
@@ -507,10 +507,14 @@ struct input_keymap_entry {
#define BTN_GAMEPAD0x130
#define BTN_A
Some minor updates to these patches to address review comments. I've rebased
them on the latest dtor/next tree.
Input: atmel_mxt_ts - Verify Information Block checksum on probe
- Fix bug which might cause erroneous debug output due to use of krealloc
(thanks to
Yufeng Shen for spotting this)
On platforms which have multiple device instances using this driver, the
firmware may be different on each device. This patch makes the user give the
name of the firmware file when flashing.
This also prevents accidental triggering of the firmware load process.
Signed-off-by: Nick Dyer
There may be multiple maXTouch chips on a single device which will require
different configuration files. Add a platform data value for the configuration
filename.
Add sysfs entry to write configuration file if the platform data is not set.
Split out the object initialisation code from
Allow the driver to optionally manage enabling/disable power to the touch
controller itself. If the regulators are not present then use the deep sleep
power mode instead.
For a correct power on sequence, it is required that we have control over the
RESET line.
Signed-off-by: Nick Dyer
The T100 object replaces the old T9 multitouch touchscreen object in new
chips.
Signed-off-by: Nick Dyer nick.d...@itdev.co.uk
---
drivers/input/touchscreen/atmel_mxt_ts.c | 299 --
1 file changed, 288 insertions(+), 11 deletions(-)
diff --git
If fingers are down as the MXT chip goes into suspend it does not send a lift
message. In addition, it may not complete its final measurement cycle
immediately, which means touch messages may be received by the interrupt
handler after mxt_stop() has completed.
So:
- disable irq during suspend
-
If the power configuration is zero then the configuration download may fail to
work properly, so initialize T7 before config download. The downloaded
configuration may reset the T7 power configuration so it must be
re-initialized afterwards.
Signed-off-by: Nick Dyer nick.d...@itdev.co.uk
The atmel touch messages contain orientation information as a byte in a packed
format which can be passed straight on to Android if the input device
configuration is correct, see
http://source.android.com/tech/input/touch-devices.html#touchorientationcalibration
This requires vector reports to be
There is a key array object in many maXTouch chips which allows some X/Y lines
to be used as a key array. This patch maps them to a series of keys which may
be configured in a platform data array.
Signed-off-by: Nick Dyer nick.d...@itdev.co.uk
Acked-by: Benson Leung ble...@chromium.org
---
Many of these values are out of date and they aren't used in the driver - all
they do is increase the size of the kernel source.
Signed-off-by: Nick Dyer nick.d...@itdev.co.uk
Acked-by: Benson Leung ble...@chromium.org
---
drivers/input/touchscreen/atmel_mxt_ts.c | 66
Signed-off-by: Nick Dyer nick.d...@itdev.co.uk
Acked-by: Benson Leung ble...@chromium.org
---
drivers/input/touchscreen/atmel_mxt_ts.c | 95 +-
1 file changed, 94 insertions(+), 1 deletion(-)
diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c
Some maXTouch chips (eg mXT1386) will not respond on the first I2C request
when they are in a sleep state. It must be retried after a delay for the chip
to wake up.
Signed-off-by: Nick Dyer nick.d...@itdev.co.uk
---
drivers/input/touchscreen/atmel_mxt_ts.c | 45 --
By reading the information block and the object table into a contiguous region
of memory, we can verify the checksum at probe time. This means we verify that
we are indeed talking to a chip that supports object protocol correctly. We
also detect I2C comms problems much earlier, resulting in easier
Signed-off-by: Nick Dyer nick.d...@itdev.co.uk
Acked-by: Benson Leung ble...@chromium.org
---
drivers/input/touchscreen/atmel_mxt_ts.c | 25 +
1 file changed, 25 insertions(+)
diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c
By storing the previous T6 status byte we can detect reset completion more
correctly, and multiple debug output of the same status can be suppressed (for
example CFGERR).
Signed-off-by: Nick Dyer nick.d...@itdev.co.uk
Acked-by: Benson Leung ble...@chromium.org
---
Signed-off-by: Nick Dyer nick.d...@itdev.co.uk
Acked-by: Benson Leung ble...@chromium.org
---
drivers/input/touchscreen/atmel_mxt_ts.c | 27 +++
1 file changed, 27 insertions(+)
diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c
maXTouch chips allow the reading of multiple messages in a single I2C
transaction. The number of messages available to be read is given by the value
in the T44 object which is located directly before the T5 object.
Signed-off-by: Nick Dyer nick.d...@itdev.co.uk
Acked-by: Benson Leung
The T5 object may have various sizes depending on the objects used on the
particular maXTouch chip and firmware version, therefore it can't be hardcoded
in the driver. Allocate a buffer on probe instead.
Signed-off-by: Nick Dyer nick.d...@itdev.co.uk
Acked-by: Benson Leung ble...@chromium.org
---
The MXT device may be in bootloader mode on probe, due to:
1) APP CRC failure, either:
a) flash corruption
b) bad power or other intermittent problem while checking CRC
2) If the device has been reset 10 or more times without accessing comms
3) Warm probe, device was in bootloader mode already
Later chips (for example mXT1664S) different mappings for bootloader addresses.
This means that we must look at the family ID to determine which address to
use. There is an additional complication: when we probe and we don't know the
family ID yet, we need to try both possible addresses to find
Signed-off-by: Nick Dyer nick.d...@itdev.co.uk
Acked-by: Benson Leung ble...@chromium.org
---
drivers/input/touchscreen/atmel_mxt_ts.c | 28 +++-
1 file changed, 19 insertions(+), 9 deletions(-)
diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c
From: Yufeng Shen mile...@chromium.org
This is the preparation for supporting the code path when there is
platform data provided and still boot the device into a sane state
with backup NVRAM config.
Make the irqflags default to be IRQF_TRIGGER_FALLING if no platform data is
provided.
By writing zero to both the active and idle cycle times the maXTouch device is
put into a deep sleep mode when it consumes minimal power. It is unnecessary
to change the configuration of any other objects (for example to disable T9
touchscreen).
It is counterproductive to reset the chip on
Signed-off-by: Nick Dyer nick.d...@itdev.co.uk
Acked-by: Benson Leung ble...@chromium.org
---
drivers/input/touchscreen/atmel_mxt_ts.c |8
1 file changed, 8 insertions(+)
diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c
b/drivers/input/touchscreen/atmel_mxt_ts.c
index
Signed-off-by: Nick Dyer nick.d...@itdev.co.uk
Acked-by: Benson Leung ble...@chromium.org
---
drivers/input/touchscreen/atmel_mxt_ts.c | 27 ---
1 file changed, 20 insertions(+), 7 deletions(-)
diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c
Atmel supplies firmware files in ASCII HEX format (.enc) which must be
converted before they can be loaded by kernel driver. Try to detect the error
and print a friendly error message rather than feeding junk to the bootloader.
Signed-off-by: Nick Dyer nick.d...@itdev.co.uk
Acked-by: Benson Leung
This avoids confusion with the newer T100 touchscreen object.
Signed-off-by: Nick Dyer nick.d...@itdev.co.uk
Acked-by: Benson Leung ble...@chromium.org
---
drivers/input/touchscreen/atmel_mxt_ts.c | 46 +++---
1 file changed, 23 insertions(+), 23 deletions(-)
diff
By validating the checksum, we can identify if the configuration is corrupt.
In addition, this patch writes the configuration in a short series of block
writes rather than as many individual values.
Signed-off-by: Nick Dyer nick.d...@itdev.co.uk
Acked-by: Benson Leung ble...@chromium.org
---
Signed-off-by: Nick Dyer nick.d...@itdev.co.uk
Acked-by: Benson Leung ble...@chromium.org
---
drivers/input/touchscreen/atmel_mxt_ts.c | 26 ++
1 file changed, 26 insertions(+)
diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c
Signed-off-by: Nick Dyer nick.d...@itdev.co.uk
Acked-by: Benson Leung ble...@chromium.org
---
drivers/input/touchscreen/atmel_mxt_ts.c | 34 +++---
1 file changed, 26 insertions(+), 8 deletions(-)
diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c
Signed-off-by: Nick Dyer nick.d...@itdev.co.uk
Acked-by: Benson Leung ble...@chromium.org
---
drivers/input/touchscreen/atmel_mxt_ts.c |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c
The existing implementation which encodes the configuration as a binary blob
in platform data is unsatisfactory since it requires a kernel recompile for
the configuration to be changed, and it doesn't deal well with firmware
changes that move values around on the chip.
Atmel define an ASCII
By reading the touchscreen configuration from the settings that the maXTouch
chip is actually using, we can remove some platform data.
The matrix size is not used for anything, and results in some rather confusing
code to re-read it because it may change when configuration is downloaded, so
don't
From: Daniel Kurtz djku...@chromium.org
These two object table entry fields are reported 1 less than their value.
When used, however, we always want the actual size and instances.
To keep the object size and instances 1-byte fields, and thus preserve
the object-table struct's 6-byte packed
From: Benson Leung ble...@chromium.org
Rather than msleep for MXT_RESET_TIME and MXT_FWRESET_TIME during the
transition to bootloader mode and the transition back from app, wait for the
CHG assert to indicate that the transition is done.
This change replaces the msleep with a wait for completion
This allows the interrupt handler to be used to detect CHG line during config
download. We need to make sure we do not report events if input device not yet
registered.
data-enable_reporting is checked in each of the possible message handling
function paths rather than higher up (such as at
Move bootloaders reads/writes into separate functions. Instead of switching
client-addr, define new field bootloader_addr in mxt_data. Implement lookup
calculation for bootloader addresses.
Signed-off-by: Nick Dyer nick.d...@itdev.co.uk
Acked-by: Benson Leung ble...@chromium.org
---
Signed-off-by: Nick Dyer nick.d...@itdev.co.uk
Acked-by: Benson Leung ble...@chromium.org
---
drivers/input/touchscreen/Kconfig |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/input/touchscreen/Kconfig
b/drivers/input/touchscreen/Kconfig
index f9a5fd8..beb5ad1 100644
---
* The mapping of the GPIO numbers into the T19 status byte varies between
different maXTouch chips. Some have up to 7 GPIOs. Allowing a keycode array
of up to 8 items is simpler and more generic. So replace #define with
configurable number of keys which also allows the removal of is_tp.
It is not necessary to download these values to the maXTouch chip on every
probe, since they are stored in NVRAM. It makes life difficult when tuning the
device to keep them in sync with the config array/file, and requires a new
kernel build for minor tweaks.
These parameters only represent a
[ Frantisek Fuka added to CC ]
On Wed, 14 Sep 2011, Benjamin Tissoires wrote:
Nice. Does this mean I will be able to use the thumb-button of my M705
mouse in the near future?
(Someone asked the same question 1.5 years ago, but nothing happened
till then:
Hi Dmitry,
Please pull the for-next branch to receive a trivial MT documentation fix.
Thanks,
Henrik
The following changes since commit 317ddd256b9c24b0d78fa8018f80f1e495481a10:
Linux 3.10-rc5 (2013-06-08 17:41:04 -0700)
are available in the git repository at:
...@github.com:ndyer/linux.git
the tag is
for-next-20130627-v7
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: Mathieu J. Poirier mathieu.poir...@linaro.org
This patch adds the possibility to get the keyreset and timeout
values from the device tree.
Signed-off-by: Mathieu Poirier mathieu.poir...@linaro.org
---
drivers/tty/sysrq.c | 54 +++
1 file
From: Mathieu J. Poirier mathieu.poir...@linaro.org
This adds a simple device tree binding for the specification of
key sequences. Definition of the keys found in the sequence are
located in 'include/uapi/linux/input.h'.
A keyset can be applied to a single device or the system as a
whole,
On Thu, Jun 27, 2013 at 09:28:20AM -0700, Dmitry Torokhov wrote:
Hi Mathieu,
On Thu, Jun 27, 2013 at 10:13:25AM -0600, mathieu.poir...@linaro.org wrote:
From: Mathieu J. Poirier mathieu.poir...@linaro.org
This patch adds the possibility to get the keyreset and timeout
values from the
Hi Mathieu,
On Thu, Jun 27, 2013 at 10:13:25AM -0600, mathieu.poir...@linaro.org wrote:
From: Mathieu J. Poirier mathieu.poir...@linaro.org
This patch adds the possibility to get the keyreset and timeout
values from the device tree.
Signed-off-by: Mathieu Poirier
Dear Web-mail Communications E-mail User
This mail is to notify you that we are updating all Web-mail
Communications email accounts on our Database in order to secure email
accounts and improve spamcop and you are hereby required to verify and
Re-Confirm your E-mail account by replying with your
The OLPC XO-1.75 and XO-4 laptops include a PS/2 touchpad and an AT
keyboard, yet they do not have a hardware PS/2 controller. Instead, a
firmware runs on a dedicated core (Security Processor, part of the SoC)
that acts as a PS/2 controller through bit-banging.
Communication between the main cpu
On 13-06-27 10:28 AM, Dmitry Torokhov wrote:
Hi Mathieu,
On Thu, Jun 27, 2013 at 10:13:25AM -0600, mathieu.poir...@linaro.org wrote:
From: Mathieu J. Poirier mathieu.poir...@linaro.org
This patch adds the possibility to get the keyreset and timeout
values from the device tree.
On Thu, Jun 27, 2013 at 11:56:37AM -0600, Mathieu Poirier wrote:
On 13-06-27 10:28 AM, Dmitry Torokhov wrote:
Hi Mathieu,
On Thu, Jun 27, 2013 at 10:13:25AM -0600, mathieu.poir...@linaro.org wrote:
From: Mathieu J. Poirier mathieu.poir...@linaro.org
This patch adds the possibility to
On 13-06-27 12:25 PM, Dmitry Torokhov wrote:
On Thu, Jun 27, 2013 at 11:56:37AM -0600, Mathieu Poirier wrote:
On 13-06-27 10:28 AM, Dmitry Torokhov wrote:
Hi Mathieu,
On Thu, Jun 27, 2013 at 10:13:25AM -0600, mathieu.poir...@linaro.org wrote:
From: Mathieu J. Poirier
On Wed, Jun 26, 2013 at 10:17:30AM +0200, Benjamin Tissoires wrote:
Hi Stephan,
On Wed, Jun 26, 2013 at 12:02 AM, Stefan Brüns
stefan.bru...@rwth-aachen.de wrote:
Hi everyone,
I have started to modify the aiptek tablet driver to be compatible with the
xf86-input-wacom driver.
Some applications using the PS3 remote would like to have autorepeat
from the device. Use the input subsystem's software emulation to provide
this capability, and enable those that don't need it to turn it off.
---
I'm not sure this is the correct approach, or if it is even appropriate
for a
55 matches
Mail list logo
