Instead of having a single 'input_dev' device that will take either pen
or touch data depending on the type of the device, create seperate devices
devices for each. By splitting things like this, we can support devices
(e.g. the I2C "AES" sensors in some newer tablet PCs) that send both pen
and tou
A little bit of cleanup work for 'wacom_update_name' to make it easier on
the eyes. Creates a temporary 'name' variable on which we'll perform our
edits. Once the name is in its final form, it will be copied (with
appropriate suffix) to 'wacom_wac->name' and 'wacom_wac->pad_name'.
Signed-off-by: J
I've recently got my hands on a device which has an I2C sensor that sends
both pen and touch reports from a single interface. To userspace, it shows
up as a single input device which blends both the report types (e.g. it has
ABS_PRESSURE for the pen, and ABS_MT_POSITION_X for the touch). This patch
The USB devices that this driver has historically supported segregate the
pen and touch portions of the tablet. Oftentimes the segregation would be
done at the interface level, though on occasion (e.g. Cintiq 24HDT) the
tablet would combine two totally independent USB devices behind an internal
USB
This splits the 'wacom_setup_pentouch_input_capabilites' function into
pieces dedicated to doing setup for just the pen interface and just
the touch interface. This makes it easier to focus on the relevant
piece when making changes.
This patch introduces no functional changes.
Signed-off-by: Jaso
Historically, both the touch and pad tools would have shared the
'BTN_TOOL_FINGER' type. Any time you needed to distinguish the two, you
had to use some other bit of knowledge (e.g. that the pad was on the same
interface as the pen, and thus 'touch_max' would be zero).
To make these checks more re
On Wed, 3 Jun 2015 10:26:47 +
"Tirdea, Irina" wrote:
> > -Original Message-
> > From: Antonio Ospite [mailto:a...@ao2.it]
> > Sent: 28 May, 2015 18:58
> > To: Tirdea, Irina
> > Cc: Dmitry Torokhov; Bastien Nocera; linux-input@vger.kernel.org;
> > devicet...@vger.kernel.org; linux-ker
Dear Sam,
Do you also have fw_version and caps that can be entered in the Laptop-model
table ? The highest number there is currently 8 ..
Thanks,
Kind regards,
Ulrik
On Wed, Jun 03, 2015 at 04:26:33PM +0800, 洪一竹 wrote:
>
>
> add new icbody type for the h/w connect with elantech driver.
>
> Si
> Add a fixed-up HID descriptor for the Sony motion controller and enable
controls for the LED light as well as force-feedback.
Hi,
I think that a mistake has been made here with the report descriptor, it
looks like it is an exact duplicate of the one for the six-axis and it
does not match the doc
Signed-off-by: Simon Wood
---
drivers/hid/hid-core.c | 1 +
drivers/hid/hid-sony.c | 2 ++
2 files changed, 3 insertions(+)
diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
index aefb248..044e96a 100644
--- a/drivers/hid/hid-core.c
+++ b/drivers/hid/hid-core.c
@@ -1960,6 +1960,7 @@ s
On 06/03/2015 02:31 PM, Matt Whitlock wrote:
> On Wednesday, 3 June 2015, at 2:24 pm, Henrik Rydberg wrote:
>>> This patch changes the report_synaptics_data() function so that it reports
>>> the highest touch_major and highest tool_major of any touching finger as
>>> ABS_PRESSURE and ABS_TOOL_WIDTH
Hi Matt,
> This patch changes the report_synaptics_data() function so that it reports
> the highest touch_major and highest tool_major of any touching finger as
> ABS_PRESSURE and ABS_TOOL_WIDTH, respectively.
I appreciate the problem, but I would much rather have bcm5974 converted
to use input_m
On Wednesday, 3 June 2015, at 2:24 pm, Henrik Rydberg wrote:
> > This patch changes the report_synaptics_data() function so that it reports
> > the highest touch_major and highest tool_major of any touching finger as
> > ABS_PRESSURE and ABS_TOOL_WIDTH, respectively.
>
> I appreciate the problem,
The Synaptics X.org driver compares the ABS_PRESSURE values in evdev input
events to its FingerLow and FingerHigh parameters to determine how it
should translate touchpad events into X pointer and button events. During a
transition between single-touch and multi-touch, the touchpad on the
MacBookPr
> -Original Message-
> From: Antonio Ospite [mailto:a...@ao2.it]
> Sent: 28 May, 2015 18:58
> To: Tirdea, Irina
> Cc: Dmitry Torokhov; Bastien Nocera; linux-input@vger.kernel.org;
> devicet...@vger.kernel.org; linux-ker...@vger.kernel.org
> Subject: Re: [PATCH 2/9] input: goodix: fix var
On Tue, 2 Jun 2015, Andrew Duggan wrote:
> The HID device does not need to know about the ACPI device associated with
> the underlying i2c device. Setting the ACPI companion field in the HID device
> also has the side effect of causing HID to be set as wake capable, since
> acpi_bind_one uses's th
add new icbody type for the h/w connect with elantech driver.
Signed-off-by: Sam
---
drivers/input/mouse/elantech.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/input/mouse/elantech.c b/drivers/input/mouse/elantech.c
index 79363b6..af40c59 100644
--- a/drivers/input/mouse/elan
From: Steve Twiss
Add OnKey driver support for DA9063
Signed-off-by: Steve Twiss
---
Hi Dmitry,
If there are comments pending for this patch or if there are any outstanding
issues with this OnKey driver then could you please let me know so I can
resolve them?
Or, if you are busy or there is
From: "james.chen"
This patch refer 3.10 driver code to solve firmware upgrade
issue(Change 266813) and enable noise-immunity(Change 243875).
BUG=chrome-os-partner:39373
TEST=Test Elan Touch Screen on cyan project without problems.
---
drivers/input/touchscreen/elants_i2c.c | 2287 +
19 matches
Mail list logo
