ENUM CVMX_USB_STATUS(9)

💅 enum cvmx_usb_status(9) — the Kernel API Manual, bestie edition ✨

okay so this is a page from the Kernel API Manual and it's literally all about enum cvmx_usb_status — the glow-up list of status codes your callback function can get handed back. no cap, it's the vibe check for how your USB transaction went 🦋

---

🌸 NAME 🌸

enum cvmx_usb_status — the possible callback function status codes 💖

like, every possible mood your transaction could come home in. some are slay, some are... not. 😭

---

✨ SYNOPSIS ✨

enum cvmx_usb_status {
    CVMX_USB_STATUS_OK ,
    CVMX_USB_STATUS_SHORT ,
    CVMX_USB_STATUS_CANCEL ,
    CVMX_USB_STATUS_ERROR ,
    CVMX_USB_STATUS_STALL ,
    CVMX_USB_STATUS_XACTERR ,
    CVMX_USB_STATUS_DATATGLERR ,
    CVMX_USB_STATUS_BABBLEERR ,
    CVMX_USB_STATUS_FRAMEERR

};

bestie look at that list. nine whole constants. iconic lineup fr fr 👑

---

🎀 Constants 🎀

okay let's meet the cast, one by one 🫶

• CVMX_USB_STATUS_OK — the main character energy result. the transaction / operation finished without any errors. we love to see it, periodt ✨
• CVMX_USB_STATUS_SHORT — FIXME: this is currently not implemented. so like… it's on the list but it's not actually doing anything yet 🙈 the manpage literally says so, don't come for me
• CVMX_USB_STATUS_CANCEL — the transaction was canceled while in flight by a user call to cvmx_usb_cancel. not me yanking it out of the air mid-flight 💀
• CVMX_USB_STATUS_ERROR — the transaction aborted with an unexpected error status. it's giving chaos, it's giving no warning 😭
• CVMX_USB_STATUS_STALL — the transaction received a USB STALL response from the device. the device literally said "no 💅" and stalled on you
• CVMX_USB_STATUS_XACTERR — the transaction failed with an error from the device even after a number of retries. we tried, we retried, it still said no 🔥
• CVMX_USB_STATUS_DATATGLERR — the transaction failed with a data toggle error even after a number of retries. yes, the data toggle. yes, even after retries 🌈
• CVMX_USB_STATUS_BABBLEERR — the transaction failed with a babble error. babble!! the drama of it all 😭
• CVMX_USB_STATUS_FRAMEERR — the transaction failed with a frame error even after a number of retries. retries were given, and still it fell apart 🍓

---

🔥 SEE ALSO 🔥

go read the Kernel file ./drivers/usb/host/octeon-hcd.c and also these absolute icons:

• enum cvmx_usb_speed(9)
• enum cvmx_usb_transfer(9)
• enum cvmx_usb_direction(9)
• struct cvmx_usb_port_status(9)
• struct cvmx_usb_iso_packet(9)
• enum cvmx_usb_initialize_flags(9)
• enum cvmx_usb_pipe_flags(9)
• struct cvmx_usb_transaction(9)
• struct cvmx_usb_pipe(9)
• struct octeon_hcd(9)
• struct octeon_temp_buffer(9)
• octeon_alloc_temp_buffer(9)
• octeon_free_temp_buffer(9)
• octeon_map_urb_for_dma(9)
• octeon_unmap_urb_for_dma(9)

---

ngl bestie, the "FIXME: This is currently not implemented" on CVMX_USB_STATUS_SHORT is the most relatable thing on this whole page. we've all been there. 💀

---

okay that's the whole thing, you ate that read 👑 this page lives in ./drivers/usb/host, dated October 2026, and it's officially called enum cvmx_usb_status(9). mwah, go forth and handle your callbacks 💜🧚‍♀️