usb_resume_both(9)

💖 NAME 💖

okay so bestie, this is the Kernel API Manual page for usb_resume_both(9), and the name is literally usb_resume_both — resume a USB device and its interfaces ✨. It’s giving “wake up, babe, we’re resuming USB stuff” energy 💅.

✨ SYNOPSIS ✨

int usb_resume_both (struct usb_device *udev , pm_message_t msg );

🎀 ARGUMENTS 🎀

• udev — the usb_device to resume 🦋
• msg — Power Management message describing this state transition ⭐

🌸 DESCRIPTION 🌸

This is the central routine for resuming USB devices. It calls the resume method for udev and then calls the resume methods for all the interface drivers in udev. No cap, it’s the main character of USB resume 💅.

Autoresume requests originating from a child device or an interface driver may be made without the protection of udev's device lock, but all other resume calls will hold the lock. Usbcore will insure that method calls do not arrive during bind, unbind, or reset operations. However, drivers must be prepared to handle resume calls arriving at unpredictable times 😭.

This routine can run only in process context. Periodt. 🫶

🔥 RETURN 🔥

0 on success. That’s the whole return vibe, bestie — zero means slay ✅.

🌈 SEE ALSO 🌈

Kernel file ./drivers/usb/core/driver.c says hi, and these besties are linked too:

• usb_driver_claim_interface(9)
• usb_driver_release_interface(9)
• usb_match_id(9)
• usb_register_device_driver(9)
• usb_deregister_device_driver(9)
• usb_register_driver(9)
• usb_deregister(9)
• usb_suspend_both(9)
• usb_enable_autosuspend(9)
• usb_disable_autosuspend(9)
• usb_autosuspend_device(9)
• usb_autoresume_device(9)
• usb_autopm_put_interface(9)
• usb_autopm_put_interface_async(9)
• usb_autopm_put_interface_no_suspend(9)
• usb_autopm_get_interface(9)
• usb_autopm_get_interface_async(9)
• usb_autopm_get_interface_no_resume(9)

okay that’s the page, bestie 🫶 source/version: ./drivers/usb/core • date: October 2026 • usb_resume_both(9) signing off 💅✨