max_contamin..._contaminant(9)

okay so bestie, this is max_contamin..._contaminant(9) from the Kernel API Manual — let's get into it 💖

🫶 NAME 🫶

• max_contaminant_is_contaminant — tests if CC was toggled due to a contaminant. that's the whole assignment, no cap ✨

✨ SYNOPSIS ✨

bool max_contaminant_is_contaminant (struct max_tcpci_chip *chip , bool
disconnect_while_debounce , bool *cc_handled );

🧚 ARGUMENTS 🧚

• chip — handle to a struct max_tcpci_chip. ur main character struct, basically 🫶
• disconnect_while_debounce — whether the disconnect was detected when CC pins were debouncing. debounce era, iykyk 🌸
• cc_handled — returns whether or not update to CC status was handled here. not me being obsessed with this bool pointer, it literally tells you if the CC-status update got handled right here 🎀

🌸 DESCRIPTION 🌸

okay so the vibe check: this function determines if a contaminant was detected. that's it, that's the plot 🔥

🔥 RETURN 🔥

true if a contaminant was detected, false otherwise. cc_handled gets updated to reflect whether or not further CC handling is required — so yeah, it's doing double duty, highkey iconic, periodt 💅

🦋 SEE ALSO 🦋

Kernel file ./drivers/usb/typec/tcpm/tcpci_maxim.h — the reference ate, go look 👀✨

mwah 💋 this cutie is sourced from ./drivers/usb/typec/tcpm, dated October 2026, and it's the max_contamin..._contaminant(9) page. periodt, love that for us 🎀