Page MenuHomeFreeBSD

usb_quirk: implement bad remote wakeup and add ASM1074 SS
Needs ReviewPublic

Authored by minsoochoo0122_proton.me on Thu, Jul 2, 12:08 AM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Jul 10, 2:57 PM
Unknown Object (File)
Fri, Jul 10, 2:46 PM
Unknown Object (File)
Fri, Jul 10, 2:08 AM
Unknown Object (File)
Thu, Jul 9, 4:26 PM
Unknown Object (File)
Thu, Jul 9, 4:20 PM
Unknown Object (File)
Thu, Jul 9, 1:29 PM
Unknown Object (File)
Thu, Jul 9, 9:17 AM
Unknown Object (File)
Wed, Jul 8, 6:07 AM

Details

Reviewers
None
Group Reviewers
USB
Summary

Some devices (e.g. ASM1074) reports remote wakeup working, but the
functionality is not implemented on the controller. As a result,
they spam dmesg with {resume,suspend}_peer error message.

PR: 292613

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 74474
Build 71357: arc lint + arc unit

Event Timeline

sys/dev/usb/usb_device.h
97–98

It's my first time to usb code, and I'm not sure how to implement this using existing remote_wakeup as usb_dev_{resume,suspend}_peer() don't seem to use it.

sys/dev/usb/usb_device.h
97–98

It's my first time to usb code, and I'm not sure how to implement this using existing remote_wakeup as usb_dev_{resume,suspend}_peer() don't seem to use it.

I think we can test the quirk in tr_handle_clear_wakeup branch of usb_handle_request to skip calling usb_handle_remote_wakeup.

bz added inline comments.
sys/dev/usb/usbdevs
1287

Indentation looks strange