Re: [PATCH 0/4] Touchscreen performance related fixes

On Monday 03 November 2014 11:39 PM, Richard Cochran wrote: > On Mon, Oct 27, 2014 at 04:38:27PM +0530, Vignesh R wrote: >> This series of patches fix TSC defects related to lag in touchscreen >> performance and cursor jump at touch release. The lag was result of >> udelay in TSC interrupt handle

Re: [PATCH 02/15] GPIO: port LoCoMo gpio support from old driver

On Thu, Nov 06, 2014 at 01:33:24AM +0400, Dmitry Eremin-Solenikov wrote: > 2014-11-03 16:43 GMT+03:00 Linus Walleij : > > Yes that's the point: if you use regmap mmio you get the RMW-locking > > for free, with the regmap implementation. > Just to be more concrete. Currently locomo_gpio_ack_irq()

Problems with Roccat Ryos in 3.16 & 3.17

Dear kernel input developers, I noticed suddenly that I can't use my Roccat Ryos PRO MK on my desktop, I mean nothing works. I notice that the problem is with USB3, there is no problem with USB2. Ryos uses 2x usb2 not usb3. I have been using 3.16.4 and I tired out 3.17.2.. on chakraOS but I

Re: About Dell Inspiron 3442 touchpad

On Wed, Nov 5, 2014 at 3:09 PM, Luiz Carlos Ramos wrote: > Hi, Benjamin. > > I'm just using vanilla 3.16.3, no patches, with .config built from the > one from Slackware stable (kernel 3.10.17). Anyway, I'll try to upgrade > it to the lastest 3.16. > I pulled 3.16.3 from linux-stable and tested wi

Re: About Dell Inspiron 3442 touchpad

Hi, Benjamin. I'm just using vanilla 3.16.3, no patches, with .config built from the one from Slackware stable (kernel 3.10.17). Anyway, I'll try to upgrade it to the lastest 3.16. As soon as I have something to inform, I'll keep you informed. Let me ask you one thing. What exactly is the "g" nu

Re: [PATCH 02/15] GPIO: port LoCoMo gpio support from old driver

2014-11-03 16:43 GMT+03:00 Linus Walleij : > On Fri, Oct 31, 2014 at 10:39 AM, Dmitry Eremin-Solenikov > wrote: >> 2014-10-31 10:48 GMT+03:00 Linus Walleij : >>> On Tue, Oct 28, 2014 at 1:01 AM, Dmitry Eremin-Solenikov >>> wrote: >>> Add gpiolib driver for gpio pins placed on the LoCoMo GA.

Re: [PATCH 01/15] mfd: add new driver for Sharp LoCoMo

On 11/05/2014 09:32 PM, Lars-Peter Clausen wrote: If it is a generic DAC it should go into drivers/iio/, this will allow code sharing and code re-usability. Given the simplicity of the DAC there might even be other existing drivers that can be used to control it. I just had a quick look and I t

Re: [PATCH 01/15] mfd: add new driver for Sharp LoCoMo

On 11/05/2014 09:02 PM, Dmitry Eremin-Solenikov wrote: 2014-11-03 16:41 GMT+03:00 Linus Walleij : On Fri, Oct 31, 2014 at 10:54 AM, Dmitry Eremin-Solenikov wrote: 2014-10-31 10:42 GMT+03:00 Linus Walleij : It seems some DAC handling is part of the MFD driver, and we recently discussed that

Re: [PATCH 1/1] x86: Surface Pro 3 Type Cover 3

On Mon, 3 Nov 2014, Alan Wu wrote: > Surface Pro 3 Type Cover that works with Ubuntu (and possibly Arch) from this > thread. Both trackpad and keyboard work after compiling my own kernel. > http://ubuntuforums.org/showthread.php?t=2231207&page=2&s=44910e0c56047e4f93dfd9fea58121ef > > Also includ

Re: [PATCH 01/15] mfd: add new driver for Sharp LoCoMo

On Thu, Nov 06, 2014 at 12:02:49AM +0400, Dmitry Eremin-Solenikov wrote: > 2014-11-03 16:41 GMT+03:00 Linus Walleij : > > The point is still the same: no unrelated code in drivers/mfd, > > then either use IIO DAC as a middle layer or sink the DAC handling > > into respective subdriver, i.e. push i

Re: [PATCH 01/15] mfd: add new driver for Sharp LoCoMo

2014-11-03 16:41 GMT+03:00 Linus Walleij : > On Fri, Oct 31, 2014 at 10:54 AM, Dmitry Eremin-Solenikov > wrote: >> 2014-10-31 10:42 GMT+03:00 Linus Walleij : > >>> It seems some DAC handling is part of the MFD driver, and we recently >>> discussed that MFD should not be doing misc stuff but mainly

Re: [PATCH 2/3] input: touchscreen: of: Register multitouch axes

On Wed, Nov 05, 2014 at 04:07:49PM +0100, Maxime Ripard wrote: > So far, the DT parsing code was only setting up the regular input axes, > completely ignoring their multitouch counter parts. > > Fill them with the same parameters than the regular axes. > > Signed-off-by: Maxime Ripard > --- > d

Re: Aorus X3+ touchpad not working

Hi Maximilien, [Adding Hans in CC, I am pretty sure he might be helpful] [side note: I hate those bug reports when there is all the information but the one we need] <-- Maximilien, do not take this personally, I know you have been asked to report it that way. So, I think we need to have a look a

Re: About Dell Inspiron 3442 touchpad

Hi Luiz, On Wed, Nov 5, 2014 at 3:09 AM, Luiz Carlos Ramos wrote: > Hi, Benjamin, > > Thanks again! > > Here it is an excerpt from $(udevadm info --export-db), I think the > relevant one: > > P: > /devices/pci:00/INT33C3:00/i2c-1/i2c-DLL0652:00/0018:06CB:2985.0005 > E: > DEVPATH=/devices/pci0

[PATCH 2/3] input: touchscreen: of: Register multitouch axes

So far, the DT parsing code was only setting up the regular input axes, completely ignoring their multitouch counter parts. Fill them with the same parameters than the regular axes. Signed-off-by: Maxime Ripard --- drivers/input/touchscreen/of_touchscreen.c | 12 +--- 1 file changed, 9

[PATCH 1/3] input: touchscreen: of: Use input_set_abs_params

Drivers are still required to call input_set_abs_params for their axes, as if they only use the touchscreen_parse_of_params function, the axis bit in absbit won't be set. Switch to using input_set_abs_params to fully setup each and every available axis so that drivers will be able to solely use th

[PATCH 0/3] input: ft5x06: Fix userspace reported maximum value

Hi, The current ft5x06 reports to the user-space that its maximum coordinates are, on both X and Y, way higher than what could be actually usable on the screen (in my case, 5759x1151 instead of 480x800). This causes trouble on some userspace stacks that then try to re-scale these coordinates back

[PATCH 3/3] input: ft5x06: Allow to set the maximum axes value through the DT

Currently the driver relies on some obscure and undocumented register to set the maximum axis value. The reported value is way too high to be meaningful, which confuses some userspace tools like QT's evdevtouch plugin which try to scale the reported events to the maximum values. Use the values fr

Re: [PATCH 1/1] hid-saitek: Quirk for Saitek R.A.T.7 works with R.A.T.9 too

On Tue, 4 Nov 2014, Ville Aakko wrote: > From: Ville Aakko > > I have tested HID quirk for Saitek R.A.T.7 with my R.A.T. 9. It works > fine for me. Attached patch makes the necessary changes to use the quirk > on the R.A.T.9 too, and necessary Kconfig changes too. > > I have stylized the Kcon

Re: [PATCH 0/4] Touchscreen performance related fixes

On Tuesday 04 November 2014 06:07 PM, Sebastian Andrzej Siewior wrote: > On 11/04/2014 12:44 PM, Vignesh R wrote: > >> I ran following commands >> $ evtest /dev/input/touchscreen0 & >> (with heavy item on touchscreen) >> and >> $ cat /sys/bus/iio/devices/iio\:device0/scan_elements/in_voltage4_e

Aorus X3+ touchpad not working

Dear Maintainers, This is my first report. Please bear with me... (and let me take the opportunity to thank all of you for your amazing work). I've been asked to give a direct link to my e-mail so here it is: maximilien.leves...@gmail.com [1.] One line summary of the problem: Aorus X3+ touchpad n

Re: About Dell Inspiron 3442 touchpad

Hi, Benjamin, Thanks again! Here it is an excerpt from $(udevadm info --export-db), I think the relevant one: P: /devices/pci:00/INT33C3:00/i2c-1/i2c-DLL0652:00/0018:06CB:2985.0005 E: DEVPATH=/devices/pci:00/INT33C3:00/i2c-1/i2c-DLL0652:00/0018:06CB:2985.0005 E: HID_ID=0018:06CB: