STRUCT TPDM_DATASET_ATTRIBUTE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct tpdm_dataset_attribute(9) β€” Kernel API Manual, bestie edition ✨

Okay so picture this: you're in the Kernel API Manual, and there's this lil struct called struct tpdm_dataset_attribute whose whole entire job is recording the member variables and index number of datasets that need to be operated by sysfs file. That's it, that's the vibe. It's giving "I know a guy who knows which dataset field you meant" πŸŽ€


✨ SYNOPSIS ✨

struct tpdm_dataset_attribute {
    struct device_attribute attr;
    enum dataset_mem mem;
    u32 idx;
 };

No cap, that's the whole shape of it. Three members, all iconic, all doing their own thing πŸ‘‘


🫢 Members 🫢

  • attr β€” the device attribute πŸ’– literally just the struct device_attribute, living its best life, nothing extra going on here.
  • mem β€” the member in the dataset data structure. Which one? That's what this field is for, bestie. It's an enum dataset_mem, so it knows exactly which member we're talking about πŸ¦‹
  • idx β€” the index number of the array data. A u32. So when the dataset field is an array, this tells you which slot in it we're operating on. Periodt 🌸

🌈 SEE ALSO 🌈

  • Kernel file ./drivers/hwtracing/coresight/coresight-tpdm.h
  • struct dsb_dataset(9)
  • struct cmb_dataset(9)
  • struct tpdm_drvdata(9)

Lowkey obsessed with how tidy this one is. Go read the header file if you want the full lore, iykyk πŸ’€βœ¨

And that's a wrap, bestie 🧚 β€” brought to you by the fine people over at ./drivers/hwtracing/coresight, dated October 2026, header and footer respectfully folded into this message because we're cute like that πŸ’œβ­

πŸ“¦ where this page comes from