bq257xx_pro...is_writeable(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… bq257xx_property_is_writeable β€” the vibe check for writeability

okay so bestie, this is a page out of the Kernel API Manual (yes, the Kernel API Manual, we're fancy now) and it's all about one tiny little function that answers the most important question in any relationship: can I write to you or not? 🫢


✨ NAME ✨

bq257xx_property_is_writeable β€” literally just checks if a property is writeable. that's it. that's the whole thing. πŸ’–


πŸŽ€ SYNOPSIS πŸŽ€

int bq257xx_property_is_writeable (struct power_supply *psy , enum
       power_supply_property prop );

🌸 ARGUMENTS 🌸

  • psy β€” the power supply device. the main character of this whole situation πŸ‘‘
  • prop β€” the power supply property you're side-eyeing and want to check πŸ™ˆ

πŸ¦‹ DESCRIPTION πŸ¦‹

so what does it actually do? it determines which power supply properties can be written to. and listen β€” the guest list is short, it's giving exclusive VIP section:

  • charge current limit
  • charge voltage limit
  • input current limit

those three and only those three are writeable. everybody else? not on the list, not getting in. periodt. πŸ’€


⭐ RETURN ⭐

  • returns 1 if the property is writeable πŸ”₯
  • returns 0 otherwise 🧚

(no in-between, no "it's complicated", just a clean little binary vibe check.)


🌈 SEE ALSO 🌈

Kernel file ./drivers/power/supply/bq257xx_charger.c β€” and honestly, the whole friend group:

like, go read them, they're all iconic in their own way πŸ’œ


and that's the page babes ✨ it lives in ./drivers/power/supply, it's dated October 2026, and it's bq257xx_pro...is_writeable(9) all the way down. mwah πŸ’‹

πŸ“¦ where this page comes from