atc260x_match_device(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… 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 .dev field 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