devm_spi_mem_dirmap_create(9)

📦 version 7.3.1, in nixpkgs unstable

💅 devm_spi_mem_dirmap_create(9) — like, the Kernel API Manual, bestie ✨

Okay so this is devm_spi_mem_dirmap_create(9), straight out of the Kernel API Manual, and honestly? It's giving "resource-managed era" and we're obsessed. 🎀

🌸 NAME 🌸

devm_spi_mem_dirmap_create — okay so what it does is it creates a direct mapping descriptor, right? And then it attaches it to a device. That's the whole vibe. 💖

✨ SYNOPSIS ✨

struct spi_mem_dirmap_desc * devm_spi_mem_dirmap_create (struct device
*dev , struct spi_mem *mem , const struct spi_mem_dirmap_info *info );

Like, it returns a struct spi_mem_dirmap_desc * and takes those three args. No cap. 🫶

🦋 ARGUMENTS 🦋

  • dev — the device that the dirmap desc is gonna get attached to. It's the main character here, fr. 👑
  • mem — the SPI mem device that this direct mapping should be created for. Like, whose map is this? This one's. 💫
  • info — the direct mapping information. All the deets live here. 📋

🌈 DESCRIPTION 🌈

So this is the devm_ variant of the spi_mem_dirmap_create function — iykyk, the devm_ prefix means it's the device-managed one. 💅 If you want the full lore, go see spi_mem_dirmap_create for more details, because this page is not about to retell the whole story. ✨

⭐ RETURN ⭐

You get a valid pointer in case of success 💖, and ERR_PTR otherwise 😭. That's it, that's the deal.

🔥 SEE ALSO 🔥

Kernel file ./drivers/spi/spi-mem.c — go read it, bestie, it's iconic. 🧚

💀 reminder bestie: the devm_ version ties the descriptor's lifetime to dev, so like... don't go freeing it yourself and then letting the device cleanup hit it too. Resource-managed means resource-managed. 🙈 (That's just the whole point of the devm_ variant, see spi_mem_dirmap_create for the deets.)

And that's the tea 🍓 — this cutie came from ./drivers/spi, dated October 2026, and it's filed under devm_spi_mem_dirmap_create(9). Slay. 💜🦋

📦 where this page comes from