STRUCT REGMAP_RANGE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ struct regmap_range(9) πŸŽ€

okay so bestie, welcome to the Kernel API Manual page for struct regmap_range πŸ’… this one's short and sweet β€” it's the little struct that says "here's a chunk of registers, from this one to that one" β€” and it's what the regmap access checks (readable / writeable / volatile / precious) use to make their decisions ✨


✨ SYNOPSIS ✨

struct regmap_range {
    unsigned int range_min;
    unsigned int range_max;
 };

literally the whole struct, that's her 🫢 two unsigned ints and a dream.


πŸ¦‹ Members πŸ¦‹

  • range_min β€” the address of the first register in the range, i.e. where the vibe starts 🌸
  • range_max β€” the address of the last register in the range, i.e. where the vibe ends πŸŽ€

so it's an inclusive lil window of registers, and the access related checks (readable/writeable/volatile/precious) use it to know what's in bounds, no cap πŸ’–


🌈 SEE ALSO 🌈

the Kernel file to go look at is ./include/linux/regmap.h β€” that's the main character file of this whole situation πŸ‘‘

and here's the rest of the friend group, bestie, all of them, no skipping πŸ™ˆ:

like I said, big friend group, but every single one of them showed up πŸ’€πŸ’– iykyk


this page lives in ./include/linux, dated October 2026, and it's struct regmap_range(9) all the way down. mwah, go read the sidebar, slay πŸ§šβ€β™€οΈπŸŒΈ
πŸ“¦ where this page comes from