On Wed, 25 Feb 2015, Benjamin Tissoires wrote:
So here is the v2 of the patch set to support the Bamboo PAD.
It has been tested by Josep (thanks!) on the wired version and I
developped it on the wireless version. I guess it should be good
to go if the reviews goes well.
Cheers,
Benjamin
On Fri, 20 Feb 2015, Ping Cheng wrote:
Hi Jiri,
This set is based on your for-3.20/upstream-fixes branch.
If pen comes in proximity while touch is down, we force touch up
before sending pen events. This idea has been implemented for
Tablet PCs. But other tablets that support both pen and
On Feb 25 2015 or thereabouts, Benjamin Tissoires wrote:
On Feb 25 2015 or thereabouts, Nikolai Kondrashov wrote:
On 02/25/2015 02:05 AM, Benjamin Tissoires wrote:
The Huion tablets show 3 interfaces. Only the first and the third
are currently used.
Also remove HID_QUIRK_MULTI_INPUT for
The stylus of this device works just fine out of the box.
The touch is seen by default as a mouse with relative events and some
gestures.
The wireless and the wired version have slightly different firmwares, but
the debug mode 2 on the feature 2 is common to the 2 devices. In this mode,
all the
Hi Maxime,
On Tue, Feb 24, 2015 at 05:55:08PM +0100, Maxime Ripard wrote:
Hi Markus,
On Mon, Feb 23, 2015 at 10:49:36PM +0100, Markus Pargmann wrote:
Hi,
On Thu, Nov 13, 2014 at 03:06:54PM +0100, Maxime Ripard wrote:
Hi,
The current ft5x06 reports to the user-space that its
udev is 208-r4 - most likely not having the patch. Thanks for the
info, will see if I can bump the version.
On Thu, Feb 26, 2015 at 3:02 PM, Bastien Nocera had...@hadess.net wrote:
On Thu, 2015-02-26 at 14:05 +0100, Stefan Sauer wrote:
hi,
on my beaglebone-black I get these lines during
On Thu, 2015-02-26 at 14:05 +0100, Stefan Sauer wrote:
hi,
on my beaglebone-black I get these lines during bootup
[ 71.745951] udevd[105]: worker [113]
/devices/ocp.2/4819c000.i2c/i2c-2/2-001d/input/input2/event1 timeout;
kill it
[ 71.771991] udevd[105]: seq 1243
Hi,
On Mon, Feb 02, 2015 at 09:51:34AM -0800, Dmitry Torokhov wrote:
On Mon, Feb 02, 2015 at 05:05:39PM +0100, Markus Pargmann wrote:
Hi,
On Fri, Jan 30, 2015 at 10:57:21AM -0800, Dmitry Torokhov wrote:
On Thu, Jan 29, 2015 at 07:56:40PM +0530, Varka Bhadram wrote:
Hi,
On
Hi Wolfram,
On Monday 26 January 2015 13:09:47 Wolfram Sang wrote:
If you drop adi,adxl346, checkpatch will start complaining if it
encounters
it in a .dts.
Boah, this is annoying. That means we need an 346 entry even if it is
not different from 345 (which is fine by me).
hi,
on my beaglebone-black I get these lines during bootup
[ 71.745951] udevd[105]: worker [113]
/devices/ocp.2/4819c000.i2c/i2c-2/2-001d/input/input2/event1 timeout;
kill it
[ 71.771991] udevd[105]: seq 1243
'/devices/ocp.2/4819c000.i2c/i2c-2/2-001d/input/input2/event1' killed
[
Some Huion tablets present 2 HID Pen interfaces. Only one is used, so
we can drop the unused one.
Signed-off-by: Benjamin Tissoires benjamin.tissoi...@redhat.com
---
New in v2
drivers/hid/hid-uclogic.c | 20
1 file changed, 20 insertions(+)
diff --git
NO_EMPTY_INPUT is useful when MULTI_INPUT is set. It prevents to create
empty input nodes that user space does not know what to do with.
It does not seem to be required at the moment, this is just a preventive
patch. This check is only made during the plug of the device, so it does
not hurt to
These 2 are left over from the USB dependency cleaning, so there is
no need to keep them.
Signed-off-by: Benjamin Tissoires benjamin.tissoi...@redhat.com
---
drivers/hid/hid-multitouch.c | 1 -
drivers/hid/hid-steelseries.c | 1 -
2 files changed, 2 deletions(-)
diff --git
From: Nikolai Kondrashov nikolai.kondras...@redhat.com
Merge the hid-huion driver into hid-uclogic as all the devices supported
by hid-huion are in fact UC-Logic devices.
Signed-off-by: Nikolai Kondrashov nikolai.kondras...@redhat.com
Signed-off-by: Benjamin Tissoires
Based on a patch from: Nikolai Kondrashov nikolai.kondras...@redhat.com
Most of the tablets handled by hid-uclogic already use MULTI_INPUT.
For the ones which are not quirked in usbhid/hidquirks, they have a
custom report descriptor which contains only one report per HID
interface. For those
Address issue reported by kbuild test robot fengguang...@intel.com
sparse warnings: (new ones prefixed by )
drivers/hid/hid-sensor-hub.c:223:39: sparse: incorrect type in argument 3
(different base types)
drivers/hid/hid-sensor-hub.c:223:39:expected signed int [signed]
[usertype]
Hi,
this is the v2 of the merge of Huion and UcLogic.
I removed the previous 3/4 as mentioned during the review and added
3 more.
Note that 6/6 could have been squashed in 2/6, but I kept it separate
to keep the first 2 reviewed.
Cheers,
Benjamin
Benjamin Tissoires (6):
HID: uclogic: Set
Hi Vince,
On Feb 26 2015 or thereabouts, Vince Herried wrote:
I'm overwhelmed by these updates My understanding of the code is not that
good.
Currently i have a version of the code that gives two interfaces from my
Huion h610. I have gotten the buttons to work using xsetwacom. I dont
On Mon, 23 Feb 2015, Krzysztof Kozlowski wrote:
Change the ownership of power_supply structure from each driver
implementing the class to the power supply core.
The patch changes power_supply_register() function thus all drivers
implementing power supply class are adjusted.
Each driver
On czw, 2015-02-26 at 01:45 +0100, Sebastian Reichel wrote:
Hi,
On Mon, Feb 23, 2015 at 12:47:32PM +0100, Krzysztof Kozlowski wrote:
Change the ownership of power_supply structure from each driver
implementing the class to the power supply core.
(...)
I would like to merge this via
Hi,
Any news/thought regarding this patch ?
Thanks,
Cheers,
2015-02-15 13:44 GMT+01:00 Thomas Sanchez thomas.san...@gmail.com:
This commit introduces a new driver for Foxconn CNTouch trackpad that
can be found on LDLC's laptop IRIS family. The driver has been inspired
from usbmouse.c.
The PID driver (usbhid/hid-pidff.c) does not set the effect ID when
uploading an effect. The result is that the initial upload works but
subsequent uploads to modify effect parameters are all directed at the
last-created effect.
The targeted effect ID must be passed back to the device when effect
On Wed, 2015-02-25 at 22:18 -0800, Darren Hart wrote:
On Fri, Feb 20, 2015 at 03:44:10PM +0100, Bastien Nocera wrote:
Rather than checking on each suspend and resume whether the laptop
has an adaptive keyboard, check when the driver is initialised.
Bastien, am I awaiting another version of
Thanks, tested it and confirming it works them same.
On Thu, Feb 26, 2015 at 1:11 PM, Stefan Sauer enso...@google.com wrote:
Thanks, tested it and confirming it works them same.
On Thu, Feb 26, 2015 at 2:48 AM, Dmitry Torokhov dmitry.torok...@gmail.com
wrote:
This simplifies error handling
On Thu, Feb 26, 2015 at 6:18 PM, Florian Echtler f...@butterbrot.org wrote:
Hello everyone,
I've recently bought an Acer Aspire Switch 11 convertible
tablet/notebook hybrid device. Ubuntu 14.04.2 with kernel 3.16 runs
almost perfectly, with one notable exception: on the keyboard dock, only
On Thu, Feb 26, 2015 at 8:28 AM, Benjamin Tissoires
benjamin.tissoi...@redhat.com wrote:
The stylus of this device works just fine out of the box.
The touch is seen by default as a mouse with relative events and some
gestures.
The wireless and the wired version have slightly different
Hi,
Changes since the last version:
- I added a commit which clamps the reported coordinates to valid values, even
if the values reported by the touchpad are wrong/misinterpreted.
- PSMOUSE_CMD_SETSCALE11 is now encapsulated in a member function of struct
psmouse, like the other configuration
Apparently, the threshold for large contact area seems to be rather low on
some devices, causing the touchpad to frequently freeze during normal
usage. Because we do now know how we are supposed to use the value in
question, this commit just drops the related code completely.
Signed-off-by:
Hello everyone,
I've recently bought an Acer Aspire Switch 11 convertible
tablet/notebook hybrid device. Ubuntu 14.04.2 with kernel 3.16 runs
almost perfectly, with one notable exception: on the keyboard dock, only
the touchpad works, not the keyboard itself. I've done a bit of digging
in the
On Thu, 26 Feb 2015, Benjamin Tissoires wrote:
These 2 are left over from the USB dependency cleaning, so there is
no need to keep them.
Signed-off-by: Benjamin Tissoires benjamin.tissoi...@redhat.com
I have fixed the filename in the subject :) and applied. Thanks.
---
The size has in most cases already been fetched from the touchpad, the
hardcoded values should have been removed.
Signed-off-by: Mathias Gottschlag mgottsch...@gmail.com
---
drivers/input/mouse/focaltech.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git
These PS/2 commands make some touchpads stop responding, so this commit
adds some dummy functions to replace the generic implementation. Because
scale changes were not encapsulated in a method of struct psmouse yet, this
commit adds a method set_scale to psmouse.
Signed-off-by: Mathias Gottschlag
We don't know whether x_max or y_max really hold the maximum possible
coordinates, and we don't know for sure whether we correctly interpret the
coordinates sent by the touchpad, so we clamp the reported values to
prevent confusion in userspace code.
Signed-off-by: Mathias Gottschlag
Hi Dmitry,
Thanks. I'll go through his patch and make the appropriate changes to
our driver.
Jon
On 15-02-24 03:18 PM, Dmitry Torokhov wrote:
Jonathan,
On Wed, Feb 11, 2015 at 10:45:34AM -0800, Jonathan Richardson wrote:
Pinging maintainers... Am I ok to go ahead with the current
34 matches
Mail list logo
