STRUCT CTI_DEVICE(9)
okay so bestie, this is struct cti_device(9) straight out of the Kernel API Manual, and it's literally just the vibe check for CTI device properties π
no cap, it's short and it slays.
π NAME π
struct cti_device β the description of CTI device properties. that's the whole assignment, and it ate β¨
π¦ SYNOPSIS π¦
struct cti_device {
int nr_trig_con;
u32 ctm_id;
struct list_head trig_cons;
int cpu;
const struct attribute_group **con_groups;
};
πΈ Members πΈ
okay so here's the member-by-member tea β and real talk, nr_trig_con is sitting right there in the struct but this list doesn't say one single thing about it, so I'm not gonna invent lore π the facts are the facts.
ctm_idβ which CTM this device is connected to. by default it's assumed there's a single CTM per SoC, ID0πtrig_consβ the list of connections to this device. it's giving "just a list" and honestly? iconic πcpuβ the CPU ID if it's associated with a CPU, and-1otherwise π«Άcon_groupsβ the combined static and dynamic sysfs groups for trigger connections. both. together. we love to see it β¨
π SEE ALSO π
- Kernel file
./drivers/hwtracing/coresight/coresight-cti.h struct cti_config(9)struct cti_drvdata(9)
and that's the whole page fr fr β it lives over in ./drivers/hwtracing/coresight, it's dated October 2026, and it's called struct cti_device(9). mwah, go read the header bestie πππ§
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms