rpr0521_set_power_state(9)
β¨ rpr0521_set_power_state(9) β¨
okay so this is a page straight out of the Kernel API Manual, bestie β like, the actual kernel docs, not a vibe. sit down, hydrate, and let's get into it π«Ά
πΈ NAME πΈ
rpr0521_set_power_state β handles runtime PM state and sensors enabled status
that's it, that's the whole gig. runtime PM state + which sensors are enabled? she's doing both. multitasking icon π
π¦ SYNOPSIS π¦
int rpr0521_set_power_state (struct rpr0521_data *data , bool on , u8 device_mask );
look at her. three args, returns an int, no cap. copy it exactly if you're writing code, okay?? character for character, bestie π
π ARGUMENTS π
dataβ the rpr0521 device private data. like, her personal little diary of device info πonβ the state to be set for the devices indevice_mask. on or off, pick a lane β¨device_maskβ bitmask specifying for which device we need to update on state. so it's giving "which ones, specifically" energy π₯
π DESCRIPTION π
okay this is the important part, so listen up fr fr π
Calls for this function must be balanced so that each ON should have matching OFF.
not me being dramatic but if you don't balance these, pm usage_count gets out of sync. that is a real sentence and a real consequence. no vibes-based power management allowed π
so: every ON gets an OFF. every OFF gets an ON. it's a two-way street, it's a situationship with rules, it's balance π
π SEE ALSO π
- Kernel file
./drivers/iio/light/rpr0521.cβ go read the source, iykyk π
and that's the whole page, bestie!! π this one comes to you from ./drivers/iio/light in the October 2026 edition of the Kernel API Manual β mwah, stay balanced, slay, periodt πβ¨π§
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms