STRUCT K3_R5_SOC_DATA(9)

✨ struct k3_r5_soc_data(9) ✨

okay bestie, so this is a page straight out of the Kernel API Manual and it's literally all about struct k3_r5_soc_data — the "match data" that lets the kernel handle all the different SoC variations out there 🦋 no cap, that's the whole vibe.

🎀 NAME 🎀

struct k3_r5_soc_data — match data to handle SoC variations. periodt 💅

🌸 SYNOPSIS 🌸

struct k3_r5_soc_data {
    bool tcm_is_double;
    bool tcm_ecc_autoinit;
    bool single_cpu_mode;
    bool is_single_core;
    const struct k3_rproc_dev_data *core_data;
 };

like, look at her. five fields. all iconic. 👑

💖 Members 💖

• tcm_is_double — a flag that denotes the larger unified TCMs in certain modes ✨ (yes, "certain modes", the manpage is being mysterious, not me 🙈)
• tcm_ecc_autoinit — a flag that denotes the auto-initialization of TCMs for ECC. very diligent, very responsible, we love her 🫶
• single_cpu_mode — a flag that denotes if the SoC/IP supports Single-CPU mode 🎀
• is_single_core — a flag that denotes if the SoC/IP has only single core R5 🌸 (yes bestie, single_cpu_mode and is_single_core are two different flags, they're siblings not twins, don't @ me 😭)
• core_data — pointer to R5-core-specific device data ⭐

🔥 SEE ALSO 🔥

• Kernel file ./drivers/remoteproc/ti_k3_r5_remoteproc.c + struct k3_r5_cluster(9), struct k3_r5_core(9)
• iykyk, go read the source, it's giving main character energy 👑

fr fr, that's the whole page — every flag, every field, nothing dropped, we ate and left no crumbs 💀✨

and that's the wrap, bestie 🧚 from ./drivers/remoteproc, dated October 2026 — source/version and date, mentioned with love, as promised 💜🌈