geni_i2c_gp...i_desc_unmap(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

geni_i2c_gpi_multi_desc_unmap β€” bestie, this one unmaps DMA buffers after multi message TX transfers, okurrr πŸ’–

So this is a section 9 kernel API manual page (yes, the header up top just calls it geni_i2c_gp...i_desc_unmap(9) because kernel manpage headers love to truncate and be mysterious πŸ™ˆ), and the whole vibe is: you already did your multi-message TX thing, now clean up the DMA mappings. Iconic, necessary, lowkey underrated πŸŽ€


✨ SYNOPSIS ✨

void geni_i2c_gpi_multi_desc_unmap (struct geni_i2c_dev *gi2c , struct
i2c_msg msgs[] , struct gpi_i2c_config *peripheral );

It returns void, so there is literally nothing to check. No return value, no drama, no "did it work" moment 😌✨


🌸 ARGUMENTS 🌸

  • gi2c β€” the I2C dev handle 🫢 that's your whole device situation right there.
  • msgs β€” array of I2C messages πŸ’Œ like, plural, the whole lineup, one big friend group of messages.
  • peripheral β€” pointer to gpi_i2c_config πŸ¦‹ this is your peripheral's config bestie, she knows things.

πŸ‘€ SEE ALSO πŸ‘€

  • Kernel file ./drivers/i2c/busses/i2c-qcom-geni.c β€” that's where the source lives, go read it, iykyk πŸ“–
  • struct geni_i2c_gpi_multi_desc_xfer(9) β€” the actual transfer bestie, the one who does the doing πŸ’…
  • geni_i2c_gpi_multi_xfer_timeout_handler(9) β€” the one who shows up when things take too long 😭⏰

🧚 SIGN-OFF 🧚

This little gem comes to you from ./drivers/i2c/busses, dated October 2026 β€” slay, periodt, go unmap those buffers responsibly πŸ’œπŸŒˆβ­

πŸ“¦ where this page comes from