devm_regmap_field_bulk_free(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… devm_regmap_field_bulk_free β€” the Kernel API Manual girlies know this one

okay so bestie, welcome to <pink>devm_regmap_field_bulk_free</pink> from the Kernel API Manual ✨ this little function is the cleanup bestie for bulk register fields, and honestly? she's lowkey iconic for doing almost nothing and letting the devm magic handle it 🫢


🌸 NAME 🌸

devm_regmap_field_bulk_free β€” frees a bulk register field that was allocated using devm_regmap_field_bulk_alloc πŸ’–


✨ SYNOPSIS ✨

void devm_regmap_field_bulk_free (struct device *dev , struct regmap_field *field );

no cap, that's the whole signature πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • dev β€” the device that will be interacted with πŸ¦‹ like, that's the device in question, keep up bestie
  • field β€” the regmap field which should be freed 🧹 the one getting the goodbye treatment

πŸ”₯ DESCRIPTION πŸ”₯

so basically this frees a register field that was allocated using devm_regmap_field_bulk_alloc ✨ that's it, that's the job.

fr fr, usually drivers need not call this function, because the memory allocated via devm gets freed automatically as per the device-driver life-cycle πŸ’€ like the whole point of devm is that you don't have to remember, she remembers for you πŸ‘‘

🌈 SEE ALSO 🌈

kernel file: ./drivers/base/regmap/regmap.c πŸ—‚οΈ and the whole friend group:

like, the whole regmap friend group showed up to the function's going-away party πŸ˜­πŸ’–


🫢 anyway, that's the page! sourced from ./drivers/base/regmap, dated October 2026, and yes the manual name is <pink>devm_regmap_field_bulk_free(9)</pink> β€” stan a self-referential queen πŸ‘‘πŸŒΈ periodt πŸ’…
πŸ“¦ where this page comes from