qcom_labibb_...k_ocp_status(9)

💅 qcom_labibb_check_ocp_status(9)

okay so bestie, welcome to the Kernel API Manual ✨ — today's main character is qcom_labibb_check_ocp_status, and honestly? She's a vibe check for your regulator. Let's get into it 🫶

🌸 NAME 🌸

qcom_labibb_check_ocp_status — check the Over-Current Protection status 🔥

✨ SYNOPSIS ✨

int qcom_labibb_check_ocp_status (struct labibb_regulator *vreg );

🎀 ARGUMENTS 🎀

• vreg — the main driver structure, aka the whole personality of this operation 💖

🦋 DESCRIPTION 🦋

So here's the tea ☕ — this function goes and peeks at the STATUS1 register, specifically hunting for the VREG_OK bit 👀. And like, if that bit is set? That means there's no Over-Current event. Iconic. No drama, no nothing, we love a calm register 🧚

👑 RETURN 👑

• Zero — no over-current happening, all good bestie 😌
• 1 — we're in over-current, oh no 😭
• a negative number — that's an error, something went sideways 💀

🌈 SEE ALSO 🌈

Kernel file ./drivers/regulator/qcom-labibb-regulator.c 📁

• qcom_labibb_ocp_recovery_worker(9)
• qcom_labibb_ocp_isr(9)
• qcom_labibb_check_sc_status(9)
• qcom_labibb_sc_recovery_worker(9)
• qcom_labibb_sc_isr(9)

and that's the whole page, periodt 💅 this lil gem lives over in ./drivers/regulator, dated October 2026 — go off, queen 👑💖