ENUM GENI_SE_XFER_MODE(9)
π enum geni_se_xfer_mode(9) β from the Kernel API Manual, bestie π«Ά
okay so picture this: it's giving "Kernel API Manual" energy, and the star of the show is enum geni_se_xfer_mode, which is literally just the list of transfer modes that Serial Engines support β¨. that's it. that's the whole vibe. no cap.
π NAME π
enum geni_se_xfer_mode β the transfer modes supported by Serial Engines, periodt π
πΈ SYNOPSIS πΈ
enum geni_se_xfer_mode {
GENI_SE_INVALID ,
GENI_SE_FIFO ,
GENI_SE_DMA ,
GENI_GPI_DMA
};
π¦ CONSTANTS π¦
bestie, let me walk you through the cast π
GENI_SE_INVALIDβ the invalid mode. it's giving "not it" π this one is literally just here to say nope, not valid.GENI_SE_FIFOβ FIFO mode! data gets transferred with the SE FIFO by the programmed IO method. old school, but she works πGENI_SE_DMAβ Serial Engine DMA mode. data is transferred with the SE by the DMAengine that's internal to the SE. self-sufficient queen πGENI_GPI_DMAβ GPI DMA mode. data is transferred using a DMAengine configured by a firmware residing on a GSI engine. and here's the tea β: this DMA name is interchangeably used as GSI or GPI, and those seem to imply the same DMAengine. iykyk π§
π₯ SEE ALSO π₯
go check out the Kernel file ./include/linux/soc/qcom/geni-se.h, plus these iconic faves π:
struct geni_se(9)geni_se_read_proto(9)geni_se_setup_m_cmd(9)geni_se_setup_s_cmd(9)geni_se_cancel_m_cmd(9)geni_se_cancel_s_cmd(9)geni_se_abort_m_cmd(9)geni_se_abort_s_cmd(9)geni_se_get_tx_fifo_depth(9)geni_se_get_tx_fifo_width(9)geni_se_get_rx_fifo_depth(9)
and that's the whole page, bestie π this lil' gem lives over in ./include/linux/soc/qcom, dated October 2026 β so yeah, she's from the future and she ate π
β¨ slay! π
π¦ 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