STRUCT TI_SCI_MSG_RM_RING_CFG(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

struct ti_sci_msg_rm_ring_cfg β€” Ring configuration, bestie ✨


πŸŽ€ SYNOPSIS πŸŽ€

struct ti_sci_msg_rm_ring_cfg {
    u32 valid_params;
    u16 nav_id;
    u16 index;
    u32 addr_lo;
    u32 addr_hi;
    u32 count;
    u8 mode;
    u8 size;
    u8 order_id;
    u16 virtid;
    u8 asel;
 };

Like, that's the whole struct β€” every field, exactly as it lives in the header, no notes 🫢


🌸 Members 🌸

Okay so this section is lowkey just vibing empty on the page β€” no per-member breakdown got written here. The fields themselves are all right up there in the SYNOPSIS, so go peek at that πŸ‘€


πŸ¦‹ DESCRIPTION πŸ¦‹

This struct is literally just the parameters for Navigator Subsystem ring configuration πŸ’« that's the whole job. It's giving "payload" energy, not "main character" energy.

And for the actual request-side deets? See ti_sci_msg_rm_ring_cfg_req β€” that's your girl, go check her page iykyk πŸ”₯


πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./include/linux/soc/ti/ti_sci_protocol.h 🌈 and honestly the whole friend group:

  • struct ti_sci_version_info(9)
  • struct ti_sci_core_ops(9)
  • struct ti_sci_dev_ops(9)
  • struct ti_sci_clk_ops(9)
  • struct ti_sci_pm_ops(9)
  • struct ti_sci_resource_desc(9)
  • struct ti_sci_rm_core_ops(9)
  • struct ti_sci_rm_irq_ops(9)
  • struct ti_sci_rm_ringacc_ops(9)
  • struct ti_sci_rm_psil_ops(9)
  • struct ti_sci_rm_udmap_ops(9)
  • struct ti_sci_proc_ops(9)
  • struct ti_sci_ops(9)
  • struct ti_sci_handle(9)
  • struct ti_sci_resource(9)

ngl that's a whole squad β€” collect them all like stickers πŸ“

✨ mwah πŸ’‹ this page came from the Kernel API Manual, lives at ./include/linux/soc/ti, and is dated October 2026 β€” so like, future-dated icon behavior, periodt πŸ’œ

πŸ“¦ where this page comes from