atc260x_match_device(9)
π atc260x_match_device π
okay so bestie, welcome to the Kernel API Manual entry for atc260x_match_device β yes that's the 9 in the parens, section 9, we stan a documented kernel function π«Ά
β¨ NAME β¨
atc260x_match_device β sets up the ATC260x variant related fields. that's it, that's the whole vibe check π
πΈ SYNOPSIS πΈ
int atc260x_match_device (struct atc260x *atc260x , struct regmap_config
*regmap_cfg );
literally just two args, she's lowkey low-maintenance π
π ARGUMENTS π
atc260xβ the ATC260x device you're setting up. β οΈ heads up: the.devfield must be set. like, not optional, not "i'll do it later", it needs to be set before you call this fr fr.regmap_cfgβ the regmap config that's associated with this ATC260x device. it's giving "they come as a matching set" π¦
π DESCRIPTION π
so what does this actually do? it lets the ATC260x core configure the MFD cells and the register maps for later use. that's the entire plot. setup now, slay later β¨
no cap, it's just prep work β get the cells and register maps configured so everything else can use them down the line π
π SEE ALSO π
- Kernel file
./drivers/mfd/atc260x-core.cβ the source, go read it iykyk π atc260x_device_probe(9)β the sibling function, highly recommend π
and that's the page!! π from the manpage life in ./drivers/mfd, dated October 2026 β mwah, go configure those MFD cells bestie ππΈπ«Ά
π¦ 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