sysc_parse_a..._child_range(9)

💅 sysc_parse_and_check_child_range — the kernel API manual, bestie edition ✨

okay so before we even start: yes, the page title is sysc_parse_a..._child_range(9) (it got truncated, it's giving "my name is too long for the terminal"), and the manual you're reading is the Kernel API Manual. Now let's get into it 🫶

---

🌸 NAME 🌸

sysc_parse_and_check_child_range — literally parses the module IO region from ranges. that's the whole job. iconic.

---

✨ SYNOPSIS ✨

int sysc_parse_and_check_child_range (struct sysc *ddata );

---

🎀 ARGUMENTS 🎀

• ddata — device driver data. that's it, that's the argument 💖

---

🦋 DESCRIPTION 🦋

okay so picture this: in general we only need rev, syss, and sysc registers — not the whole entire module range. like, we're not greedy, we don't need all of it 💅

but here's the thing — we do want the offsets for these registers, measured from the module base. why? because that lets us check them against the legacy hwmod platform data. very "keeping receipts" of it all, ngl.

and also? let's check the ranges are configured properly. vibe check on the ranges, basically. no cap. 🔥

---

👑 SEE ALSO 👑

• Kernel file ./drivers/bus/ti-sysc.c
• struct sysc(9)
• sysc_init_resets(9)
• sysc_check_one_child(9)
• sysc_parse_one(9)
• sysc_check_registers(9)
• sysc_ioremap(9)
• sysc_map_and_check_registers(9)
• sysc_show_rev(9)
• sysc_show_registers(9)
• sysc_write_sysconfig(9)
• sysc_context_notifier(9)
• sysc_add_restored(9)

like, go read those too, they're all in the same friend group fr fr 🧚

---

and that's the page!! 💜 this lil beauty lives in ./drivers/bus and it's dated October 2026 — so mark your calendar bestie, the page itself is already living in the future, main character energy only ⭐🌈🍓