STRUCT SBTSI_I3C_PRIV(9)
π struct sbtsi_i3c_priv(9) π
okay so this is a page from the Kernel API Manual, bestie, and we're talking about struct sbtsi_i3c_priv β no cap, it's the per-device state for I3C SBTSI, and it's literally carrying DMA-safe buffers in it. main character struct energy fr fr π
β¨ NAME β¨
struct sbtsi_i3c_priv β per-device state for I3C SBTSI (includes DMA-safe buffers)
like... it holds the state, and it holds the buffers, and it does both at once. iconic behavior π
πΈ SYNOPSIS πΈ
struct sbtsi_i3c_priv {
struct sbtsi_data data;
u8 tx[2];
u8 rx;
};
three members. that's it. that's the whole vibe. π¦
π Members π
dataβ the public device state, exposed viadev_set_drvdata. this is the one everybody else gets to see, the extrovert of the struct π«Άtxβ the outgoing I3C bytes, and no they're not optional: this isDMA_TO_DEVICEterritory.[0]is the register address,[1]is the value. two bytes, one job, slayed β¨rxβ the incoming I3C data byte, coming at youDMA_FROM_DEVICE. single byte, huge responsibility π
ok real talk though β those DMA directions are load-bearing.txis DMA_TO_DEVICE,rxis DMA_FROM_DEVICE, and the whole "DMA-safe buffers" thing in the NAME line is not decoration. don't be out here messing with that π
π SEE ALSO π
- Kernel file
./drivers/misc/amd-sbi/tsi-core.hβ go read it, iykyk π
and that's the whole page, bestie!! source is ./drivers/misc/amd-sbi and the date stamp says October 2026, so like... mark your calendar or whatever ποΈπ mwah, stay DMA-safe βπ§π
π¦ 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