HID: add support for Sony RF receiver with USB product id 0x0374
PATCH 1/1 HID: add support for Sony RF receiver with USB product id 0x0374
Some Vaio desktop computers, among them the VGC-LN51JGB multimedia PC, have a RF receiver, multi-interface USB device 054c:0374, that is used to connect a wireless keyboard and a wireless mouse.
The keyboard works flawlessly, but the mouse (VGP-WMS3 in my case) does not seem to be generating any pointer events. The problem is that the mouse pointer is wrongly declared as a constant non-data variable in the report descriptor (see lsusb and usbhid-dump output below), with the consenquence that it is ignored by the HID code.
Add this device to the have-special-driver list and fix up the report descriptor in the Sony-specific driver which happens to already have a fixup for a similar firmware bug.
# lsusb -vd 054C:0374
Bus 003 Device 002: ID 054c:0374 Sony Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x054c Sony Corp.
idProduct 0x0374
iSerial 0
[...]
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 2 Mouse
iInterface 2 RF Receiver
[...]
Report Descriptor: (length is 100)
Item(Global): Usage Page, data= [ 0x01 ] 1
Generic Desktop Controls
Item(Local ): Usage, data= [ 0x30 ] 48
Direction-X
Item(Local ): Usage, data= [ 0x31 ] 49
Direction-Y
Item(Global): Report Count, data= [ 0x02 ] 2
Item(Global): Report Size, data= [ 0x08 ] 8
Item(Global): Logical Minimum, data= [ 0x81 ] 129
Item(Global): Logical Maximum, data= [ 0x7f ] 127
Item(Main ): Input, data= [ 0x07 ] 7
Constant Variable Relative No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield# sudo usbhid-dump
003:002:001:DESCRIPTOR 1357910009.758544
05 01 09 02 A1 01 05 01 09 02 A1 02 85 01 09 01
A1 00 05 09 19 01 29 05 95 05 75 01 15 00 25 01
81 02 75 03 95 01 81 01 05 01 09 30 09 31 95 02
75 08 15 81 25 7F 81 07 A1 02 85 01 09 38 35 00
45 00 15 81 25 7F 95 01 75 08 81 06 C0 A1 02 85
01 05 0C 15 81 25 7F 95 01 75 08 0A 38 02 81 06
C0 C0 C0 C0
---
drivers/hid/hid-core.c +1 -0
@@ -1697,6 +1697,7 @@ static const struct hid_device_id hid_ha { HID_USB_DEVICE(USB_VENDOR_ID_SONY, USB_DEVICE_ID_SONY_NAVIGATION_CONTROLLER) }, { HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_SONY, USB_DEVICE_ID_SONY_PS3_CONTROLLER) }, { HID_USB_DEVICE(USB_VENDOR_ID_SONY, USB_DEVICE_ID_SONY_VAIO_VGX_MOUSE) }, + { HID_USB_DEVICE(USB_VENDOR_ID_SONY, USB_DEVICE_ID_SONY_VAIO_VGP_MOUSE) }, { HID_USB_DEVICE(USB_VENDOR_ID_SUNPLUS, USB_DEVICE_ID_SUNPLUS_WDESKTOP) }, { HID_USB_DEVICE(USB_VENDOR_ID_THRUSTMASTER, 0xb300) }, { HID_USB_DEVICE(USB_VENDOR_ID_THRUSTMASTER, 0xb304) },
drivers/hid/hid-ids.h +1 -0
@@ -706,6 +706,7 @@#define USB_VENDOR_ID_SONY 0x054c#define USB_DEVICE_ID_SONY_VAIO_VGX_MOUSE 0x024b +#define USB_DEVICE_ID_SONY_VAIO_VGP_MOUSE 0x0374#define USB_DEVICE_ID_SONY_PS3_BDREMOTE 0x0306#define USB_DEVICE_ID_SONY_PS3_CONTROLLER 0x0268#define USB_DEVICE_ID_SONY_NAVIGATION_CONTROLLER 0x042f
drivers/hid/hid-sony.c +8 -4
@@ -44,19 +44,21 @@ static __u8 *sony_report_fixup(struct histruct sony_sc *sc =hid_get_drvdata (hdev);if ((sc->quirks &VAIO_RDESC_CONSTANT ) && - *rsize >=56 && rdesc[54 ] ==0x81 && rdesc[55 ] ==0x07 ) { -hid_info (hdev,"Fixing up Sony Vaio VGX report descriptor\n" ); + *rsize >=56 && rdesc[54 ] ==0x81 && rdesc[55 ] ==0x07 ) { +hid_info (hdev, +"Fixing up Sony RF Receiver report descriptor\n" ); rdesc[55 ] =0x06 ; }/* The HID descriptor exposed over BT has a trailing zero byte */ if ((((sc->quirks &SIXAXIS_CONTROLLER_USB ) && *rsize ==148 ) || - ((sc->quirks &SIXAXIS_CONTROLLER_BT ) && *rsize ==149 )) && - rdesc[83 ] ==0x75 ) { + ((sc->quirks &SIXAXIS_CONTROLLER_BT ) && *rsize ==149 )) && + rdesc[83 ] ==0x75 ) {hid_info (hdev,"Fixing up Sony Sixaxis report descriptor\n" );memcpy ((void *)&rdesc[83 ], (void *)&sixaxis_rdesc_fixup,sizeof (sixaxis_rdesc_fixup)); } +return rdesc; }
@@ -217,6 +219,8 @@ static const struct hid_device_id sony_d .driver_data = SIXAXIS_CONTROLLER_BT }, { HID_USB_DEVICE(USB_VENDOR_ID_SONY, USB_DEVICE_ID_SONY_VAIO_VGX_MOUSE), .driver_data = VAIO_RDESC_CONSTANT }, + { HID_USB_DEVICE(USB_VENDOR_ID_SONY, USB_DEVICE_ID_SONY_VAIO_VGP_MOUSE), + .driver_data = VAIO_RDESC_CONSTANT }, { } };MODULE_DEVICE_TABLE (hid, sony_devices);
On Tue, 15 Jan 2013 12:43:48 +0900
Fernando Luis Vázquez Cao <[email protected]> wrote:
Hi Fernando,
Quoted 8 lines
Some Vaio desktop computers, among them the VGC-LN51JGB multimedia PC, have a RF receiver, multi-interface USB device 054c:0374, that is used to connect a wireless keyboard and a wireless mouse.
The keyboard works flawlessly, but the mouse (VGP-WMS3 in my case) does not seem to be generating any pointer events. The problem is that the mouse pointer is wrongly declared as a constant non-data variable in the report descriptor (see lsusb and usbhid-dump output below), with the consenquence that it is
typo: consequence
Quoted 89 lines
ignored by the HID code.
Add this device to the have-special-driver list and fix up the report descriptor in the Sony-specific driver which happens to already have a fixup for a similar firmware bug.
# lsusb -vd 054C:0374 Bus 003 Device 002: ID 054c:0374 Sony Corp. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x054c Sony Corp. idProduct 0x0374 iSerial 0 [...] Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 2 RF Receiver [...] Report Descriptor: (length is 100) Item(Global): Usage Page, data= [ 0x01 ] 1 Generic Desktop Controls Item(Local ): Usage, data= [ 0x30 ] 48 Direction-X Item(Local ): Usage, data= [ 0x31 ] 49 Direction-Y Item(Global): Report Count, data= [ 0x02 ] 2 Item(Global): Report Size, data= [ 0x08 ] 8 Item(Global): Logical Minimum, data= [ 0x81 ] 129 Item(Global): Logical Maximum, data= [ 0x7f ] 127 Item(Main ): Input, data= [ 0x07 ] 7 Constant Variable Relative No_Wrap Linear Preferred_State No_Null_Position Non_Volatile Bitfield# sudo usbhid-dump003:002:001:DESCRIPTOR 1357910009.758544
05 01 09 02 A1 01 05 01 09 02 A1 02 85 01 09 01
A1 00 05 09 19 01 29 05 95 05 75 01 15 00 25 01
81 02 75 03 95 01 81 01 05 01 09 30 09 31 95 02
75 08 15 81 25 7F 81 07 A1 02 85 01 09 38 35 00
45 00 15 81 25 7F 95 01 75 08 81 06 C0 A1 02 85
01 05 0C 15 81 25 7F 95 01 75 08 0A 38 02 81 06
C0 C0 C0 C0Signed-off-by Fernando Luis Vazquez Cao <[email protected]>---
diff -urNp
linux-3.8-rc3-orig/drivers/hid/hid-core.clinux-3.8-rc3/drivers/hid/hid-core.cdrivers/hid/hid-core.c +1
-0@@ -1697,6 +1697,7 @@ static const struct hid_device_id hid_ha { HID_USB_DEVICE(USB_VENDOR_ID_SONY, USB_DEVICE_ID_SONY_NAVIGATION_CONTROLLER) }, { HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_SONY, USB_DEVICE_ID_SONY_PS3_CONTROLLER) }, { HID_USB_DEVICE(USB_VENDOR_ID_SONY, USB_DEVICE_ID_SONY_VAIO_VGX_MOUSE) }, + { HID_USB_DEVICE(USB_VENDOR_ID_SONY, USB_DEVICE_ID_SONY_VAIO_VGP_MOUSE) }, { HID_USB_DEVICE(USB_VENDOR_ID_SUNPLUS, USB_DEVICE_ID_SUNPLUS_WDESKTOP) }, { HID_USB_DEVICE(USB_VENDOR_ID_THRUSTMASTER, 0xb300) }, { HID_USB_DEVICE(USB_VENDOR_ID_THRUSTMASTER, 0xb304) },diff -urNp
linux-3.8-rc3-orig/drivers/hid/hid-ids.hlinux-3.8-rc3/drivers/hid/hid-ids.hdrivers/hid/hid-ids.h +1
-0@@ -706,6 +706,7 @@#define USB_VENDOR_ID_SONY 0x054c#define USB_DEVICE_ID_SONY_VAIO_VGX_MOUSE 0x024b +#define USB_DEVICE_ID_SONY_VAIO_VGP_MOUSE 0x0374#define USB_DEVICE_ID_SONY_PS3_BDREMOTE 0x0306#define USB_DEVICE_ID_SONY_PS3_CONTROLLER 0x0268#define USB_DEVICE_ID_SONY_NAVIGATION_CONTROLLER 0x042fdiff -urNp
linux-3.8-rc3-orig/drivers/hid/hid-sony.clinux-3.8-rc3/drivers/hid/hid-sony.c
drivers/hid/hid-sony.c static __u8 *sony_report_fixup(struct hi · line 49
Quoted 8 lines
drivers/hid/hid-sony.c +3
-2@@ -44,19 +44,21 @@ static __u8 *sony_report_fixup(struct histruct sony_sc *sc =hid_get_drvdata (hdev);if ((sc->quirks &VAIO_RDESC_CONSTANT ) && - *rsize >=56 && rdesc[54 ] ==0x81 && rdesc[55 ] ==0x07 ) { -hid_info (hdev,"Fixing up Sony Vaio VGX report descriptor\n" ); + *rsize >=56 && rdesc[54 ] ==0x81 && rdesc[55 ] ==0x07 ) { +hid_info (hdev, +"Fixing up Sony RF Receiver report descriptor\n" );
Changing the message does make sense, but try to avoid mixing functional changes with style changes (I am referring to the change of indentation here).
If you _really_ want to change the style send a separate patch stating clearly in the commit message that there are no functionality changes.
This makes the review easier for both kind of patches.
drivers/hid/hid-sony.c static __u8 *sony_report_fixup(struct hi · line 56
Quoted 9 lines
drivers/hid/hid-sony.c +2
-2rdesc[55 ] =0x06 ; }/* The HID descriptor exposed over BT has a trailing zero byte */ if ((((sc->quirks &SIXAXIS_CONTROLLER_USB ) && *rsize ==148 ) || - ((sc->quirks &SIXAXIS_CONTROLLER_BT ) && *rsize ==149 )) && - rdesc[83 ] ==0x75 ) { + ((sc->quirks &SIXAXIS_CONTROLLER_BT ) && *rsize ==149 )) && + rdesc[83 ] ==0x75 ) {
Ditto, style changes.
drivers/hid/hid-sony.c static __u8 *sony_report_fixup(struct hi · line 61
Quoted 5 lines
drivers/hid/hid-sony.c +1
-0hid_info (hdev,"Fixing up Sony Sixaxis report descriptor\n" );memcpy ((void *)&rdesc[83 ], (void *)&sixaxis_rdesc_fixup,sizeof (sixaxis_rdesc_fixup)); } +
Ditto.
Quoted 6 lines
drivers/hid/hid-sony.c +0
-0return rdesc; }
drivers/hid/hid-sony.c static const struct hid_device_id sony_d · line 226
Quoted 8 lines
drivers/hid/hid-sony.c +2
-0@@ -217,6 +219,8 @@ static const struct hid_device_id sony_d .driver_data = SIXAXIS_CONTROLLER_BT }, { HID_USB_DEVICE(USB_VENDOR_ID_SONY, USB_DEVICE_ID_SONY_VAIO_VGX_MOUSE), .driver_data = VAIO_RDESC_CONSTANT }, + { HID_USB_DEVICE(USB_VENDOR_ID_SONY, USB_DEVICE_ID_SONY_VAIO_VGP_MOUSE), + .driver_data = VAIO_RDESC_CONSTANT }, { } };MODULE_DEVICE_TABLE (hid, sony_devices);
Thanks,
Antonio
Signature · 10 lines
Antonio Ospite http://ao2.it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing? -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Antonio,
Quoted 7 lines · Antonio Ospite
Quoted 6 lines · On Tue, 15 Jan 2013 12:43:48 +0900 Fernando Luis Vázquez Cao…
diff -urNp
linux-3.8-rc3-orig/drivers/hid/hid-sony.clinux-3.8-rc3/drivers/hid/hid-sony.cdrivers/hid/hid-sony.c +0
-0@@ -44,19 +44,21 @@ static __u8 *sony_report_fixup(struct histruct sony_sc *sc =hid_get_drvdata (hdev);
Quoted 9 lines
drivers/hid/hid-sony.c static __u8 *sony_report_fixup(struct hi · line 49
Quoted 6 lines
drivers/hid/hid-sony.c +3
-2if ((sc->quirks &VAIO_RDESC_CONSTANT ) && - *rsize >=56 && rdesc[54 ] ==0x81 && rdesc[55 ] ==0x07 ) { -hid_info (hdev,"Fixing up Sony Vaio VGX report descriptor\n" ); + *rsize >=56 && rdesc[54 ] ==0x81 && rdesc[55 ] ==0x07 ) { +hid_info (hdev, +"Fixing up Sony RF Receiver report descriptor\n" );Changing the message does make sense, but try to avoid mixing functional changes with style changes (I am referring to the change of indentation here).
Oops, that was unintended. I will be replying to this email with an updated version.
Thanks,
Fernando
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
PATCH v2 1/1 HID: add support for Sony RF receiver with USB product id 0x0374
Some Vaio desktop computers, among them the VGC-LN51JGB multimedia PC, have a RF receiver, multi-interface USB device 054c:0374, that is used to connect a wireless keyboard and a wireless mouse.
The keyboard works flawlessly, but the mouse (VGP-WMS3 in my case) does not seem to be generating any pointer events. The problem is that the mouse pointer is wrongly declared as a constant non-data variable in the report descriptor (see lsusb and usbhid-dump output below), with the consequence that it is ignored by the HID code.
Add this device to the have-special-driver list and fix up the report descriptor in the Sony-specific driver which happens to already have a fixup for a similar firmware bug.
# lsusb -vd 054C:0374
Bus 003 Device 002: ID 054c:0374 Sony Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x054c Sony Corp.
idProduct 0x0374
iSerial 0
[...]
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 2 Mouse
iInterface 2 RF Receiver
[...]
Report Descriptor: (length is 100)
[...]
Item(Global): Usage Page, data= [ 0x01 ] 1
Generic Desktop Controls
Item(Local ): Usage, data= [ 0x30 ] 48
Direction-X
Item(Local ): Usage, data= [ 0x31 ] 49
Direction-Y
Item(Global): Report Count, data= [ 0x02 ] 2
Item(Global): Report Size, data= [ 0x08 ] 8
Item(Global): Logical Minimum, data= [ 0x81 ] 129
Item(Global): Logical Maximum, data= [ 0x7f ] 127
Item(Main ): Input, data= [ 0x07 ] 7
Constant Variable Relative No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield# usbhid-dump 003:002:001:DESCRIPTOR 1357910009.758544 05 01 09 02 A1 01 05 01 09 02 A1 02 85 01 09 01 A1 00 05 09 19 01 29 05 95 05 75 01 15 00 25 01 81 02 75 03 95 01 81 01 05 01 09 30 09 31 95 02 75 08 15 81 25 7F 81 07 A1 02 85 01 09 38 35 00 45 00 15 81 25 7F 95 01 75 08 81 06 C0 A1 02 85 01 05 0C 15 81 25 7F 95 01 75 08 0A 38 02 81 06 C0 C0 C0 C0
---
drivers/hid/hid-core.c +1 -0
@@ -1697,6 +1697,7 @@ static const struct hid_device_id hid_ha { HID_USB_DEVICE(USB_VENDOR_ID_SONY, USB_DEVICE_ID_SONY_NAVIGATION_CONTROLLER) }, { HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_SONY, USB_DEVICE_ID_SONY_PS3_CONTROLLER) }, { HID_USB_DEVICE(USB_VENDOR_ID_SONY, USB_DEVICE_ID_SONY_VAIO_VGX_MOUSE) }, + { HID_USB_DEVICE(USB_VENDOR_ID_SONY, USB_DEVICE_ID_SONY_VAIO_VGP_MOUSE) }, { HID_USB_DEVICE(USB_VENDOR_ID_SUNPLUS, USB_DEVICE_ID_SUNPLUS_WDESKTOP) }, { HID_USB_DEVICE(USB_VENDOR_ID_THRUSTMASTER, 0xb300) }, { HID_USB_DEVICE(USB_VENDOR_ID_THRUSTMASTER, 0xb304) },
drivers/hid/hid-ids.h +1 -0
@@ -706,6 +706,7 @@#define USB_VENDOR_ID_SONY 0x054c#define USB_DEVICE_ID_SONY_VAIO_VGX_MOUSE 0x024b +#define USB_DEVICE_ID_SONY_VAIO_VGP_MOUSE 0x0374#define USB_DEVICE_ID_SONY_PS3_BDREMOTE 0x0306#define USB_DEVICE_ID_SONY_PS3_CONTROLLER 0x0268#define USB_DEVICE_ID_SONY_NAVIGATION_CONTROLLER 0x042f
drivers/hid/hid-sony.c +3 -1
@@ -45,7 +45,7 @@ static __u8 *sony_report_fixup(struct hiif ((sc->quirks &VAIO_RDESC_CONSTANT ) && *rsize >=56 && rdesc[54 ] ==0x81 && rdesc[55 ] ==0x07 ) { -hid_info (hdev,"Fixing up Sony Vaio VGX report descriptor\n" ); +hid_info (hdev,"Fixing up Sony RF Receiver report descriptor\n" ); rdesc[55 ] =0x06 ; }
@@ -217,6 +217,8 @@ static const struct hid_device_id sony_d .driver_data = SIXAXIS_CONTROLLER_BT }, { HID_USB_DEVICE(USB_VENDOR_ID_SONY, USB_DEVICE_ID_SONY_VAIO_VGX_MOUSE), .driver_data = VAIO_RDESC_CONSTANT }, + { HID_USB_DEVICE(USB_VENDOR_ID_SONY, USB_DEVICE_ID_SONY_VAIO_VGP_MOUSE), + .driver_data = VAIO_RDESC_CONSTANT }, { } };MODULE_DEVICE_TABLE (hid, sony_devices);
Jiri Kosina
AppliedQuoted 10 lines · Fernando Luis Vázquez Cao
Some Vaio desktop computers, among them the VGC-LN51JGB multimedia PC, have a RF receiver, multi-interface USB device 054c:0374, that is used to connect a wireless keyboard and a wireless mouse.
The keyboard works flawlessly, but the mouse (VGP-WMS3 in my case) does not seem to be generating any pointer events. The problem is that the mouse pointer is wrongly declared as a constant non-data variable in the report descriptor (see lsusb and usbhid-dump output below), with the consequence that it is ignored by the HID code.
Quoted 3 lines
Add this device to the have-special-driver list and fix up the report descriptor in the Sony-specific driver which happens to already have a fixup for a similar firmware bug.
Applied, thanks.
Signature · 2 lines
Jiri Kosina SUSE Labs
Hi Jiri,
Quoted 12 lines · Jiri Kosina
Quoted 10 lines · Fernando Luis Vázquez Cao
Some Vaio desktop computers, among them the VGC-LN51JGB multimedia PC, have a RF receiver, multi-interface USB device 054c:0374, that is used to connect a wireless keyboard and a wireless mouse.
The keyboard works flawlessly, but the mouse (VGP-WMS3 in my case) does not seem to be generating any pointer events. The problem is that the mouse pointer is wrongly declared as a constant non-data variable in the report descriptor (see lsusb and usbhid-dump output below), with the consequence that it is ignored by the HID code.
Quoted 4 lines
Quoted 3 lines
Add this device to the have-special-driver list and fix up the report descriptor in the Sony-specific driver which happens to already have a fixup for a similar firmware bug.
Applied, thanks.
Thank you.
I noticed that the patch was tagged "for-3.9". Does this mean that it is too late to get it merged during the current release cycle?
If possible, I would like to get it backported to 3.7-stable (and possibly 3.2 stable), since without it a whole family of Sony desktop computers is unusable under Linux out of the box. Should I do it myself or do you have a process in place for HID stable patches?
Regards,
Fernando
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 3 lines · Fernando Luis Vazquez Cao
I noticed that the patch was tagged "for-3.9". Does this mean that it is too late to get it merged during the current release cycle?
I currently don't have anything queued for 3.8, and this particular patch doesn't justify a separate pull request.
Once it's in Linus' tree, it can be easily pushed out to all existing -stable branches (including 3.8-stable, once it's created).
If I am gfoing to be sending pull request for 3.8 to Linus still due to some important bugfix, I will be including this.
Quoted 4 lines
If possible, I would like to get it backported to 3.7-stable (and possibly 3.2 stable), since without it a whole family of Sony desktop computers is unusable under Linux out of the box. Should I do it myself or do you have a process in place for HID stable patches?
If the patch had
in it, it'd be picked for -stable queue automatically. Otherwise, anyone is free to take it once it's in Linus' tree and sent to to [email protected] for inclusion.
Hope this helps,
Signature · 2 lines
Jiri Kosina SUSE Labs
Quoted 6 lines · Jiri Kosina
Quoted 3 lines · Fernando Luis Vazquez Cao
I noticed that the patch was tagged "for-3.9". Does this mean that it is too late to get it merged during the current release cycle?
Quoted 8 lines
I currently don't have anything queued for 3.8, and this particular patch doesn't justify a separate pull request.
Once it's in Linus' tree, it can be easily pushed out to all existing -stable branches (including 3.8-stable, once it's created).
If I am gfoing to be sending pull request for 3.8 to Linus still due to some important bugfix, I will be including this.
Ok, thank you for the explanation. I really appreciate it.
Quoted 10 lines
Quoted 4 lines
If possible, I would like to get it backported to 3.7-stable (and possibly 3.2 stable), since without it a whole family of Sony desktop computers is unusable under Linux out of the box. Should I do it myself or do you have a process in place for HID stable patches?
If the patch had
Cc: [email protected]in it, it'd be picked for -stable queue automatically.
I considered doing that but I thought and upstream commit ID was needed.
Quoted 2 lines
Otherwise, anyone is free to take it once it's in Linus' tree and sent to to [email protected] for inclusion.
So it is the standard procedure. I just wanted to make sure whether you wanted to have all the -stable patches funnelled through you. I will send the patch to -stable directly and Cc you as soon as it makes it into Linus' tree.
By the way, I will be replying to this email with a follow-up patch that I forgot to send the last time around. It is just documentation for the quirk.
Thanks,
Fernando
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
HID: clean up quirk for Sony RF receivers
Document what the fix-up is does and make it more robust by ensuring that it is only applied to the USB interface that corresponds to the mouse (sony_report_fixup() is called once per interface during probing).
---
drivers/hid/hid-sony.c +12 -2
@@ -43,9 +43,19 @@ static __u8 *sony_report_fixup(struct hi {struct sony_sc *sc =hid_get_drvdata (hdev); -if ((sc->quirks &VAIO_RDESC_CONSTANT ) && - *rsize >=56 && rdesc[54 ] ==0x81 && rdesc[55 ] ==0x07 ) { +/* +* Some Sony RF receivers wrongly declare the mouse pointer as a +* a constant non-data variable. +*/ +if ((sc->quirks &VAIO_RDESC_CONSTANT ) && *rsize >=56 && +/* usage page: generic desktop controls */ +/* rdesc[0] == 0x05 && rdesc[1] == 0x01 && */ +/* usage: mouse */ + rdesc[2 ] ==0x09 && rdesc[3 ] ==0x02 && +/* input (usage page for x,y axes): constant, variable, relative */ + rdesc[54 ] ==0x81 && rdesc[55 ] ==0x07 ) {hid_info (hdev,"Fixing up Sony RF Receiver report descriptor\n" ); +/* input: data, variable, relative */ rdesc[55 ] =0x06 ; }
Jiri Kosina
AppliedRe: HID: clean up quirk for Sony RF receivers
Quoted 3 lines · Fernando Luis Vázquez Cao
Document what the fix-up is does and make it more robust by ensuring that it is only applied to the USB interface that corresponds to the mouse (
sony_report_fixup()is called once per interface during probing).
Applied.
Signature · 6 lines
Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 5 lines · Fernando Luis Vazquez Cao
Quoted 5 lines
Quoted 4 lines
If possible, I would like to get it backported to 3.7-stable (and possibly 3.2 stable), since without it a whole family of Sony desktop computers is unusable under Linux out of the box. Should I do it myself or do you have a process in place for HID stable patches?
Quoted 8 lines
Quoted 5 lines
If the patch had
in it, it'd be picked for -stable queue automatically.
I considered doing that but I thought and upstream commit ID was needed.
Yes, that's necessary in case you are cherry-picking a commit already present in Linus' tree that doesn't have explicit "Cc:
[email protected]". Otherwise, -stable tree maintainer is automatically picking up commits that appear in Linus tree with this tag.
Quoted 6 lines
Quoted 3 lines
Otherwise, anyone is free to take it once it's in Linus' tree and sent to to [email protected] for inclusion.
So it is the standard procedure. I just wanted to make sure whether you wanted to have all the -stable patches funnelled through you.
It's not strictly necessary. I get copied on them when they are queued in -stable queue anyway.
Quoted 3 lines
By the way, I will be replying to this email with a follow-up patch that I forgot to send the last time around. It is just documentation for the quirk.
Ok, thanks.
Signature · 2 lines
Jiri Kosina SUSE Labs
Hi Jiri,
Quoted 12 lines · Jiri Kosina
Quoted 10 lines · Fernando Luis Vázquez Cao
Some Vaio desktop computers, among them the VGC-LN51JGB multimedia PC, have a RF receiver, multi-interface USB device 054c:0374, that is used to connect a wireless keyboard and a wireless mouse.
The keyboard works flawlessly, but the mouse (VGP-WMS3 in my case) does not seem to be generating any pointer events. The problem is that the mouse pointer is wrongly declared as a constant non-data variable in the report descriptor (see lsusb and usbhid-dump output below), with the consequence that it is ignored by the HID code.
Quoted 5 lines
Quoted 3 lines
Add this device to the have-special-driver list and fix up the report descriptor in the Sony-specific driver which happens to already have a fixup for a similar firmware bug.
Applied, thanks.
It looks like after the merge of the the sony and steelseries branches the hid core hunk was left out, which means that this fix-up is never applied.
I will be replying to this email with a fix.
Thanks,
Fernando
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
PATCH 1/1 HID: fix botched tree merge that disabled fix-up for certain Sony RF receivers
It looks like the manual merge 0d69a3c731e120b05b7da9fb976830475a3fbc01 ("Merge branches 'for-3.9/sony' and 'for-3.9/steelseries' into for-linus") accidentally removed Sony RF receiver with USB product id 0x0374 from the "have special driver" list, effectively nullifying a464918419f94a0043d2f549d6defb4c3f69f68a ("HID: add support for Sony RF receiver with USB product id 0x0374"). Add the device back to the list.
---
drivers/hid/hid-core.c +1 -0
@@ -1702,6 +1702,7 @@ static const struct hid_device_id hid_ha { HID_USB_DEVICE(USB_VENDOR_ID_SONY, USB_DEVICE_ID_SONY_NAVIGATION_CONTROLLER) }, { HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_SONY, USB_DEVICE_ID_SONY_PS3_CONTROLLER) }, { HID_USB_DEVICE(USB_VENDOR_ID_SONY, USB_DEVICE_ID_SONY_VAIO_VGX_MOUSE) }, + { HID_USB_DEVICE(USB_VENDOR_ID_SONY, USB_DEVICE_ID_SONY_VAIO_VGP_MOUSE) }, { HID_USB_DEVICE(USB_VENDOR_ID_STEELSERIES, USB_DEVICE_ID_STEELSERIES_SRWS1) }, { HID_USB_DEVICE(USB_VENDOR_ID_SUNPLUS, USB_DEVICE_ID_SUNPLUS_WDESKTOP) }, { HID_USB_DEVICE(USB_VENDOR_ID_THINGM, USB_DEVICE_ID_BLINK1) },
Re: [PATCH] HID: fix botched tree merge that disabled fix-up for certain Sony RF receivers
Quoted 15 lines · Fernando Luis Vázquez Cao
It looks like the manual merge
0d69a3c731e120b05b7da9fb976830475a3fbc01("Merge branches 'for-3.9/sony' and 'for-3.9/steelseries' into for-linus") accidentally removed Sony RF receiver with USB product id0x0374from the "have special driver" list, effectively nullifyinga464918419f94a0043d2f549d6defb4c3f69f68a("HID: add support for Sony RF receiver with USB product id0x0374"). Add the device back to the list.Signed-off-by Fernando Luis Vazquez Cao <[email protected]>---
diff -urNp
linux-3.9/drivers/hid/hid-core.clinux-3.9-fix/drivers/hid/hid-core.c
drivers/hid/hid-core.c static const struct hid_device_id hid_ha · line 1708
Quoted 7 lines
drivers/hid/hid-core.c +1
-0@@ -1702,6 +1702,7 @@ static const struct hid_device_id hid_ha { HID_USB_DEVICE(USB_VENDOR_ID_SONY, USB_DEVICE_ID_SONY_NAVIGATION_CONTROLLER) }, { HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_SONY, USB_DEVICE_ID_SONY_PS3_CONTROLLER) }, { HID_USB_DEVICE(USB_VENDOR_ID_SONY, USB_DEVICE_ID_SONY_VAIO_VGX_MOUSE) }, + { HID_USB_DEVICE(USB_VENDOR_ID_SONY, USB_DEVICE_ID_SONY_VAIO_VGP_MOUSE) }, { HID_USB_DEVICE(USB_VENDOR_ID_STEELSERIES, USB_DEVICE_ID_STEELSERIES_SRWS1) }, { HID_USB_DEVICE(USB_VENDOR_ID_SUNPLUS, USB_DEVICE_ID_SUNPLUS_WDESKTOP) }, { HID_USB_DEVICE(USB_VENDOR_ID_THINGM, USB_DEVICE_ID_BLINK1) },
Thanks a lot for noticing. Applied.
Signature · 6 lines
Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html