qcom_labibb_ocp_isr(9)
π qcom_labibb_ocp_isr(9) π
okay so this is a page from the Kernel API Manual, and honestly? it's giving "tiny function, big responsibility." we're talking about the interrupt routine that handles OverCurrent Protection, aka OCP, aka the moment your regulator's current draw goes feral. let's get into it bestie π«Ά
β¨ NAME β¨
qcom_labibb_ocp_isr β the interrupt routine for OverCurrent Protection, no cap π
πΈ SYNOPSIS πΈ
irqreturn_t qcom_labibb_ocp_isr (int irq , void *chip );
that's the whole signature, queen. two args, one irqreturn_t coming back at you β¨
π ARGUMENTS π
irqβ the interrupt number. literally just which IRQ we're talking about π₯chipβ the main driver structure. the big one. the main character π
π¦ DESCRIPTION π¦
so here's the vibe: Over Current Protection (OCP) will signal to the client driver that an over-current event has happened, and then it'll schedule a recovery worker. that's the whole job of this ISR β flag it, hand it off, done. π§
and now the part you actually need to remember, bestie: disabling and eventually re-enabling the regulator is expected to be done by the driver. that's on you, not on this function. the reason is lowkey important β some hardware may be triggering an over-current condition only at first initialization, or it may be expected only for a very brief amount of time, after which the attached hardware may be expected to stabilize its current draw. so yeah, hardware is dramatic, but the point stands π
ngl this is the kind of nuance people skip and then wonder why their regulator is acting up. read it twice. iykyk π
β RETURN β
IRQ_HANDLEDβ for success πIRQ_NONEβ for failure π
that's it, that's the whole return contract π
π₯ SEE ALSO π₯
- the kernel file
./drivers/regulator/qcom-labibb-regulator.cβ go read the source, it's iconic π qcom_labibb_check_ocp_status(9)qcom_labibb_ocp_recovery_worker(9)qcom_labibb_check_sc_status(9)qcom_labibb_sc_recovery_worker(9)qcom_labibb_sc_isr(9)
the whole labibb squad, fr fr π
okay and for the cute sign-off: this lil page comes from ./drivers/regulator, dated October 2026, and it's the qcom_labibb_ocp_isr(9) page from the Kernel API Manual. slay, go protect some currents π
β¨π
π¦ 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