STRUCT TI_SYSC_MODULE_DATA(9)

✨ struct ti_sysc_module_data(9) ✨

okay so bestie, welcome to the kernel API manual for struct ti_sysc_module_data, and honestly? this one is giving "translation layer" main character energy 💅 it's the struct that holds ti-sysc to hwmod translation data for a module. yes, translation — like when your friend explains your group chat drama to their mom, except it's device tree data being explained to the legacy hwmod world 😭

---

🌸 SYNOPSIS 🌸

here's the whole shape of it, literally verbatim, no cap:

struct ti_sysc_module_data {
    const char *name;
    u64 module_pa;
    u32 module_size;
    int *offsets;
    int nr_offsets;
    const struct sysc_capabilities *cap;
    struct sysc_config *cfg;
 };

---

🎀 Members 🎀

let's go through them one by one, bestie, they all matter:

• name — the legacy "ti,hwmods" module name. iconic throwback, honestly.
• module_pa — the physical address of the interconnect target module 🔥
• module_size — the size of the interconnect target module
• offsets — an array of register offsets as listed in enum sysc_registers
• nr_offsets — the number of registers
• cap — interconnect target module capabilities
• cfg — interconnect target module configuration

---

🦋 Description 🦋

so what's the whole point? literally this: this data is enough to allocate a new struct omap_hwmod_class_sysconfig based on device tree data parsed by the ti-sysc driver. that's it, that's the vibe check ✅ enough info to build the thing, sourced from device tree data, parsed by ti-sysc.

---

🌈 SEE ALSO 🌈

go look at these, iykyk:

• Kernel file ./include/linux/platform_data/ti-sysc.h
• struct sysc_regbits(9)
• struct sysc_capabilities(9)
• struct sysc_config(9)

fr fr go read ti-sysc.h first, it's the whole context and it ate 💖

---

and that's the page!! 🫶 sign-off time: this beauty comes from ./include/linux/platform_data, dated October 2026, and it's struct ti_sysc_module_data(9) — periodt, go forth and translate those modules babes 🌸✨👑