STRUCT REG_DATA(9)

✨ struct reg_data(9) ✨

okay so this is a page from the Kernel API Manual, and bestie, we're about to talk about struct reg_data — literally the data that comes out of the registers 💅

🌸 SYNOPSIS 🌸

struct reg_data {
    u8 meas_regs[PAC1934_MEAS_REG_LEN];
    u8 ctrl_regs[PAC1934_CTRL_REG_LEN];
    s64 energy_sec_acc[PAC1934_MAX_NUM_CHANNELS];
    s64 vpower_acc[PAC1934_MAX_NUM_CHANNELS];
    s32 vpower[PAC1934_MAX_NUM_CHANNELS];
    s32 vbus[PAC1934_MAX_NUM_CHANNELS];
    s32 vbus_avg[PAC1934_MAX_NUM_CHANNELS];
    s32 vsense[PAC1934_MAX_NUM_CHANNELS];
    s32 vsense_avg[PAC1934_MAX_NUM_CHANNELS];
    u8 num_enabled_channels;
};

like, that's the whole vibe. ten members, all doing their little jobs 🫶

🎀 Members 🎀

let me walk you through each one, no skips, we're doing all of them:

• meas_regs — a snapshot of the raw measurements registers. just a little pic of them at that moment 📸
• ctrl_regs — a snapshot of the control registers. same energy, different registers 💫
• energy_sec_acc — a snapshot of the energy values ⚡
• vpower_acc — the accumulated vpower values. it's been stacking them up, icon behaviour fr
• vpower — a snapshot of the vpower registers
• vbus — a snapshot of the vbus registers
• vbus_avg — the averages of the vbus registers. not a snapshot, an average, okurrr 📊
• vsense — a snapshot of the vsense registers
• vsense_avg — the averages of the vsense registers
• num_enabled_channels — the count of how many chip channels are currently enabled. like a headcount but for channels 👑

ngl bestie, notice how vbus_avg and vsense_avg are averages while vbus and vsense are snapshots — do not mix those up, that's the whole plot twist 😭

💜 SEE ALSO 💜

go read these next, they're in the same universe, main-character adjacent:

• Kernel file ./drivers/iio/adc/pac1934.c
• struct pac1934_features(9)
• struct pac1934_chip_info(9)

and that's the page 🦋 this little gem lives in ./drivers/iio/adc, dated October 2026 — mwah, slay, periodt ✨🎀💖