STRUCT CTI_DEVICE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

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, ID 0 πŸ‘‘
  • 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 -1 otherwise 🫢
  • 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