mhi_notify(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ mhi_notify(9) ✨

okay so this is mhi_notify, straight out of the Kernel API Manual, section 9, and it's literally the function that tells your MHI client driver "hey bestie, here's the tea on your client device's status" πŸ‘€πŸ’…


🌸 NAME 🌸

mhi_notify β€” notify the MHI client driver about client device status πŸ’–


πŸŽ€ SYNOPSIS πŸŽ€

void mhi_notify (struct mhi_device *mhi_dev , enum mhi_callback cb_reason );

that's it. that's the whole thing. returns void, so like, no receipts, no return value, she just does her thing and leaves πŸ¦‹


πŸ’œ ARGUMENTS πŸ’œ

  • mhi_dev β€” the MHI device instance, aka the main character of this whole operation πŸ‘‘
  • cb_reason β€” the MHI callback reason, aka why we're all gathered here today πŸŽ€

🌈 SEE ALSO 🌈

bestie, this list is LONG, so buckle up. we got the whole MHI cinematic universe over here, starting with the header file itself:

Kernel file ./include/linux/mhi.h

then the enums:

  • enum mhi_callback(9)
  • enum mhi_flags(9)
  • enum mhi_device_type(9)
  • enum mhi_ch_type(9)
  • struct mhi_buf(9)
  • struct image_info(9)
  • struct mhi_link_info(9)
  • enum mhi_ee_type(9)
  • enum mhi_state(9)
  • enum mhi_ch_ee_mask(9)
  • enum mhi_er_data_type(9)
  • enum mhi_db_brst_mode(9)
  • struct mhi_channel_config(9)
  • struct mhi_event_config(9)
  • struct mhi_controller_config(9)
  • struct mhi_controller(9)
  • struct mhi_device(9)
  • struct mhi_result(9)
  • struct mhi_driver(9)

and the functions, oh the functions 😭:

like, that's the entire friend group, no cap 🫢


ngl, that's everything this page gives us β€” no options, no exit statuses, no warnings, no bugs section. she's a short queen and she knows it ✨

and that's the whole page, periodt πŸ’… this cutie lives in the kernel source tree at ./include/linux, and the lovely folks stamped her with October 2026 as the date πŸŽ€ go forth and notify, bestie πŸ’–πŸ‘‘

πŸ“¦ where this page comes from