has_valid_limit(9)

📦 version 7.3.1, in nixpkgs unstable

💅 has_valid_limit — a kernel API manual, but make it cute ✨

okay so real talk: this page lives in the Kernel API Manual (section 9, the kernel-API girlies 🧚), and today we're doing a vibe check on has_valid_limit. yes bestie, that's literally the whole function name, and yes it's exactly as iconic as it sounds 🎀

✨ NAME ✨

has_valid_limit — checks if a power-related attribute has a valid limit value 🔥

like, does this thing actually have a real limit, or is it giving nothing? we find out 👑

🌸 SYNOPSIS 🌸

bool has_valid_limit (const char *name , const struct power_limits *limits );

🦋 ARGUMENTS 🦋

  • name — the name of the attribute to check. that's the string, the label, the little nametag 🏷️
  • limits — pointer to the power_limits structure containing limit values. this is where the actual numbers live 💖

💜 DESCRIPTION 💜

okay so here's the tea ☕: this function checks if a power-related attribute has a valid limit value. that's it, that's the job, and she does it flawlessly.

it returns false in two very specific situations, and only these two, no cap:

  • if limits is NULL 😭 (girl is not there, can't check a ghost)
  • if the corresponding limit value is zero 💀

basically zero and NULL both fail the vibe check. everything else slays through as valid 🫶

⭐ RETURN ⭐

true if the attribute has a valid limit value, false otherwise 🌈

two outcomes. binary. clean. she ate 💅

🎀 SEE ALSO 🎀

kernel file ./drivers/platform/x86/asus-armoury.c — like, the actual source, go read her

honestly the whole friend group is worth a look:

lowkey a reminder bestie: false is not a bad thing here, it's just information 💖 don't take it personally

and that's the page!! 🦋💖 sign-off time: this little baddie comes to you from ./drivers/platform/x86, and the date on the tag says October 2026 🗓️✨ ily, go check your limits, mwah 💅🎀

📦 where this page comes from