fsl_mc_bus_match(9)
π fsl_mc_bus_match(9) β the Kernel API Manual page, but make it make sense
okay so this is a page from the Kernel API Manual, and it's genuinely short, so bestie you have zero excuses not to read it. it's about fsl_mc_bus_match, one little callback that answers the question "hey, does this device go with this driver?" π
β¨ NAME β¨
fsl_mc_bus_match β the device-to-driver matching callback, literally that's its whole job π¦
β¨ SYNOPSIS β¨
int fsl_mc_bus_match (struct device *dev , const struct device_driver
*drv );
β¨ ARGUMENTS β¨
devβ the fsl-mc device we're trying to match against πdrvβ the device driver we're searching through, looking for matching fsl-mc object type structures π
β¨ DESCRIPTION β¨
So the way this works: it returns 1 on success, and 0 otherwise. that's it. that's the whole function. no cap. πβ¨
lowkey the most important thing on this page is the return value β1means yes/success,0means nope. don't mix them up bestie, the vibes will be off π
β¨ SEE ALSO β¨
go look at these if you want the full lore, iykyk π
- the kernel file
./drivers/bus/fsl-mc/fsl-mc-bus.c struct fsl_mc(9)struct fsl_mc_addr_translation_range(9)mc_get_version(9)fsl_mc_get_version(9)fsl_mc_device_remove(9)
πΈ and that's the page!! sourced straight from ./drivers/bus/fsl-mc, dated October 2026 β go drink some water and go read fsl-mc-bus.c bestie, mwah π«Άπ
π¦ 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