input_get_new_minor(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay bestie, welcome to input_get_new_minor(9) β€” this one is straight from the Kernel API Manual, and it’s giving β€œkernel internals but make it cute” energy βœ¨πŸ’…

πŸŽ€ NAME πŸŽ€

input_get_new_minor β€” allocates a new input minor number πŸ¦‹

✨ SYNOPSIS ✨

int input_get_new_minor (int legacy_base , unsigned int legacy_num ,
       bool allow_dynamic );

πŸ’… ARGUMENTS πŸ’…

  • legacy_base β€” beginning of the legacy range to be searched πŸ”
  • legacy_num β€” size of legacy range πŸ“
  • allow_dynamic β€” whether we can also take ID from the dynamic range πŸ‘€

πŸ”₯ DESCRIPTION πŸ”₯

This function allocates a new device minor from the input major namespace ✨. The caller can request a legacy minor by specifying legacy_base and legacy_num parameters, and can also specify whether an ID can be allocated from the dynamic range if there are no free IDs in the legacy range. That’s the whole vibe β€” legacy range first, dynamic range as the backup plan, no cap πŸ’…

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./drivers/input/input.c β€” yes, that’s the source-file reference, and then the whole input crew is here, iykyk:


okay that’s a wrap, bestie 🫢 β€” source/path: ./drivers/input, date: October 2026, page: input_get_new_minor(9). go forth and understand those minors, slay πŸ’–βœ¨

πŸ“¦ where this page comes from