STRUCT MCP47FEB02_FEATURES(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ struct mcp47feb02_features(9) ✨

okay so bestie, welcome to the Kernel API Manual πŸ’– this is one of those little kernel pages that's short, sweet, and honestly kind of iconic β€” it's the chip-specific data struct for the mcp47feb02 driver, and it ate. no cap. let's get into it 🫢


πŸ’… NAME

struct mcp47feb02_features β€” chip specific data ✨

like, literally just "chip specific data." that's the whole vibe. it's the struct that holds the deets each different chip variant needs to spill 🌸


πŸŽ€ SYNOPSIS

struct mcp47feb02_features {
    const char *name;
    unsigned int phys_channels;
    unsigned int resolution;
    bool have_ext_vref1;
    bool have_eeprom;
};

🌈 Members

bestie there are five (5) members and every single one matters, so let's go one by one πŸ‘‘

  • name β€” device name. that's it, that's the field πŸ’« it's the const char * that tells you what the device is called.
  • phys_channels β€” number of hardware channels πŸ”₯ unsigned int, and it's counting the actual physical channels the hardware has, fr fr.
  • resolution β€” DAC resolution ⭐ also unsigned int, and yes it's the DAC resolution, exactly like it says.
  • have_ext_vref1 β€” the field that answers the question: does the hardware have an the second external voltage reference? πŸ™ˆ yes, "an the" β€” the typo is canon, I don't make the rules, I just report them 😭 it's a bool, so it's just a yes/no vibe check on that second external voltage reference.
  • have_eeprom β€” does the hardware have an internal eeprom? πŸ“ another bool, another yes/no. internal eeprom: present or not present, that is the question.

πŸ’œ SEE ALSO

  • Kernel file ./drivers/iio/dac/mcp47feb02.c struct mcp47feb02_channel_data(9), struct mcp47feb02_data(9)
go read those two sibling structs too, bestie β€” mcp47feb02_channel_data(9) and mcp47feb02_data(9) β€” they're right there in the same ./drivers/iio/dac/mcp47feb02.c file and they're lowkey the rest of the story πŸ¦‹

k that's the whole page, you slayed by reading it πŸ’… mwah. this little drop comes to you from the ./drivers/iio/dac directory, dated October 2026, straight out of the Kernel API Manual β€” periodt πŸŽ€βœ¨πŸ‘‘

πŸ“¦ where this page comes from