max77759_maxq_command(9)

💅 max77759_maxq_command(9) 💅

okay so bestie, welcome to the Kernel API Manual ✨ — yes that's the whole manual name, we're fancy here — and today's main character is max77759_maxq_command, which is literally just "send a MaxQ command, then sit there and wait for the response and all the data that comes with it" 🫶. No cap, that's the whole vibe.

---

🌸 NAME 🌸

max77759_maxq_command — issue a MaxQ command and wait for the response and associated data

like it sends the thing, then it waits, because we do not ghost our hardware 👑✨

---

🎀 SYNOPSIS 🎀

int max77759_maxq_command (struct max77759 *max77759 , const struct
max77759_maxq_command *cmd , struct max77759_maxq_response *rsp );

look at that signature. iconic. three args, one int coming back at you 💅

---

🦋 ARGUMENTS 🦋

• max77759 — the core max77759 device handle. your main character device, fr fr 🌟
• cmd — the command to be sent. this is the whole point of the function, ngl 📨
• rsp — any response data associated with the command gets copied in here; it can be NULL if the command has no response (other than the ACK). so like, no data? no problem, pass NULL and vibe 😌

---

⭐ RETURN ⭐

0 on success, a negative error number otherwise. that's it, that's the check — zero means slay, negative means 😭

---

🌈 SEE ALSO 🌈

• Kernel file ./include/linux/mfd/max77759.h enum max77759_chgr_chgin_dtls_status(9)
• enum max77759_chgr_bat_dtls_states(9)
• enum max77759_chgr_chg_dtls_states(9)
• struct max77759(9)
• struct max77759_maxq_command(9)
• struct max77759_maxq_response(9)

go read those too, iykyk 🧚‍♀️💜

---

real talk: don't forget to actually check that return value. a negative error number is not a vibe check you want to fail 🙈

---

and that's the page, bestie 🍓 — brought to you by the source/version line ./include/linux/mfd, dated October 2026, which is giving very much "signed, sealed, delivered" energy. mwah 💋✨