sysc_ioremap(9)

📦 version 7.3.1, in nixpkgs unstable

💅 sysc_ioremap — like, the whole vibe ✨

okay so bestie, welcome to sysc_ioremap(9), straight out of the Kernel API Manual 🎀. This one's a tiny little function with main character energy, and honestly? She ate. Let's get into it 💖

🌸 NAME 🌸

sysc_ioremap — ioremap register space for the interconnect target module ✨

Like, that's literally her whole job. She takes the interconnect target module's register space and ioremaps it. No cap 🫶

🦋 SYNOPSIS 🦋

int sysc_ioremap (struct sysc *ddata );

There she is. One (1) function, one (1) argument, zero drama 💅

🎀 ARGUMENTS 🎀

  • ddata — device driver data 🌈

That's it. That's the argument. She's lowkey low-maintenance like that.

✨ DESCRIPTION ✨

Okay so here's the tea, and it's actually kind of important ☕:

the interconnect target module registers can be anywhere within the interconnect target module range. Like, they're not guaranteed to be sitting politely at the start. They're giving "wherever they feel like it" energy 😭

For example — and these examples are iconic, ngl:

  • SGX has them at offset 0x1fc00 in the 32MB module address space 👀
  • and cpsw has them at offset 0x1200 in the CPSW_WR child 💀

So yeah, do NOT just assume offset zero, bestie. That's the trap.

That said — usually the interconnect target module registers are at the beginning of the module range though. Usually!! Not always!! Read the room, read the offset 🌸

fr fr, this is the whole reason the function exists. The registers are wherever the hardware decided to put them, and you gotta deal with it 💜

🔥 SEE ALSO 🔥

Kernel file ./drivers/bus/ti-sysc.c — go read it, it's giving essential lore 📖

Then the whole friend group of related pages, all of them, no skips:

iykyk 👑

mwah 💋 that's the page. written from ./drivers/bus, dated October 2026, and yeah — it's still signed sysc_ioremap(9), because she's the main character. periodt 💅✨

📦 where this page comes from