ame), "%s %04hX:%04hX",
> client->name, hid->vendor, hid->product);
> + strlcpy(hid->phys, dev_name(&client->dev), sizeof(hid->phys));
>
> ret = hid_add_device(hid);
> if (ret) {
> --
Tested and
Reviewed-by: Daniel Mar
uot;Touchpad";
> + break;
> case HID_GD_SYSTEM_CONTROL:
> suffix = "System Control";
> break;
> --
I will drop my locally pending patch for this. ;)
Reviewed-by: Daniel Martin
--
To unsubscribe fr
On 28 September 2015 at 14:15, Mika Westerberg
wrote:
> For I2C HID devices output currently looks like:
>
> hid-multitouch ... input,hidraw0: HID v1.00 Mouse ...
>
> Add knowledge about I2C bus to hid_connect() so that it shows "I2C"
> correctly instead of "".
>
> Signed-off-by: Mika Westerber
Hi,
why do we skip constant fields (HID_MAIN_ITEM_CONSTANT) in hid-input
and hid-core?
In the "Device Class Definition for Human Interface Devices" (v1.11)
one can read:
"Constant indicates the item is a static read-only field in a
report and cannot be modified (written) by the host."
(As an
What's the problem with last minute fixes, which look so simple that
they can't cause any harm?
... This patch is discarded! :/
--
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.
02 c5 02 ff ff ff ff 00
cd 01 e7 3a 00 a6 19 a6 19 5a 05 5a 05 e2 01 29 02 ff ff ff ff 00
cd 01 e7 3b 00 bc 15 bc 15 84 09 84 09 df 01 24 02 ff ff ff ff 00
cd 01 e7 3c 00 fb 16 fb 16 4c 13 4c 13 8b 01 bd 01 ff ff ff ff 00
Next frame and we're back to normal mode/data.
Signed-off-
Section "Event Computation" had this:
...
ABS_MT_TOOL_X := C_X
ABS_MT_TOOL_X := C_Y
Replace the second ABS_MT_TOOL_X with ABS_MT_TOOL_Y.
Signed-off-by: Daniel Martin
---
Documentation/input/multi-touch-protocol.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
di
Just to prettify the log message. Otherwise it would be .
Signed-off-by: Daniel Martin
---
drivers/hid/hid-core.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
index e6fce23..2636fac 100644
--- a/drivers/hid/hid-core.c
+++ b/drivers/hid
On 14 September 2015 at 16:37, Daniel Martin wrote:
> I've retried this issue with v4.2 and it still exists.
I've got it! The patch(es) should pop up soon.
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majord.
oblem / keeps the events
floating.
Anyone has a clue, why we end up in such a state? Do you need more logs, which?
Cheers,
Daniel Martin
[0.00] Linux version 3.19.6-grsec+ (be1060@ts-4) (gcc version 4.9.2 (Debian 4.9.2-10) ) #11 SMP Tue Jun 9 11:03:29 CEST 2015
[0.00] Command line:
On 21 May 2015 at 04:40, Alan Wu wrote:
> Hello Jiri,
> I believe the patch may work, but I would rename the IDs. Obviously
> I can't test Surface 3 non-Pro cover, but the difference is likely due
> to the following:
>
> This is 0x07dc (I do own)
> http://www.microsoftstore.com/store/msusa/en_U
On 25 March 2015 at 02:20, Filip Ayazi wrote:
> Sets min_max_quirk values for LEN2006 touchpad found in Lenovo Thinkpad E440
> (board_id=2691).
Dmitry already applied a patch for the E440:
http://www.spinics.net/lists/linux-input/msg37497.html
--
To unsubscribe from this list: send the line "
@@ static const char * const topbuttonpad_pnp_ids[] = {
> "LEN0041",
> "LEN0042", /* Yoga */
> "LEN0045",
> - "LEN0046",
> "LEN0047",
> "LEN0049",
> "LEN2000",
>
From: Daniel Martin
Split the function synaptics_resolution() into
synaptics_resolution() and synaptics_quirks().
synaptics_resolution() will be called before synaptics_quirks() to query
dimensions and resolutions before overwriting them with quirks.
v2: Removed SYN_ID_MAJOR() check from
From: Daniel Martin
Logging the dimension values we queried (info) and the values we use
from a quirk to overwrite (warn) can be helpful for debugging.
This partly relates to bug:
https://bugzilla.kernel.org/show_bug.cgi?id=91541
Signed-off-by: Daniel Martin
---
drivers/input/mouse
From: Daniel Martin
Query the min dimensions even if the check
SYN_EXT_CAP_REQUESTS(priv->capabilities) >= 7
fails, but we know that the firmware version 8.1 is safe.
With that we don't need quirks for post-2013 models anymore as they
expose correct min and max dimensions.
v2:
Add a min/max range for board ids to the min/max coordinates quirk. This
makes it possible to restrict quirks to specific models based upon their
board id. The define ANY_BOARD_ID (0) serves as a wildcard.
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=91541
Signed-off-by: Daniel Martin
From: Daniel Martin
The firmware of the X240 (LEN0035, 2013/12) exposes the same values
x [1232..5710], y [1156..4696]
as the quirk applies.
Signed-off-by: Daniel Martin
---
drivers/input/mouse/synaptics.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/input
s
Cheers,
Daniel Martin
--
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
te:
> >>> Hi Daniel,
> >>>
> >>> On Tue, Jan 27, 2015 at 3:34 AM, Daniel Martin
> >>> wrote:
> >>>> From: Daniel Martin
> >>>>
> >>>> If we queried min/max dimensions of x [1266..5674], y [1170..4684] w
niel,
> >>>
> >>>in one hand I would like to see that upstream ASAP. But on the other
> >>>hand, I have some concerns here and there regarding this series.
> >>>
> >>>On Tue, Jan 27, 2015 at 3:34 AM, Daniel Martin
> >>> wrote:
Hi,
this is the second version of my patches to address the problems
described at:
https://bugzilla.kernel.org/show_bug.cgi?id=91541
I have incorporated changes according to Hans comments. That means I
removed the patch
Input: synaptics - Add PnP id for X1 Carbon 1nd
as the PnP id doesn't
From: Daniel Martin
Query the min dimensions even if the check
SYN_EXT_CAP_REQUESTS(priv->capabilities) >= 7
fails, but we know that the firmware version is safe. Atm. this is
version 8.1 only.
With that we don't need quirks for post-2013 models anymore as they
expose correct
From: Daniel Martin
Split the function synaptics_resolution() into
synaptics_resolution() and synaptics_quirks().
synaptics_resolution() will be called before synaptics_quirks() to query
dimensions and resolutions before overwriting them with quirks.
v2: Removed SYN_ID_MAJOR() check from
From: Daniel Martin
The firmware of the X240 (LEN0035, 2013/12) exposes the same values
x [1232..5710], y [1156..4696]
as the quirk applies.
Signed-off-by: Daniel Martin
---
drivers/input/mouse/synaptics.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/input
From: Daniel Martin
If we queried min/max dimensions of x [1266..5674], y [1170..4684] we
have post-2013 model and don't need to apply any quirk.
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=91541
Signed-off-by: Daniel Martin
---
drivers/input/mouse/synaptics.c | 5 +
1
From: Daniel Martin
Logging the dimension values we queried (info) and the values we use
from a quirk to overwrite (warn) can be helpful for debugging.
This partly relates to bug:
https://bugzilla.kernel.org/show_bug.cgi?id=91541
Signed-off-by: Daniel Martin
---
drivers/input/mouse
Withdrawn!
On 22 January 2015 at 17:46, Daniel Martin wrote:
> From: Daniel Martin
>
> This adds the PnP id (LEN0030) for the X1 Carbon 1nd (2013/07) to the
> list of known PnP ids.
>
> The firmware exposes the correct dimensions:
> x [1264..5678], y [1124..4732].
>
On 22 January 2015 at 17:46, Daniel Martin wrote:
> From: Daniel Martin
>
> This adds the PnP id (LEN0030) for the X1 Carbon 1nd (2013/07) to the
> list of known PnP ids.
>
> The firmware exposes the correct dimensions:
> x [1264..5678], y [1124..4732].
>
> S
From: Daniel Martin
Split the function synaptics_resolution() into
synaptics_resolution() and synaptics_quirks().
synaptics_resolution() will be called before synaptics_quirks() to query
dimensions and resolutions before overwriting them with quirks.
Signed-off-by: Daniel Martin
),
Helix (2013?) and
X1 Carbon (2013, LEN0030).
Any comments are welcome,
Daniel Martin
--
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: Daniel Martin
The firmware of the X240 (LEN0035, 2013/12) exposes the same values
x [1232..5710], y [1156..4696]
as the quirk applies.
Signed-off-by: Daniel Martin
---
drivers/input/mouse/synaptics.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/input
From: Daniel Martin
Logging the dimension values we queried (info) and the values we use
from a quirk to overwrite (warn) can be helpful for debugging.
This partly relates to bug:
https://bugzilla.kernel.org/show_bug.cgi?id=91541
Signed-off-by: Daniel Martin
---
drivers/input/mouse
From: Daniel Martin
This adds the PnP id (LEN0030) for the X1 Carbon 1nd (2013/07) to the
list of known PnP ids.
The firmware exposes the correct dimensions:
x [1264..5678], y [1124..4732].
Signed-off-by: Daniel Martin
---
drivers/input/mouse/synaptics.c | 1 +
1 file changed, 1
From: Daniel Martin
If we queried min/max dimensions of x [1266..5674], y [1170..4684] we
have post-2013 model and don't need to apply any quirk.
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=91541
Signed-off-by: Daniel Martin
---
drivers/input/mouse/synaptics.c | 5 +
1
From: Daniel Martin
Query the min dimensions even if the check
SYN_EXT_CAP_REQUESTS(priv->capabilities) >= 7
fails, but we know that the firmware version is safe. Atm. this is
version 8.1 only.
With that we don't need quirks for post-2013 models anymore as they
expose correct
36 matches
Mail list logo
