STRUCT CTI_DRVDATA(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– struct cti_drvdata(9) πŸ’–

okay so bestie, this is the Kernel API Manual page for struct cti_drvdata, and it is literally the specifics for the CTI device. We are gonna go through every field together, no skipping, fr fr. 🫢


🌸 NAME 🌸

struct cti_drvdata β€” specifics for the CTI device. That's the whole assignment, and she ate. ✨


✨ SYNOPSIS ✨

       struct cti_drvdata {
           void __iomem *base;
           struct coresight_device *csdev;
           struct cti_device ctidev;
           raw_spinlock_t spinlock;
           struct cti_config config;
           struct list_head node;
        };

πŸŽ€ Members πŸŽ€

  • base β€” memory-mapped base address for this component. (The source really did give us a double period there, and honestly? iconic 😭)
  • csdev β€” standard CoreSight device information. yes bestie, the standard stuff πŸ’…
  • ctidev β€” extra information needed by the CTI/CTM framework. it's giving "extra" in the best way πŸ¦‹
  • spinlock β€” controls data access to one at a time. one at a time, periodt πŸ”’
  • config β€” configuration data for this CTI device. all the settings vibes πŸŽ€
  • node β€” list entry of this device in the list of CTI devices. she's on the list, literally 🌟

πŸ”₯ SEE ALSO πŸ”₯

  • Kernel file ./drivers/hwtracing/coresight/coresight-cti.h, struct cti_device(9), struct cti_config(9) β€” go read those too, iykyk πŸ’œ

mwah πŸ’‹ β€” source/version: ./drivers/hwtracing/coresight; date: October 2026; page: struct cti_drvdata(9). bye bestie, go forth and read structs πŸ’…

πŸ“¦ where this page comes from