geni_i2c_gp...i_desc_unmap(9)
π 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 togpi_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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms