TUH not receiving Consumer Control reports? #3176
Replies: 1 comment
-
Calling |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have a TinyUSB dual host/device running on a Raspberry Pi Pico. The host receives input from a keyboard that poses as multiple interfaces, and the device prints out the reports called from
tuh_hid_report_received_cb
to a TUD CDC endpoint, among other things.I can see that the TinyUSB host has all three interfaces properly mounted, and I can see it receiving inputs on all 3 interfaces by reading the output on the device-side CDC. However, on interface 1, there should be HID reports received on report ID 3 (consumer control - should be volume controls) and report ID 5 (vendor defined - I don't think it's relevant but it's key up/down messages), but I am only seeing them received by
tuh_hid_report_received_cb
for report ID 5.These are the inputs that I can see are sent when the keyboard is plugged in directly to a PC by looking at
/sys/kernel/debug/hid/.../events
.And this is the relevant code within
tuh_hid_report_received_cb
that is outputting messages to the TUD CDC.As shown below,
tuh_hid_report_received_cb
is getting called on reports from the keyboard on the same interface, but only for report ID=5.The reports on the same interface for report ID=3 do not seem to be calling
tuh_hid_report_received_cb
when connected to the Raspberry Pi Pico instead of directly into the PC. What am I doing wrong/is this intended behavior?Below is the HID report descriptor on the interface in question (interface 1)
Beta Was this translation helpful? Give feedback.
All reactions