cs_dsp_mock_regmap_is_dirty(9)

💅 cs_dsp_mock_regmap_is_dirty — the Kernel API Manual page you didn't know you needed

okay bestie, welcome to the Kernel API Manual, section 9, and today's main character is cs_dsp_mock_regmap_is_dirty(9). she's a little test helper and honestly she's iconic for it 🎀

---

✨ NAME ✨

cs_dsp_mock_regmap_is_dirty — literally just testing for dirty registers in the cache. that's the whole vibe check 🫶

---

🌸 SYNOPSIS 🌸

bool cs_dsp_mock_regmap_is_dirty (struct cs_dsp_test *priv , bool
drop_system_regs );

like, copy it exactly, don't @ me 😭

---

🦋 ARGUMENTS 🦋

• priv — Pointer to struct cs_dsp_test object. your whole little test world lives in here ✨
• drop_system_regs — if this is true, the DSP system regs get dropped from the cache before the dirty check happens. so like, they're not invited to the party anymore 💅

---

💜 DESCRIPTION 💜

okay so the whole thing is: every register that's expected to be written must have already been dropped from the cache. and yes, the DSP system registers can be dropped by passing drop_system_regs == true 👑

now the plot twist 🙈 — if any unexpected registers got written, there are still dirty entries chillin' in the cache, and a cache sync will cause a write. so that's your red flag right there, no cap 🔥

---

⭐ RETURN ⭐

• true — there were dirty entries 😭
• false — there were not, we're clean, we ate 🍓

---

🧚 SEE ALSO 🧚

go read these too, they're the friend group:

• Kernel file ./drivers/firmware/cirrus/test/cs_dsp_mock_regmap.c
• cs_dsp_mock_regmap_drop_range(9)
• cs_dsp_mock_regmap_drop_regs(9)
• cs_dsp_mock_regmap_drop_bytes(9)
• cs_dsp_mock_regmap_drop_system_regs(9)
• cs_dsp_mock_regmap_init(9)

---

ngl bestie, read the source file before you go poking at registers — it's giving required reading 📚

---

and that's the page!! mwah 💖 this one shipped from ./drivers/firmware/cirrus/test, dated October 2026, and it's brought to you by the Kernel API Manual — cs_dsp_mock_regmap_is_dirty(9), periodt 💅🌈