have the time to
implement/test at the moment. If some else does that would be good, can we
make sure that the kconfig/makefile stuff uses same/sensible HID_CONFIGs?
Simon
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majord..
When plugged in the Logitech G920 wheel starts with USBID 046d:c261
and behaviors as a vendor specific class. If a 'magic' byte sequence
is sent the wheel will detach and reconnect as a HID device with the
USBID 046d:c262.
Signed-off-by: Simon Wood
---
drivers/input/joystick/x
Patch add support for the 'very long' HID++ packets, which are
64 bytes in length.
Signed-off-by: Simon Wood
---
drivers/hid/hid-logitech-hidpp.c | 59
1 file changed, 48 insertions(+), 11 deletions(-)
diff --git a/drivers/hid/hid-logitech
The normal HID functions work to give input functionality using
joystick/event interface.
Note: in 'hidpp_probe()' we have to start the hardware to get packets
flowing, the same might apply in future for other devices which don't
use the unifying protocol.
Signed-off-by: Simon W
The Logitech G920 uses a couple of vendor specific usage pages,
which results in incorrect number of axis/buttons being detected.
This patch adds these pages to the 'ignore' list.
Reported-by: Elias Vanderstuyft
Signed-off-by: Simon Wood
---
drivers/hid/hid-input.c | 4
inc
The G920 can adjust the amount of 'turn' it permits, this patch adds
a sysfs file 'range' to control this.
Signed-off-by: Simon Wood
---
drivers/hid/hid-logitech-hidpp.c | 140 ++-
1 file changed, 139 insertions(+), 1 deletion(-)
diff --g
Ensure that the G920 is not given the default deadzones.
Signed-off-by: Simon Wood
---
drivers/hid/hid-logitech-hidpp.c | 20
1 file changed, 20 insertions(+)
diff --git a/drivers/hid/hid-logitech-hidpp.c b/drivers/hid/hid-logitech-hidpp.c
index fc553e3..f2a4811 100644
.
The future... as the internals of the wheel are considerably more 'capable' we
are working on implementing Force Feedback using the forth-coming KLGD system.
Simon Wood (6):
INPUT: xpad: switch Logitech G920 Wheel into HID mode
HID: hid-logitech-hidpp: Add support for very long packets
On Thu, November 19, 2015 11:31 am, Dmitry Torokhov wrote:
> On Thu, Nov 19, 2015 at 02:50:51PM +0100, Jiri Kosina wrote:
>
>> On Thu, 12 Nov 2015, Simon Wood wrote:
>>
>>
>>> When plugged in the Logitech G920 wheel starts with USBID 046d:c261
>>> and
fa 9f 13 54 80 0a f6 df e5 3f
01 00 01 3c 23 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
47 a7 c2 bc fa 9f 13 54 80 0a f6 df e5 3f
--
Attached are some quick notes from 15mins playing with the device.
Cheer
The G920 can adjust the amount of 'turn' it permits, this patch adds
a sysfs file 'range' to control this.
Signed-off-by: Simon Wood
---
drivers/hid/hid-logitech-hidpp.c | 140 ++-
1 file changed, 139 insertions(+), 1 deletion(-)
diff --g
> Note: These patches are applied to Jiri's 'for-next' tree to work with
> the other HID++ changes already queued for 4.4.
Whoops, left this note in by mistake. These patches are against 4.4 HEAD.
Simon.
--
To unsubscribe from this list: send the line "unsubscribe lin
Ensure that the G920 is not given the default deadzones.
Signed-off-by: Simon Wood
---
drivers/hid/hid-logitech-hidpp.c | 20
1 file changed, 20 insertions(+)
diff --git a/drivers/hid/hid-logitech-hidpp.c b/drivers/hid/hid-logitech-hidpp.c
index 80ebd1c..e235f3d 100644
The Logitech G920 uses a couple of vendor specific usage pages,
which results in incorrect number of axis/buttons being detected.
This patch adds these pages to the 'ignore' list.
Reported-by: Elias Vanderstuyft
Signed-off-by: Simon Wood
---
drivers/hid/hid-input.c | 4
inc
When plugged in the Logitech G920 wheel starts with USBID 046d:c261
and behaviors as a vendor specific class. If a 'magic' byte sequence
is sent the wheel will detach and reconnect as a HID device with the
USBID 046d:c262.
Signed-off-by: Simon Wood
---
drivers/input/joystick/x
Patch add support for the 'very long' HID++ packets, which are
64 bytes in length.
Signed-off-by: Simon Wood
---
drivers/hid/hid-logitech-hidpp.c | 59
1 file changed, 48 insertions(+), 11 deletions(-)
diff --git a/drivers/hid/hid-logitech
The normal HID functions work to give input functionality using
joystick/event interface.
Note: in 'hidpp_probe()' we have to start the hardware to get packets
flowing, the same might apply in future for other devices which don't
use the unifying protocol.
Signed-off-by: Simon W
Patch-V2 tweaked as per Benjamin's requests.
This series of patches provide input support for the Logitech G920 gaming wheel.
This wheel is internally different from the other Logitech wheels; when first
connected it is in X-Box mode and can instructed to switch to HID with a 'magic
command' (1
> With this change, and the nitpicks in the other patches, the series is:
> Reviewed-by: Benjamin Tissoires
Have Patch-V2 in progress. Other build problems stopped in last night but
trying again with new pull - hopefully they are fixed.
Simon
--
To unsubscribe from this list: send th
The G920 can adjust the amount of 'turn' it permits, this patch adds
a sysfs file 'range' to control this.
Signed-off-by: Simon Wood
---
drivers/hid/hid-logitech-hidpp.c | 140 ++-
1 file changed, 139 insertions(+), 1 deletion(-)
diff --g
When plugged in the Logitech G920 wheel starts with USBID 046d:c261
and behaviors as a vendor specific class. If a 'magic' byte sequence
is sent the wheel will detach and reconnect as a HID device with the
USBID 046d:c262.
Signed-off-by: Simon Wood
---
drivers/input/joystick/x
Ensure that the G920 is not given the default deadzones.
Signed-off-by: Simon Wood
---
drivers/hid/hid-logitech-hidpp.c | 22 ++
1 file changed, 22 insertions(+)
diff --git a/drivers/hid/hid-logitech-hidpp.c b/drivers/hid/hid-logitech-hidpp.c
index 03e01be..853b9c2 100644
Patch add support for the 'very long' HID++ packets, which are
64 bytes in length.
Signed-off-by: Simon Wood
---
drivers/hid/hid-logitech-hidpp.c | 59
1 file changed, 48 insertions(+), 11 deletions(-)
diff --git a/drivers/hid/hid-logitech
The normal HID functions work to give input functionality using
joystick/event interface.
Signed-off-by: Simon Wood
---
drivers/hid/hid-core.c | 1 +
drivers/hid/hid-ids.h| 1 +
drivers/hid/hid-logitech-hidpp.c | 69 +++-
3 files c
This series of patches provide input support for the Logitech G920 gaming wheel.
This wheel is internally different from the other Logitech wheels; when first
connected it is in X-Box mode and can instructed to switch to HID with a 'magic
command' (1st patch). Once the wheel reconnects in HID mo
The Logitech G920 uses a couple of vendor specific usage pages,
which results in incorrect number of axis/buttons being detected.
This patch adds these pages to the 'ignore' list.
Reported-by: Elias Vanderstuyft
Signed-off-by: Simon Wood
---
drivers/hid/hid-input.c | 2 +-
include/l
At present the G29 is mis-identified as a DFGT, this patch ensures
that the wheel is correctly detected and allows setting the LEDs and
turning range via the '/sys' interface.
This wheel can also emulate other types of Logitech wheels.
Signed-off-by: Simon Wood
---
drivers/hid/hid-co
Simplfy how hid-logitech driver detects the native mode of the wheel,
done by looking at the USB-ID revision and comparing bit mask.
Signed-off-by: Simon Wood
---
drivers/hid/hid-lg4ff.c | 70 -
1 file changed, 28 insertions(+), 42 deletions
When plugged in the Logitech G920 wheel starts with USBID 046d:c261
and behaviors as a vendor specific class. If a 'magic' byte sequence
is sent the wheel will detach and reconnect as a HID device with the
USBID 046d:c262.
---
drivers/input/joystick/xpad.c | 16
1 file changed, 16
This patch adds basic support for the Logitech G920 wheel when in HID
mode. This wheel 'speaks' the HID++ protocol, and therefor is driven
with hid-logitech-hidpp.
At this stage the driver only shows that it can communicate with the
wheel by outputting the name discovered over HID++.
The normal H
The G920 can adjust the amount of 'turn' it permits, this patch adds
a sysfs file 'range' to control this.
---
drivers/hid/hid-logitech-hidpp.c | 140 ++-
1 file changed, 139 insertions(+), 1 deletion(-)
diff --git a/drivers/hid/hid-logitech-hidpp.c b/drivers/h
Patch add support for the 'very long' HID++ packets, which are
64 bytes in length.
---
drivers/hid/hid-logitech-hidpp.c | 59
1 file changed, 48 insertions(+), 11 deletions(-)
diff --git a/drivers/hid/hid-logitech-hidpp.c b/drivers/hid/hid-logitech-hidpp.c
The Logitech G920 uses a couple of vendor specific usage pages,
which results in incorrect number of axis/buttons being detected.
This patch adds these pages to the 'ignore' list.
Reported-by: Elias Vanderstuyft
---
drivers/hid/hid-input.c | 2 +-
include/linux/hid.h | 2 ++
2 files changed
ernel: [11080.134339] logitech: probe of
0003:046D:C24F.0003 failed with error -1
--
Any suggestions as to how we can 'ignore' or unbind the 2nd interface in
order to only work with the 1st?
Simon
G29 connected, appears as DFEX then we send command to get it to reconnect
--
Sep 28 12:30:
> The first patch might conflict with Simon's current work in progress, so
> that's why Simon is CC-ed to it.
Thanks for the 'heads-up', I think that the HID++ stuff I have in progress
won't be ready until the 4.4 cycle,
Cheers,
Simon
--
To unsubscribe from this l
as G29 (900' turn).
The mode should be selectable something like
--
root@retrobox:/home/simon# cd /sys/bus/hid/devices/0003\:046D\:C29B.0002
root@retrobox:/sys/bus/hid/devices/0003:046D:C29B.0002# ls
alternate_modes country driver hidraw input leds modalias power
range real_id report
On Fri, Aug 14, 2015 at 12:31:09AM +0300, Laurent Pinchart wrote:
> On Thursday 13 August 2015 11:26:32 Geert Uytterhoeven wrote:
> > On Thu, Aug 13, 2015 at 2:05 AM, Simon Horman wrote:
> > > On Wed, Jul 08, 2015 at 09:51:49AM +0900, Simon Horman wrote:
> > >> On T
On Wed, Jul 08, 2015 at 09:51:49AM +0900, Simon Horman wrote:
> On Tue, Jul 07, 2015 at 09:56:29AM +0300, Laurent Pinchart wrote:
> > Hi Simon,
> >
> > On Tuesday 07 July 2015 09:26:21 Simon Horman wrote:
> > > On Mon, Jul 06, 2015 at 04:29:33PM +0300, Laurent Pincha
for adjust HID descriptor and handle
switching between emulation and native modes.
Signed-off-by: Simon Wood
---
drivers/hid/hid-ids.h | 1 +
drivers/hid/hid-lg.c | 2 ++
2 files changed, 3 insertions(+)
diff --git a/drivers/hid/hid-ids.h b/drivers/hid/hid-ids.h
index b04b082..653bfd4 100644
were reported (*) over the on Bluetooth list, and
appear in both the HID and the HCI streams (suggesting that they are
really sent from device). They are not seen on the USB connection.
Dropping them in 'raw_event()' seems a sensible approach,
Simon.
* http://www.spinics.net/lis
Patch HID report descriptor to add joystick axis for the L1 button (previously
missing).
Signed-off-by: Simon Wood
---
drivers/hid/hid-sony.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/drivers/hid/hid-sony.c b/drivers/hid/hid-sony.c
index ed2f008..69586b3
On Tue, Jul 07, 2015 at 09:56:29AM +0300, Laurent Pinchart wrote:
> Hi Simon,
>
> On Tuesday 07 July 2015 09:26:21 Simon Horman wrote:
> > On Mon, Jul 06, 2015 at 04:29:33PM +0300, Laurent Pinchart wrote:
> > > On Monday 06 July 2015 12:55:32 Geert Uytterhoeven wr
On Mon, Jul 06, 2015 at 04:29:33PM +0300, Laurent Pinchart wrote:
> Hi Geert,
>
> Thank you for the patch.
>
> On Monday 06 July 2015 12:55:32 Geert Uytterhoeven wrote:
> > Replace the deprecated generic "adi,adxl34x" compatible value by the
> > adxl345-specific "adi,adxl345" value, cfr. commit e
x27;, but is the 117 taken from the accelerometer
> datasheet? What is it? And BTW I get 9.80665/117 = 0.083817521
The '117' was taken from experimentation, average value accessed across
all accelerometer axis on a stationary device.
It does appear however that I can not use a calculator ;
> the SixAxis also have a gyroscope, I don't know how useful/reliable it
> is, but it's there.
I had a recollection that there was a gyro, but didn't see it when looking
at the 'hidraw' stream.
It might be affected by the 'multi-touch axes' bug.
Simon
-
---
drivers/hid/hid-sony.c | 71 --
1 file changed, 69 insertions(+), 2 deletions(-)
diff --git a/drivers/hid/hid-sony.c b/drivers/hid/hid-sony.c
index b7a7f0d..ce0526d 100644
--- a/drivers/hid/hid-sony.c
+++ b/drivers/hid/hid-sony.c
@@ -39,9 +39,11
---
drivers/hid/hid-sony.c | 50 +++---
1 file changed, 47 insertions(+), 3 deletions(-)
diff --git a/drivers/hid/hid-sony.c b/drivers/hid/hid-sony.c
index c4686e3..b7a7f0d 100644
--- a/drivers/hid/hid-sony.c
+++ b/drivers/hid/hid-sony.c
@@ -37,6 +37,11
This series of patches is a RFC for the idea of connecting motion capability
controllers to the IIO subsystem, initially targeting the Sony SixAxis
controller. In the future I hope that this can be used for sensor packs used
in VR headset/devices.
The advantage of the IIO subsystem is that the da
---
drivers/hid/hid-sony.c | 87 +-
1 file changed, 79 insertions(+), 8 deletions(-)
diff --git a/drivers/hid/hid-sony.c b/drivers/hid/hid-sony.c
index ce0526d..f1c1a16 100644
--- a/drivers/hid/hid-sony.c
+++ b/drivers/hid/hid-sony.c
@@ -62,7 +62,7
---
drivers/hid/hid-sony.c | 153 -
1 file changed, 152 insertions(+), 1 deletion(-)
diff --git a/drivers/hid/hid-sony.c b/drivers/hid/hid-sony.c
index 6ca96ce..c4686e3 100644
--- a/drivers/hid/hid-sony.c
+++ b/drivers/hid/hid-sony.c
@@ -36,6 +36,7
, is this normal for IIO?
Next is a little code clean-up and I'll post what I have for some more
comments,
Simon.
--
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
1 02 c0 c0 00|.|
0095
Signed-off-by: Simon Wood
---
drivers/hid/hid-sony.c | 91 +-
1 file changed, 90 insertions(+), 1 deletion(-)
diff --git a/drivers/hid/hid-sony.c b/drivers/hid/hid-sony.c
index af02139..ed2f008 100644
--- a/drivers/hid/hid
Signed-off-by: Simon Wood
---
drivers/hid/hid-sony.c | 41 +
1 file changed, 33 insertions(+), 8 deletions(-)
diff --git a/drivers/hid/hid-sony.c b/drivers/hid/hid-sony.c
index 3fba2dca..af02139 100644
--- a/drivers/hid/hid-sony.c
+++ b/drivers/hid/hid
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 044e96a..a64f862 100644
--- a/drivers/hid/hid-core.c
+++ b/drivers/hid/hid-core.c
@@ -1962,6 +1962,7
ing at
iio_dummy_event and iios_sysfs for inspiration
On the assumption that there will be multiple devices (either same type or
with different HID drivers) all trying to issue triggers, we'd need to be
a little careful.
Is there a 'short-cut' we can use if a HID device is only r
[resent as I screwed up addressing... sorry]
This patch is a RFC/POC for the idea of using the iio-subsystem as the
'proper' way to communicate the state of motion enabled controllers to
the Linux internals.
I have started with the hid-sony driver, with support for the SixAxis's
3 Accelerometers.
'fixing' their byte order would break user-space
drivers such as PSMoveAPI.
It is hoped to resolve this at a future time.
Signed-off-by: Simon Wood
---
drivers/hid/hid-sony.c | 69 --
1 file changed, 44 insertions(+), 25 deletions(-)
di
Add support for the battery charge level and state to be read via BT.
This is not support via USB as there is no know way to get the device
sending 'input' reports over USB.
Signed-off-by: Simon Wood
---
drivers/hid/hid-sony.c | 15 +++
1 file changed, 11 insertions(+), 4
The LED and Rumble control only function via BT if the full output report
is sent. The large report still functions via USB.
Signed-off-by: Simon Wood
---
drivers/hid/hid-sony.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/drivers/hid/hid-sony.c b/drivers/hid
Split quirk for PS Move Controller as it has to be treated differently
when connected via BT.
Signed-off-by: Simon Wood
---
drivers/hid/hid-sony.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/drivers/hid/hid-sony.c b/drivers/hid/hid-sony.c
index 6fcc2b4..28dba6c
I wrote this for accelerometers that are in tablets/convertibles:
> https://github.com/hadess/iio-sensor-proxy/
Thanks I'll check it out. Thinking more of a AHRS rather than 'just'
rotating the screen. ;-)
Simon
--
To unsubscribe from this list: send the line "unsubscribe
tion to IIO system and pushing the Accel/Gyro/Mag values there
(rather than exposing them on the joystick interface) make sense?
Are there any examples of other devices doing this, so I can re-use the code?
Simon.
--
To unsubscribe from this list: send the line "unsubscribe linux-input" i
owever I have noticed that this affects/reshuffles the output
of '/dev/hidraw0', which would 'corrupt' the data going into the existing
user-mode drivers (such as psmoveapi).
Is there a 'better' place/way to reshuffle this data, or is this just how
it needs to be?
Giv
the 'original' reports (ie. with hid-sony changing them)
for reference. Note the BT one has a trailing zero (like the DS4 has)
which prevents decoding... I just cropped it off to decode.
Simon.
psmove_bt_report_orig.bin
Description: Binary data
psmove_bt_report_orig.code
Description
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
ich will enable full USB operation?
Simon.
PS. I did not try BT connection as that apparently requires Bluez > 5.0,
which is a pain on _that_ machine.
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majord...@vger.kernel.org
ewed-by: Wolfram Sang
> Signed-off-by: Geert Uytterhoeven
> ---
> v2:
> - Add Reviewed-by.
Reviewed-by: Simon Horman
--
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
adi,adxl346 and adi,adxl345,
> in that order.
>
> Signed-off-by: Laurent Pinchart
> Acked-by: Wolfram Sang
> Signed-off-by: Geert Uytterhoeven
> ---
> v2:
> - Add Acked-by.
Reviewed-by: Simon Horman
--
To unsubscribe from this list: send the line "unsubscribe lin
sina wrote:
On Thu, 29 Jan 2015,li...@simon-woerner.de wrote:
From: Simon Wörner
HID: Add driver for acer keybard with broken rdesc
Hi Simon,
to make sure proper device <-> driver binding is performed, you also have
to add device ID to the hid_have_special_driver[] array.
To the co
.
Yes, it does look like hid_post_reset() should be returning proper error
codes on failure, to allow correct behaviour here. usb_reset_device()
should still interpret such error code returns as a need to attempt a
rebind.
1595 }
1596 return status;
1597 }
regards,
d not force 'FF_MEMLESS=Y' (just leave that as module
too).
There is also the 'LEDS CLASS' which is required for G27 support. IIRC
there was some 'magic' done with hid-steelseries to tweak problems with
LEDs.
I'd be open to helping this happen, given some guidance.
logitech' which use any
other transport (HID over Bluetooth or the like)?
Simon.
--
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
with the new
build, so it looks like my patch is not required after all (and fixing in
LED subsystem makes far more sense).
I am, however, confused about what I pulled and built. It definately had
the patch (I looked in drivers/leds/leds.h before building) but built as
3.19 guess I'll
n't
> replicate your bug.
I guess it's possible, I am running 3.19.0rc5. I'll build 3.19 and see if
it's showing the bug.
Simon
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majord...@vger.kernel.org
More maj
27;s
own interface.
Patch limits the LEDs 'value' to the 'max brightness', thus preventing bug.
Tested with SixAxis DS3, DS4 and Intec (3rd party) controllers, via USB
connection.
Signed-off-by: Simon Wood
---
drivers/hid/hid-sony.c | 3 +++
1 file changed, 3 insertions(+)
diff --
nst latest linux-next
> - Document the newly introduced sysfs interfaces in appropriate
> commits
> - Assume that we are targeting kernel version 4.1
> - Fix a misleading error message regarding unsupported wheel mode
This version looks good to me; tested with WiiW
lier. I'd be happy to apply and fix later,
but I suspect Jiri will say fix it first.
Simon
PS. Resent via Gmail as my hosting is having issues.
On Fri, 6 Feb 2015 10:27:21 -0700, si...@mungewell.org wrote:
> > This patch series improves handling of various Logitech gaming wheels and
>
eel so far).
This newer code should automatically cope with new wheels in the future.
Thanks to Michal for undertaking this work. I have been testing the code
over the past weeks and believe it to be working, I will confirm mid-next
week when I can gain access to my wheels.
Simon
--
To unsubscr
gain.
--
Would it make more sense to use EPERM, or is there another error code we
can throw to be more informative.
Thanks,
Simon.
--
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
The new version is nearly finished, I will send it later today.
See below for additional changes not in the other mails.
Am 28.01.15 um 00:46 schrieb Andrew Duggan:
> On Tue, Jan 27, 2015 at 8:13 AM, Benjamin Tissoires
> wrote:
>> On Tue, Jan 27, 2015 at 10:10 AM, Simon Wörne
2:03 PM, Simon Wörner wrote:
>> From: Simon Wörner
>>
>> Signed-off-by: Simon Wörner
>> ---
>> drivers/hid/Kconfig | 6 ++
>> drivers/hid/Makefile| 1 +
>> drivers/hid/hid-ids.h | 1 +
>> drivers/hid/hid-synaptics.c | 19
Synaptics keyboards (USB ID 06cb:2968) e.g. in Acer SW5-012
have the following issue:
- The report descriptor specifies an excessively large number of consumer
usages (2^15), which is more than HID_MAX_USAGES. This prevents proper
parsing of the report descriptor.
--
To unsubscribe from this
From: Simon Wörner
Signed-off-by: Simon Wörner
---
drivers/hid/Kconfig | 6 ++
drivers/hid/Makefile| 1 +
drivers/hid/hid-ids.h | 1 +
drivers/hid/hid-synaptics.c | 190
4 files changed, 198 insertions(+)
create mode
> Even if I did add the plumbing for HID over into the LED subsystem, is
> there an
> easy way to correlate input devices and their LEDs from userspace?
You can follow the symlinks through the '/sys' filesystem. For example the
following all point to the same LED.
--
simo
>From Jiri Kosina , Wed, Sep 03, 2014 at 04:37:05PM +0200:
> On Wed, 3 Sep 2014, Dylan Alex Simon wrote:
>
> > I think that did the trick. I've run through the whole cycle about 20 times
> > in various conditions, and it seems solid so far. Thanks!
>
> Thanks. I
> Hrm, what we really want is to first destroy the LED interface, otherwise
> someone might have re-queued the workqueue through thingm_led_set() after
> it has been flushed / cancelled already.
>
> Could you please give it one more shot with the patch below? Thanks for
> your prompt testing.
>
> I sent you wrong version of the patch, sorry for that. Could you please
> try the one below instead?
>
>
> diff --git a/drivers/hid/hid-thingm.c b/drivers/hid/hid-thingm.c
> index 134be89..dffc50d 100644
> --- a/drivers/hid/hid-thingm.c
> +++ b/drivers/hid/hid-thingm.c
> @@ -208,7 +208,7 @@ un
>From Jiri Kosina , Wed, Sep 03, 2014 at 09:29:07AM +0200:
> On Tue, 2 Sep 2014, Dylan Alex Simon wrote:
>
> > Some combination of kernel debugging options and killing processes let it
> > survive long enough to write the backtrace to disk. A simple modprobe/rmmod
> >
>From Jiri Kosina , Tue, Sep 02, 2014 at 11:32:30PM +0200:
> On Tue, 2 Sep 2014, Benjamin Tissoires wrote:
>
> > > Whenever either disconnecting the USB device or simply rmmod'ing the
> > > module
> > > (even when not in use), I get a kernel panic. I haven't managed to
> > > capture a
> > > bac
>From Benjamin Tissoires , Tue, Sep 02, 2014 at
>03:58:08PM -0400:
> Hi,
>
> On 09/02/2014 01:46 PM, Dylan Alex Simon wrote:
> > Whenever either disconnecting the USB device or simply rmmod'ing the module
> > (even when not in use), I get a kernel panic. I h
Whenever either disconnecting the USB device or simply rmmod'ing the module
(even when not in use), I get a kernel panic. I haven't managed to capture a
backtrace, but at least the first two lines were saved after an rmmod:
18:53:17 kernel: thingm 0003:27B8:01ED.0004: hidraw3: USB HID v1.01 Devic
---
drivers/hid/hid-lg4ff.c | 81 +++--
1 file changed, 78 insertions(+), 3 deletions(-)
diff --git a/drivers/hid/hid-lg4ff.c b/drivers/hid/hid-lg4ff.c
index 0ba0838..1be561e 100644
--- a/drivers/hid/hid-lg4ff.c
+++ b/drivers/hid/hid-lg4ff.c
@@ -41,11 +
---
drivers/hid/hid-lg.c| 17 -
drivers/hid/hid-lg.h| 7 +--
drivers/hid/hid-lg4ff.c | 4 ++--
3 files changed, 23 insertions(+), 5 deletions(-)
diff --git a/drivers/hid/hid-lg.c b/drivers/hid/hid-lg.c
index a976f48..81ba24d 100644
--- a/drivers/hid/hid-lg.c
+++ b/dr
es[i].product_id);
- break;
- }
- }
-
- if (i == ARRAY_SIZE(lg4ff_devices)) {
- hid_err(hid, "Device is not supported by lg4ff driver. If you
think it should be, consider reporting a bug to"
- "LKML,
---
drivers/hid/hid-lg4ff.c | 126 +---
1 file changed, 55 insertions(+), 71 deletions(-)
diff --git a/drivers/hid/hid-lg4ff.c b/drivers/hid/hid-lg4ff.c
index eda07a2..0ba0838 100644
--- a/drivers/hid/hid-lg4ff.c
+++ b/drivers/hid/hid-lg4ff.c
@@ -32,21
;m tied up with work stuff for the next week or so (and won't
have access to the hardware).
If people can test/comment that would be great,
Simon
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majord...@vger.kernel.org
Mo
If the device data is not accessible for some reason, returning 0 will cause
the call to be
continuously called again as none of the string has been 'consumed'.
Signed-off-by: Simon Wood
---
drivers/hid/hid-lg4ff.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
> Simon mailed me his revised patchset which has the changes broken out into
> four separate patches and allows to switch "extended compatibility" modes
> on
> the fly through sysfs. I looked them over and I they seem fine to me. I
> suppose he'll submit them for r
If the device data is not accessible for some reason, returning 0 will cause
the call to be
continuously called again as none of the string has been 'consumed'.
---
drivers/hid/hid-lg4ff.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/hid/hid-lg4ff.c b/drivers/hi
all options for control.
Cheers,
Simon.
--
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
1 - 100 of 291 matches
Mail list logo
