STRUCT STM32_DFSDM_DEV_DATA(9)
π NAME
struct stm32_dfsdm_dev_data β the DFSDM compatible configuration data struct, aka the little info packet that tells the driver what hardware it's actually dealing with π
(this is from the Kernel API Manual btw, iykyk)
β¨ SYNOPSIS
struct stm32_dfsdm_dev_data {
u32 ipid;
unsigned int num_filters;
unsigned int num_channels;
const struct regmap_config *regmap_cfg;
};
πΈ Members
okay bestie, here's the whole cast of this struct β every single one, no skips π
ipidβ the DFSDM identification number π₯ heads up tho: this one is only used if the hardware actually provides identification registers. no registers? then it's just sitting there looking cute.num_filtersβ how many filters the DFSDM has π§ and lowkey, this is unused if identification registers are available. it's giving backup dancer energy.num_channelsβ how many channels the DFSDM has π same deal: unused if identification registers are available. the register-having hardware just handles it itself, periodt.regmap_cfgβ pointer to the SAI register map configuration β¨ yep, it literally says SAI in the description, we're not questioning it, we're just reporting it.
ngl the pattern here is real:ipid,num_filtersandnum_channelsare all the "only if hardware gives you identification registers" crew, andregmap_cfgis the one always doing its job π«Ά
π¦ SEE ALSO
- Kernel file
./drivers/iio/adc/stm32-dfsdm-core.cβ go read it, it's the main character π stm32_dfsdm_start_dfsdm(9)stm32_dfsdm_stop_dfsdm(9)
and that's the whole page, bestie π sourced from ./drivers/iio/adc, dated October 2026 β struct stm32_dfsdm_dev_data(9), slay, no cap, bye πβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms