ENUM CPPI5_TR_RESP_STATUS_UNSUPPORTED(9)

✨ NAME ✨

okay so bestie, welcome to the Kernel API Manual — today’s main character is enum cppi5_tr_resp_status_unsupported, aka the TR Response Status field values that correspond to an Unsupported Error. it’s giving “nope, not supported” energy in enum form, and honestly? iconic. 💅✨

🩷 SYNOPSIS 🩷

here’s the enum in all its glory — keep it exactly as-is, no cap:

       enum cppi5_tr_resp_status_unsupported {
           CPPI5_TR_RESPONSE_STATUS_UNSUPPORTED_TR_TYPE ,
           CPPI5_TR_RESPONSE_STATUS_UNSUPPORTED_STATIC ,
           CPPI5_TR_RESPONSE_STATUS_UNSUPPORTED_EOL ,
           CPPI5_TR_RESPONSE_STATUS_UNSUPPORTED_CFG_SPECIFIC ,
           CPPI5_TR_RESPONSE_STATUS_UNSUPPORTED_AMODE ,
           CPPI5_TR_RESPONSE_STATUS_UNSUPPORTED_ELTYPE ,
           CPPI5_TR_RESPONSE_STATUS_UNSUPPORTED_DFMT ,
           CPPI5_TR_RESPONSE_STATUS_UNSUPPORTED_SECTR ,
           CPPI5_TR_RESPONSE_STATUS_UNSUPPORTED_AMODE_SPECIFIC

       };

💅 CONSTANTS 💅

each constant is a different flavor of “not supported,” and they are all serving unsupported realness:

• CPPI5_TR_RESPONSE_STATUS_UNSUPPORTED_TR_TYPE — TR Type? not supported. periodt. 🙅‍♀️
• CPPI5_TR_RESPONSE_STATUS_UNSUPPORTED_STATIC — STATIC not supported, bestie. 💀
• CPPI5_TR_RESPONSE_STATUS_UNSUPPORTED_EOL — EOL not supported. nope. 🚫
• CPPI5_TR_RESPONSE_STATUS_UNSUPPORTED_CFG_SPECIFIC — CONFIGURATION SPECIFIC not supported. it’s not invited. 🙈
• CPPI5_TR_RESPONSE_STATUS_UNSUPPORTED_AMODE — AMODE not supported. catch you never. ✌️
• CPPI5_TR_RESPONSE_STATUS_UNSUPPORTED_ELTYPE — ELTYPE not supported. lowkey tragic. 😭
• CPPI5_TR_RESPONSE_STATUS_UNSUPPORTED_DFMT — DFMT not supported. fr fr. 🍓
• CPPI5_TR_RESPONSE_STATUS_UNSUPPORTED_SECTR — SECTR not supported. bye bestie. 👋
• CPPI5_TR_RESPONSE_STATUS_UNSUPPORTED_AMODE_SPECIFIC — the AMODE SPECIFIC field is not supported. it’s giving rejected by the group chat. 💔

👑 SEE ALSO 👑

okay if you want the full lore, go peek at the kernel file ./include/linux/dma/ti-cppi5.h and the whole bestie lineup:

• struct cppi5_desc_hdr_t(9)
• struct cppi5_host_desc_t(9)
• struct cppi5_desc_epib_t(9)
• struct cppi5_monolithic_desc_t(9)
• cppi5_desc_is_tdcm(9)
• cppi5_desc_get_type(9)
• cppi5_desc_get_errflags(9)
• cppi5_desc_get_pktids(9)
• cppi5_desc_set_pktids(9)
• cppi5_desc_set_retpolicy(9)
• cppi5_desc_get_tags_ids(9)
• cppi5_desc_set_tags_ids(9)
• cppi5_hdesc_calc_size(9)
• cppi5_hdesc_init(9)
• cppi5_hdesc_update_flags(9)
• cppi5_hdesc_update_psdata_size(9)
• cppi5_hdesc_get_psdata_size(9)
• cppi5_hdesc_get_pktlen(9)
• cppi5_hdesc_set_pktlen(9)
• cppi5_hdesc_get_psflags(9)
• cppi5_hdesc_set_psflags(9)
• cppi5_hdesc_get_pkttype(9)
• cppi5_hdesc_set_pkttype(9)
• cppi5_hdesc_attach_buf(9)
• cppi5_hdesc_link_hbdesc(9)
• cppi5_hdesc_epib_present(9)
• cppi5_hdesc_get_psdata(9)
• cppi5_hdesc_get_swdata(9)
• enum cppi5_tr_types(9)
• enum cppi5_tr_event_size(9)
• enum cppi5_tr_trigger(9)
• enum cppi5_tr_trigger_type(9)
• struct cppi5_tr_type0_t(9)
• struct cppi5_tr_type1_t(9)
• struct cppi5_tr_type2_t(9)
• struct cppi5_tr_type3_t(9)
• struct cppi5_tr_type15_t(9)
• struct cppi5_tr_resp_t(9)
• enum cppi5_tr_resp_status_type(9)
• enum cppi5_tr_resp_status_submission(9)
• cppi5_trdesc_calc_size(9)
• cppi5_trdesc_init(9)
• cppi5_tr_init(9)
• cppi5_tr_set_trigger(9)
• cppi5_tr_csf_set(9)

mwah 💋 that’s the page, bestie — source/version ./include/linux/dma, dated October 2026, and the page name is enum cppi5_..._unsupported(9). go be iconic with your TR response statuses 🫶✨