diff options
| author | John Schock <joschock@microsoft.com> | 2023-05-26 16:50:41 -0700 |
|---|---|---|
| committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2024-08-06 03:24:40 +0000 |
| commit | 472be4d139b26c50949cf30eeb47640810e5ef2c (patch) | |
| tree | 583a73fee43bf5ade877171c99a49eec8d661dcc /CryptoPkg | |
| parent | 1b37b3659b5098f764dee5b893e4eb174949f40a (diff) | |
| download | edk2-472be4d139b26c50949cf30eeb47640810e5ef2c.tar.gz | |
MdeModulePkg ConPlatform: Support IAD-style USB input devices.
Some multi-function input devices (e.g. combo keyboard and mouse)
present as IAD-style devices (https://www.usb.org/defined-class-codes,
https://learn.microsoft.com/en-us/windows-hardware/drivers/usbcon/usb-interface-association-descriptor).
Historically, multi-function devices would report a DeviceClass of 0,
indicating that interface matching should be done on the interface
descriptor rather than the global device descriptor.
IAD-style devices us DeviceClass of 0xEF, so they don't match
MatchUsbClass() for keyboard (DeviceClass=3, SubClass=1, Proto=1). If
they are treated as if they had a DeviceClass of zero, which is more
traditional for legacy multi-function devices, then the interface
descriptors are used instead and these types of devices will "just work"
without needing to add a custom USB device path to ConIn.
Signed-off-by: Aaron Pop <aaronpop@microsoft.com>
Diffstat (limited to 'CryptoPkg')
0 files changed, 0 insertions, 0 deletions