STRUCT MHI_EVENT_CONFIG(9)

📦 version 7.3.1, in nixpkgs unstable

💖 struct mhi_event_config — the event ring config glow-up 💖

okay so this is from the Kernel API Manual (section 9, bestie, the kernel section), and it's literally the blueprint for a controller's event ring. it's giving "settings page for one very specific ring" and honestly? iconic. let's get into it 🎀

✨ NAME ✨

struct mhi_event_config — the event ring configuration structure for controller 🦋

like, this whole struct is the vibe check for how an event ring behaves. num_elements, irqs, priorities, the works. no cap, every field matters.

🌸 SYNOPSIS 🌸

struct mhi_event_config {
    u32 num_elements;
    u32 irq_moderation_ms;
    u32 irq;
    u32 channel;
    u32 priority;
    enum mhi_db_brst_mode mode;
    enum mhi_er_data_type data_type;
    bool hardware_event;
    bool client_managed;
    bool offload_channel;
 };

look at her. ten fields. every single one of them copy-pasted exactly, because we do not mess with kernel structs 💅

🫶 Members 🫶

the big four (numbers & irqs)

  • num_elements — literally how many elements can be queued to this ring. that's the capacity, bestie. that's how much room she has to hold stuff 📦
  • irq_moderation_ms — delays the irq so extra events can get aggregated together. yes, it's a delay, it's on purpose, it's batching 🧚 this is a "wait a sec, let more of them pile up" situation.
  • irq — the IRQ that's associated with this ring. the actual interrupt line, fr fr ⚡
  • channel — the dedicated channel number. and here's the fun part: U32_MAX means it's a non-dedicated ring. so if you see U32_MAX chilling there, she's not tied to any one channel 💀
  • priority — priority of this ring. and the manpage literally says "Use 1 for now" 😭 so yeah, just put 1. it's giving placeholder-that-became-canon.

the enum girlies

  • mode — the doorbell mode. that's enum mhi_db_brst_mode territory, iykyk 🔔
  • data_type — the type of data this ring will process. that's enum mhi_er_data_type. she's picky about what she handles 🌈

the three bool besties (all bool, all lowercase, all important)

  • hardware_event — this ring is associated with hardware channels. so: yes she is a hardware event ring, or no she isn't 🖥️
  • client_managed — this ring is client managed. the client's got the aux, she's running her own show 👑
  • offload_channel — this ring is associated with an offloaded channel. omg offload, we love a delegating queen 🍓
lowkey the whole point: you fill out this struct so the controller knows exactly what kind of event ring it's dealing with. flags on, flags off, numbers in the right slots. that's the gig 🫡

💜 SEE ALSO 💜

the whole friend group, no one left out 🫶 the source of truth here is Kernel file ./include/linux/mhi.h, and here's literally all of it:

k that's the page!! 💅 this came out of ./include/linux, dated October 2026 — so yes, future-dated manpage energy, we stan a timeless icon ⭐ go configure your event rings responsibly bestie, and remember: priority stays at 1 for now. periodt. 🎀🌈

📦 where this page comes from