On Mon, 2015-06-08 at 22:38 -0400, si...@mungewell.org wrote:
Hi all,
I'm in the process of fixing the HID descriptor for the PS3 Move
Controller. which has a particularly convoluted layout for it's
Accelormeters, Gyros and Magnetometers involving 2 sets of data per
output
report.
Hi folks,
I've found a reproducable problem where the touchscreen stops sending events.
The touchscreen is a NTRG (1b96:1b05) inside of a MS Surface Pro 3 and
the i2c-hid reports errors at bootup:
[ 43.744915] i2c_hid i2c-NTRG0001:01: error in i2c_hid_init_report
size:9 / ret_size:0
[
On 21 May 2015 at 04:40, Alan Wu alan.c...@gmail.com 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)
On Tuesday 09 June 2015 13:12:42 Pavel Machek wrote:
On Tue 2015-06-09 12:54:21, Pavel Machek wrote:
I did echo kbd-capslock trigger, but still no luck. (That might be
bug in Debian, IIRC?)
I tried rebooting with stock Debian kernel, and the bug is there, too.
Best regards,
On Tue 2015-06-09 13:12:42, Pavel Machek wrote:
On Tue 2015-06-09 12:54:21, Pavel Machek wrote:
Hi!
I finally was able to spend some time looking over Samuel's patch set
switching input LEDs from custom implementation over to standard LED class
devices and I think this is the shape
On Tue 2015-06-09 13:22:21, Pali Rohár wrote:
On Tuesday 09 June 2015 13:12:42 Pavel Machek wrote:
On Tue 2015-06-09 12:54:21, Pavel Machek wrote:
I did echo kbd-capslock trigger, but still no luck. (That might be
bug in Debian, IIRC?)
I tried rebooting with stock Debian kernel, and
Hi!
I finally was able to spend some time looking over Samuel's patch set
switching input LEDs from custom implementation over to standard LED class
devices and I think this is the shape I am reasonably happy with. The
changes:
Thanks!
Please take a look and see if you see any holes.
On Tue 2015-06-09 12:54:21, Pavel Machek wrote:
Hi!
I finally was able to spend some time looking over Samuel's patch set
switching input LEDs from custom implementation over to standard LED class
devices and I think this is the shape I am reasonably happy with. The
changes:
Thanks!
On 09 June 2015 07:51 Lee Jones wrote:
On Mon, 08 Jun 2015, Dmitry Torokhov wrote:
On Tue, May 19, 2015 at 11:32:45AM +0100, S Twiss wrote:
From: Steve Twiss stwiss.opensou...@diasemi.com
Add MFD support for the DA9063 OnKey driver
The function da9063_clear_fault_log() is added
On Mon, 08 Jun 2015, Dmitry Torokhov wrote:
On Tue, May 19, 2015 at 11:32:45AM +0100, S Twiss wrote:
From: Steve Twiss stwiss.opensou...@diasemi.com
Add MFD support for the DA9063 OnKey driver
The function da9063_clear_fault_log() is added to mitigate the case of a
hardware
Pali Rohár, le Tue 09 Jun 2015 15:50:18 +0200, a écrit :
On Tuesday 09 June 2015 15:42:41 Samuel Thibault wrote:
Dmitry Torokhov, le Mon 08 Jun 2015 14:43:07 -0700, a écrit :
If user wants all keyboards to light up CapsLock LED when VT state locks
CtrlL modifier they need to write a udev
On Mon, 2015-06-08 at 17:37 +0300, Irina Tirdea wrote:
Fix sparse warning:
drivers/input/touchscreen/goodix.c:182:26: warning:
Variable length array is used.
Replace the variable length array with fixed length.
Some Goodix devices have maximum 5 touch points, while
others have 10 touch
Hello,
Samuel Thibault, le Thu 05 Feb 2009 12:39:08 +0100, a écrit :
And about the led issue, we need to ask the kernel for an interface to
be able to configure which lock should drive which led.
Dmitry Torokhov, le Mon 08 Jun 2015 14:43:07 -0700, a écrit :
If user wants all keyboards to
On Mon, 2015-06-08 at 17:37 +0300, Irina Tirdea wrote:
Goodix touchscreens export through their registers a Product ID
and Firmware Version. The Product ID is an ASCII encoding of the
product name (e.g.: 911).
Export to sysfs (through the input subsystem) the product id and
firmware version
On Mon, 2015-06-08 at 17:37 +0300, Irina Tirdea wrote:
After power on, it is recommended that the driver resets the device.
The reset procedure timing is described in the datasheet and is used
at device init (before writing device configuration) and
for power management. It is a sequence of
On Tue, Jun 09, 2015 at 04:17:23PM +0200, Samuel Thibault wrote:
Dmitry Torokhov, le Mon 08 Jun 2015 14:43:07 -0700, a écrit :
If user wants all keyboards to light up CapsLock LED when VT state locks
CtrlL modifier they need to write a udev rule or similar to set up
kbd-ctrlllock trigger
Hi Pavel,
On Tue, Jun 09, 2015 at 06:18:18PM +0200, Pavel Machek wrote:
Hi!
I finally was able to spend some time looking over Samuel's patch set
switching input LEDs from custom implementation over to standard LED class
devices and I think this is the shape I am reasonably happy
On Tue, Jun 09, 2015 at 03:27:34PM +0200, Samuel Thibault wrote:
Samuel Thibault, le Tue 09 Jun 2015 15:19:55 +0200, a écrit :
+ [LED_NUML] = { num-lock, VT_TRIGGER(kbd-numlock) },
+ [LED_CAPSL] = { caps-lock, VT_TRIGGER(kbd-capslock) },
+ [LED_SCROLLL] = { scroll-lock,
Dmitry Torokhov, le Tue 09 Jun 2015 09:50:52 -0700, a écrit :
On Tue, Jun 09, 2015 at 03:27:34PM +0200, Samuel Thibault wrote:
Samuel Thibault, le Tue 09 Jun 2015 15:19:55 +0200, a écrit :
+ [LED_NUML] = { num-lock, VT_TRIGGER(kbd-numlock) },
+ [LED_CAPSL] = {
On Tue, Jun 09, 2015 at 12:54:21PM +0200, Pavel Machek wrote:
Hi!
I finally was able to spend some time looking over Samuel's patch set
switching input LEDs from custom implementation over to standard LED class
devices and I think this is the shape I am reasonably happy with. The
Hi!
I finally was able to spend some time looking over Samuel's patch set
switching input LEDs from custom implementation over to standard LED class
devices and I think this is the shape I am reasonably happy with. The
changes:
Thanks!
Please take a look and see if you see any
On Tue, Jun 09, 2015 at 01:26:34PM +0200, Pavel Machek wrote:
On Tue 2015-06-09 13:12:42, Pavel Machek wrote:
On Tue 2015-06-09 12:54:21, Pavel Machek wrote:
Hi!
I finally was able to spend some time looking over Samuel's patch set
switching input LEDs from custom implementation
On Tue, Jun 09, 2015 at 07:25:42AM +0200, Daniel Mack wrote:
Hi Matt,
On 06/09/2015 05:46 AM, Matt Ranostay wrote:
Several cap11xx variants have LEDs that be can be controlled, this
patchset implements this functionality.
Signed-off-by: Matt Ranostay mranos...@gmail.com
---
The IIO subsystem's user-space API is awful, and root only. I said as
much here:
http://thread.gmane.org/gmane.linux.kernel.iio/14421
Just getting started with this idea, and found this which might waylay
some of the pain
https://github.com/analogdevicesinc/libiio
I wrote this for
On Tue, 2015-06-09 at 17:34 +0200, Bastien Nocera wrote:
On Mon, 2015-06-08 at 17:37 +0300, Irina Tirdea wrote:
After power on, it is recommended that the driver resets the
device.
The reset procedure timing is described in the datasheet and is
used
at device init (before writing
On Mon, Jun 8, 2015 at 10:26 PM, Daniel Mack dan...@zonque.org wrote:
On 06/09/2015 05:46 AM, Matt Ranostay wrote:
Several cap11xx variants have LEDs that be can be controlled, this
patchset implements this functionality.
Signed-off-by: Matt Ranostay mranos...@gmail.com
---
On Tue, Jun 09, 2015 at 03:19:55PM +0200, Samuel Thibault wrote:
Hello,
Dmitry Torokhov, le Mon 08 Jun 2015 14:43:08 -0700, a écrit :
1. Instead of making LED class devices part of the input device they are
implemented as an input handler (and thus are completely separate from
input
Dmitry Torokhov, le Tue 09 Jun 2015 09:49:35 -0700, a écrit :
+ [LED_NUML] = { num-lock, VT_TRIGGER(kbd-numlock) },
+ [LED_CAPSL] = { caps-lock, VT_TRIGGER(kbd-capslock) },
+ [LED_SCROLLL] = { scroll-lock, VT_TRIGGER(kbd-scrollock) },
I'd tend to think we'd want to
From: Samuel Thibault samuel.thiba...@ens-lyon.org
This change creates a new input handler called leds that exports LEDs on input
devices as standard LED class devices in sysfs and allows controlling their
ptate via sysfs or via any of the standard LED triggers. This allows to
re-purpose and
On Tue, Jun 9, 2015 at 10:12 AM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Tue, Jun 09, 2015 at 07:25:42AM +0200, Daniel Mack wrote:
Hi Matt,
On 06/09/2015 05:46 AM, Matt Ranostay wrote:
Several cap11xx variants have LEDs that be can be controlled, this
patchset implements this
On Mon, Jun 08, 2015 at 05:37:51PM +0300, Irina Tirdea wrote:
Implement suspend/resume for goodix driver.
This is based on Goodix datasheets for GT911 and GT9271
and on Goodix driver gt9xx.c for Android (publicly available
in Android kernel trees for various devices).
Signed-off-by:
Hi Irina,
On Mon, Jun 08, 2015 at 05:37:50PM +0300, Irina Tirdea wrote:
Goodix devices can be configured by writing custom data to the device at
init. The configuration data is read with request_firmware from
goodix_id_cfg.bin, where id is the product id read from the device
(e.g.:
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive a small tweak for Synaptics PS/2 touchpad driver.
Changelog:
-
Peter Hutterer (1):
Input: synaptics - add min/max quirk for Lenovo S540
Diffstat:
On Mon, Jun 08, 2015 at 05:37:45PM +0300, Irina Tirdea wrote:
Add several enhancements to the Goodix touchscreen driver:
- write configuration data to the device
- power management support
- cleanup and refactoring
I have kept the original patch for ESD (input: goodix: add support
for
On Tue, Jun 09, 2015 at 07:22:31PM +0200, Samuel Thibault wrote:
Dmitry Torokhov, le Tue 09 Jun 2015 09:49:35 -0700, a écrit :
+ [LED_NUML] = { num-lock, VT_TRIGGER(kbd-numlock) },
+ [LED_CAPSL] = { caps-lock, VT_TRIGGER(kbd-capslock) },
+ [LED_SCROLLL] =
Fields like HID_DG_CONTACTCOUNT are outside of the physical collection,
but within the application collection and report ID. Make sure to catch
those fields that are not part of the mt_report_id and return 0 so they
can be processed with the pen. Otherwise, the wrong HID_DG_CONTACTCOUNT
will be
input_mt_init_slots() will do that for us.
Signed-off-by: Dmitry Torokhov dmitry.torok...@gmail.com
---
drivers/input/touchscreen/goodix.c | 4
1 file changed, 4 deletions(-)
diff --git a/drivers/input/touchscreen/goodix.c
b/drivers/input/touchscreen/goodix.c
index 73ade35..b4d12e2 100644
From: Pavel Rojtberg rojtb...@gmail.com
this series is based on the changes discussed in
[PATCH 0/7] Input: xpad: Fix wireless controller connection and leds.
It incorporates the discussed improvements, while leaving the conroversal parts
out.
So only the constantly blinking LED on the Xbox360
From: Pavel Rojtberg rojtb...@gmail.com
the controller only receives commands when its present. So for the
correct LED to be lit the LED command has to be sent on the present
event. move led_no to xpad struct to remember the pad number.
Signed-off-by: Pavel Rojtberg rojtb...@gmail.com
---
From: Pierre-Loup A. Griffais pgriff...@valvesoftware.com
Based on Patch by Pierre-Loup A. Griffais pgriff...@valvesoftware.com:
Add the logic to set the LEDs on XBox Wireless controllers. Command
sequence found by sniffing the Windows data stream when plugging the
device in.
Updated based on
On 06/09/2015 07:12 PM, Dmitry Torokhov wrote:
On Tue, Jun 09, 2015 at 07:25:42AM +0200, Daniel Mack wrote:
Use the .brightness_set_sync callback, so you don't have to dance around
with the workers at all.
Umm, how will it help? You still can't sleep in set_brightness().
On Tue, Jun 9, 2015 at 4:31 PM, Brent Adam brentadam...@gmail.com wrote:
Fields like HID_DG_CONTACTCOUNT are outside of the physical collection,
but within the application collection and report ID. Make sure to catch
those fields that are not part of the mt_report_id and return 0 so they
can
Pali Rohár, le Tue 09 Jun 2015 13:22:21 +0200, a écrit :
On Tuesday 09 June 2015 13:12:42 Pavel Machek wrote:
On Tue 2015-06-09 12:54:21, Pavel Machek wrote:
I did echo kbd-capslock trigger, but still no luck. (That might be
bug in Debian, IIRC?)
I tried rebooting with stock Debian
Pavel Machek, le Tue 09 Jun 2015 12:54:21 +0200, a écrit :
1) input4::caps-lock -- default trigger was not set, so caps lock did
not control the LED. That's bug, right?
I did echo kbd-capslock trigger, but still no luck. (That might be
bug in Debian, IIRC?)
In console-setup, yers.
Samuel
Hello,
Thanks for the modified version. This all seems to be working as
expected with multiple keyboards.
Samuel
--
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
On Wed, Jun 10, 2015 at 02:32:32AM +0200, Samuel Thibault wrote:
Hello,
Thanks for the modified version. This all seems to be working as
expected with multiple keyboards.
Excellent. Let's give Pavel and Pali chance to test it out and let's get
it in 4.2.
Thanks.
--
Dmitry
--
To
On Tuesday 09 June 2015 15:42:41 Samuel Thibault wrote:
Dmitry Torokhov, le Mon 08 Jun 2015 14:43:07 -0700, a écrit :
If user wants all keyboards to light up CapsLock LED when VT state locks
CtrlL modifier they need to write a udev rule or similar to set up
kbd-ctrlllock trigger for all
Hello,
Dmitry Torokhov, le Mon 08 Jun 2015 14:43:08 -0700, a écrit :
1. Instead of making LED class devices part of the input device they are
implemented as an input handler (and thus are completely separate from
input core).
That's nicer indeed. Not defining triggers per LED however does
Dmitry Torokhov, le Mon 08 Jun 2015 14:43:07 -0700, a écrit :
If user wants all keyboards to light up CapsLock LED when VT state locks
CtrlL modifier they need to write a udev rule or similar to set up
kbd-ctrlllock trigger for all appearing input%::capslock LED class
devices.
I guess
Samuel Thibault, le Tue 09 Jun 2015 15:19:55 +0200, a écrit :
+ [LED_NUML] = { num-lock, VT_TRIGGER(kbd-numlock) },
+ [LED_CAPSL] = { caps-lock, VT_TRIGGER(kbd-capslock) },
+ [LED_SCROLLL] = { scroll-lock, VT_TRIGGER(kbd-scrollock) },
I'd tend to think we'd want to
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 si...@mungewell.org
---
drivers/hid/hid-sony.c | 15 +++
1 file changed, 11
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 si...@mungewell.org
---
drivers/hid/hid-sony.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git
Split quirk for PS Move Controller as it has to be treated differently
when connected via BT.
Signed-off-by: Simon Wood si...@mungewell.org
---
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
53 matches
Mail list logo
