ltq_mm_apply(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

Hey bestie πŸ’– welcome to the ltq_mm_apply(9) page, straight outta the Kernel API Manual. This one is short, sweet, and lowkey crucial if you're messing with EBU GPIO stuff. Let's get into it ✨

πŸŽ€ NAME πŸŽ€

ltq_mm_apply β€” write the shadow value to the ebu address. That's the whole name, no cap.

πŸ¦‹ SYNOPSIS πŸ¦‹

Here's the signature, bestie:

void ltq_mm_apply (struct ltq_mm *chip );

🌸 ARGUMENTS 🌸

  • chip β€” pointer to our private data structure. That's the vibe: it points at our own private-data situation 🫢

πŸ’… DESCRIPTION πŸ’…

Okay so what it does: writes the shadow value to the EBU to set the gpios. Iconic little helper, fr fr.

And yes, we need to set the global EBU lock to make sure that PCI/MTD don't break. Non-negotiable.

Do not skip the global EBU lock, bestie β€” PCI/MTD can break and that is not the vibe πŸ’€

🌈 SEE ALSO 🌈


Catch you later πŸ’… this page came from source/version ./drivers/gpio, dated October 2026, and it's literally the ltq_mm_apply(9) manual page. Slay πŸŽ€

πŸ“¦ where this page comes from