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

Authored by mchoo on Jul 2 2026, 12:08 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 74473
Build 71356: arc lint + arc unit

Event Timeline

mchoo created this revision.Jul 2 2026, 12:08 AM

Herald added subscribers: ziaee, imp. · View Herald TranscriptJul 2 2026, 12:08 AM

mchoo requested review of this revision.Jul 2 2026, 12:08 AM

Harbormaster completed remote builds in B74473: Diff 181204.Jul 2 2026, 12:08 AM

mchoo added a subscriber: aokblast.Jul 2 2026, 12:09 AM

Fix indent on flags

Harbormaster completed remote builds in B74474: Diff 181205.Jul 2 2026, 12:11 AM

mchoo added inline comments.Jul 2 2026, 12:13 AM

sys/dev/usb/usb_device.h
97–99	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.

aokblast added a reviewer: USB.Jul 12 2026, 8:50 AM

aokblast added inline comments.Jul 12 2026, 8:54 AM

sys/dev/usb/usb_device.h
97–99	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.