STRUCT RM_TI_SCI_MSG_UDMAP_RX_FLOW_OPT_CFG(9)
πΈ struct rm_ti_sci_msg_udmap_rx_flow_opt_cfg(9) β Kernel API Manual πΈ
okay bestie, welcome to the Kernel API Manual, pull up a chair π«Ά this one's all about the parameters for UDMAP receive flow optional configuration. yes it's a mouthful, no you don't have to say it out loud π
β¨ NAME β¨
struct rm_ti_sci_msg_udmap_rx_flow_opt_cfg β the parameters for UDMAP receive flow optional configuration. that's it, that's the vibe π
π¦ SYNOPSIS π¦
struct rm_ti_sci_msg_udmap_rx_flow_opt_cfg {
struct ti_sci_msg_hdr hdr;
u32 nav_id;
u32 flow_index;
u32 rx_ch_index;
u16 rx_size_thresh0;
u16 rx_size_thresh1;
u16 rx_size_thresh2;
u16 rx_fdq0_sz1_qnum;
u16 rx_fdq0_sz2_qnum;
u16 rx_fdq0_sz3_qnum;
};
literally just look at it. gorgeous. no notes. π₯
π Members π
okay so this is the part where we meet the whole cast, main character energy for every single field π
hdrβ the Generic Header. every struct's little passport, iykyk πnav_idβ the SoC Navigator Subsystem device ID that the receive flow gets allocated from. it's giving "where do you even come from" π§flow_indexβ the UDMAP receive flow index for optional configuration. this is the one you're configuring, bestie, don't lose it πrx_ch_indexβ specifies the index of the receive channel that's using theflow_index. the way these two are linked... obsessed πrx_size_thresh0β UDMAP receive flow packet size threshold 0. yes, zero. the first one βrx_size_thresh1β UDMAP receive flow packet size threshold 1. the sequel πΈrx_size_thresh2β UDMAP receive flow packet size threshold 2. the trilogy, complete πrx_fdq0_sz1_qnumβ UDMAP receive flow free descriptor queue for size threshold 1. matching set with the threshold above, slay β¨rx_fdq0_sz2_qnumβ UDMAP receive flow free descriptor queue for size threshold 2. same energy, different number π¦rx_fdq0_sz3_qnumβ UDMAP receive flow free descriptor queue for size threshold 3. yes threshold 3 β look, I just report what the struct says π
π Description π
so for the detailed info on all these settings, go read the UDMAP section of the TRM. that's the whole assignment, no cap π β I'm not out here inventing lore that isn't in the original, periodt.
π SEE ALSO π
Kernel file ./drivers/firmware/ti_sci.h, plus this whole friend group right here (all (9) man pages, obviously) π«Ά
struct ti_sci_msg_hdr(9)struct ti_sci_msg_resp_version(9)struct ti_sci_msg_req_reboot(9)struct ti_sci_msg_resp_query_fw_caps(9)struct ti_sci_msg_req_set_device_state(9)struct ti_sci_msg_req_get_device_state(9)struct ti_sci_msg_resp_get_device_state(9)struct ti_sci_msg_req_set_device_resets(9)struct ti_sci_msg_req_set_clock_state(9)struct ti_sci_msg_req_get_clock_state(9)struct ti_sci_msg_resp_get_clock_state(9)struct ti_sci_msg_req_set_clock_parent(9)struct ti_sci_msg_req_get_clock_parent(9)struct ti_sci_msg_resp_get_clock_parent(9)struct ti_sci_msg_req_get_clock_num_parents(9)struct ti_sci_msg_resp_get_clock_num_parents(9)struct ti_sci_msg_req_query_clock_freq(9)struct ti_sci_msg_resp_query_clock_freq(9)struct ti_sci_msg_req_set_clock_freq(9)struct ti_sci_msg_req_get_clock_freq(9)struct ti_sci_msg_resp_get_clock_freq(9)struct ti_sci_msg_req_prepare_sleep(9)struct ti_sci_msg_req_set_io_isolation(9)struct ti_sci_msg_resp_lpm_wake_reason(9)struct ti_sci_msg_req_lpm_set_device_constraint(9)struct ti_sci_msg_req_lpm_set_latency_constraint(9)struct ti_sci_msg_req_get_resource_range(9)struct ti_sci_msg_resp_get_resource_range(9)struct ti_sci_msg_req_manage_irq(9)struct ti_sci_msg_rm_ring_cfg_req(9)struct ti_sci_msg_psil_pair(9)struct ti_sci_msg_psil_unpair(9)struct ti_sci_msg_udmap_rx_flow_cfg(9)struct ti_sci_msg_rm_udmap_tx_ch_cfg_req(9)struct ti_sci_msg_rm_udmap_rx_ch_cfg_req(9)struct ti_sci_msg_rm_udmap_flow_cfg_req(9)struct ti_sci_msg_req_proc_request(9)struct ti_sci_msg_req_proc_release(9)struct ti_sci_msg_req_proc_handover(9)struct ti_sci_msg_req_set_config(9)struct ti_sci_msg_req_set_ctrl(9)struct ti_sci_msg_req_get_status(9)struct ti_sci_msg_resp_get_status(9)
like, go read them, they're all right there in ./drivers/firmware ππ
ngl this page is short but it ate. no flags, no exit statuses, no scary warnings β just a struct being its best self π
and that's the whole page, bestie!! this lil drop came from ./drivers/firmware, version dated October 2026, and the page itself is struct rm_ti...flow_opt_cfg(9) β mwah, go forth and configure those receive flows π
πβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms