check_plugged_state_change(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– check_plugged_state_change(9)

okay so bestie, this page is from the Kernel API Manual, and it's giving β€œone tiny kernel function with a very specific job.” The function is check_plugged_state_change, and the whole plot is spotting when an MC object's plugged state switches up. ✨


🌸 NAME

check_plugged_state_change β€” Check change in an MC object's plugged state. πŸ’…

πŸ¦‹ SYNOPSIS

void check_plugged_state_change (struct fsl_mc_device *mc_dev , struct
       fsl_mc_obj_desc *obj_desc );

πŸŽ€ ARGUMENTS

  • mc_dev β€” pointer to the fsl-mc device for a given MC object. It's the device side of the situation, iykyk. 🫢
  • obj_desc β€” pointer to the MC object's descriptor in the MC. Basically the MC's lil info card for the object. πŸͺͺ✨

✨ DESCRIPTION

If the plugged state has changed from unplugged to plugged, the fsl-mc device is bound to the corresponding device driver. That's the β€œwelcome to the driver, bestie” moment. πŸ’–

If the plugged state has changed from plugged to unplugged, the fsl-mc device is unbound from the corresponding device driver. That's the β€œokay bye, driver” moment. πŸ˜­πŸ‘‹

No cap, that's the whole function vibe: state change in, bind/unbind out. πŸ¦‹

πŸ”₯ SEE ALSO

Kernel file ./drivers/bus/fsl-mc/dprc-driver.c β€” go read the whole squad. πŸ‘‘


xoxo bestie πŸ’– this page's source/version corner is ./drivers/bus/fsl-mc, dated October 2026, and it's the check_plugged_state_change(9) page. Go check those plugged-state changes, respectfully. 🫢🌈

πŸ“¦ where this page comes from