From the rdesc, the raw report data (01 00 00) does not match may valid HID_USAGE_PAGE/HID_USAGE. That's why they are not processed.
From the raw data by the command cat /dev/usb/hiddev0 | hexdump -v -e '/1 "%02X\n"', it seems that the data is MicroSoft specific usage page and the usage is 0xDC for mute key and 0xDB for Fn+F10.
Can you give me the raw data in parallel (cat /dev/usb/hidddev0 and the /sys/kernel/debug/hid/0003:17ef:60a9.0003/events)? I want to identify the code for HID_USAGE_PAGE/HID_USAGE when Fn+F4 and Fn+F10. When that's confirmed, I'll send you a customized kernel for verification and trying to fix it in our release.
Thanks for the information.
From the rdesc, the raw report data (01 00 00) does not match may valid HID_USAGE_ PAGE/HID_ USAGE. That's why they are not processed.
From the raw data by the command cat /dev/usb/hiddev0 | hexdump -v -e '/1 "%02X\n"', it seems that the data is MicroSoft specific usage page and the usage is 0xDC for mute key and 0xDB for Fn+F10.
Can you give me the raw data in parallel (cat /dev/usb/hidddev0 and the /sys/kernel/ debug/hid/ 0003:17ef: 60a9.0003/ events) ? I want to identify the code for HID_USAGE_ PAGE/HID_ USAGE when Fn+F4 and Fn+F10. When that's confirmed, I'll send you a customized kernel for verification and trying to fix it in our release.