mma9551_write_config_word(9)

💫 NAME 💫

mma9551_write_config_word — ok so bestie, this one writes 1 config word, that's literally the whole vibe ✨

---

🎀 SYNOPSIS 🎀

int mma9551_write_config_word (struct i2c_client *client , u8 app_id ,
u16 reg , u16 val );

---

🦋 ARGUMENTS 🦋

• client — the I2C client, your lil connection to the device 🫶
• app_id — Application ID, telling the platform which app we're talking to
• reg — Application register, the exact spot we're poking
• val — Value to write, the payload, the main character of this whole operation 👑

---

🌸 DESCRIPTION 🌸

So the way this works: it writes one configuration word to the device using the MMA955xL command format 💅 Commands to the MMA955xL platform are built as a write followed by one or more reads — that's just how it rolls, no cap.

⚠️ Locking note, and this one matters fr fr: this function must be called with the device lock held. Locking is not handled inside the function — it does not do that for you 🙈 Callers should make sure they serialize access to the HW themselves. Like, do your own homework on this one, bestie.

---

⭐ RETURN ⭐

0 on success, and a negative value on failure 😭 that's it, that's the tea.

---

🔥 SEE ALSO 🔥

Kernel file ./drivers/iio/accel/mma9551_core.c — go read it, iykyk 📖

The whole friend group, in order:

• mma9551_read_config_byte(9)
• mma9551_write_config_byte(9)
• mma9551_read_status_byte(9)
• mma9551_read_config_word(9)
• mma9551_read_status_word(9)
• mma9551_read_config_words(9)
• mma9551_read_status_words(9)
• mma9551_write_config_words(9)
• mma9551_update_config_bits(9)
• mma9551_gpio_config(9)
• mma9551_read_version(9)
• mma9551_set_device_state(9)
• mma9551_set_power_state(9)
• mma9551_sleep(9)
• mma9551_read_accel_chan(9)
• mma9551_read_accel_scale(9)
• mma9551_app_reset(9)

---

🌈 aaaand that's the page! brought to you from ./drivers/iio/accel, stamped October 2026 — mwah, love you, go hold that lock 💖👑