STRUCT TI_SCI_RESOURCE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ struct ti_sci_resource(9) πŸŽ€

okay so bestie, welcome to the Kernel API Manual β€” yes we're doing kernel structs today and honestly? it's giving main character energy πŸ’…


✨ NAME ✨

struct ti_sci_resource β€” it's literally the structure that represents a resource assigned to a device. that's the whole vibe. a resource. assigned to a device. periodt 🫢


🌸 SYNOPSIS 🌸

struct ti_sci_resource {
    u16 sets;
    raw_spinlock_t lock;
    struct ti_sci_resource_desc *desc;
};

like look at her. three fields. clean. iconic. no cap πŸ’œ


πŸ¦‹ Members πŸ¦‹

  • sets β€” a u16 holding the Number of sets available from this resource type. that's how many sets you get from this resource type, fr fr ✨
  • lock β€” a raw_spinlock_t, and its whole job is to guard the res map in each set. the res map. in each set. she's the bouncer at the door, lowkey πŸ”₯
  • desc β€” pointer to the Array of resource descriptors, typed as struct ti_sci_resource_desc *. the descriptors live here, that's just where they are πŸ’–

🌈 SEE ALSO 🌈

bestie you already know there's more where this came from. the kernel file is ./include/linux/soc/ti/ti_sci_protocol.h and it's packed with 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_msg_rm_ring_cfg(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)

go read them. all of them. iykyk πŸ˜­πŸ’…


okay that's the whole page and honestly you ate that πŸ“ this lil number lives at ./include/linux/soc/ti, and it's stamped October 2026, so like… future vibes ✨ and the title card on this one is struct ti_sci_resource(9) in case anyone asks β€” bye bestie, see you in the headers πŸ’œπŸ§šβ€β™€οΈ

πŸ“¦ where this page comes from