spi_test_run_test(9)

✨ spi_test_run_test(9) ✨

okay so bestie, buckle up, because this is a page from the Kernel API Manual and it's literally about running one single SPI test and doing it properly 💅

🎀 NAME 🎀

spi_test_run_test — run an individual spi_test including all the relevant iterations on: length and buffer alignment 🦋

like, not just a test. the whole test, with every length variation and every alignment variation it needs. the way that this function is thorough?? obsessed. 😭

---

🌸 SYNOPSIS 🌸

int spi_test_run_test (struct spi_device *spi , const struct spi_test
*test , void *tx , void *rx );

yes the signature is exactly that, spacing and all, don't come for me, I'm just the messenger 🫶

---

💖 ARGUMENTS 💖

• spi — the spi_device that we're gonna send the messages to 📨
• test — the actual test we need to execute, like this is the main character of the whole operation 👑
• tx — the tx buffer that was allocated for the test sequence 🍓
• rx — the rx buffer that was allocated for the test sequence 🍓

like yeah, both buffers are handed to you, pre-allocated, no cap. you're not malloc-ing anything here, that's not your job, that's somebody else's era 💀

---

⭐ RETURN ⭐

status code of spi_sync or other failures 🌈

so basically: you get back the status of spi_sync, or some other failure. either way it's a status code, and you should check it, bestie, like please, fr fr 🙈

---

🦋 SEE ALSO 🦋

• Kernel file ./drivers/spi/spi-loopback-test.c
• spi_test_execute_msg(9)
• spi_test_run_tests(9)

go read those if you wanna know how the pieces fit together, iykyk 🧚

---

and that's the vibe check, bestie ✨ this page came from ./drivers/spi, dated October 2026, and it's spi_test_run_test(9) — slay, go run some tests 💜🎀