i3c_device_g...ed_xfer_mode(9)

📦 version 7.3.1, in nixpkgs unstable

💅 i3c_device_g...ed_xfer_mode(9) 💅

okay so bestie, welcome to the Kernel API Manual ✨ — this one's a teeny tiny function page and honestly? it's giving "small but mighty." the full title got truncated in the header (cute!), but it's i3c_device_get_supported_xfer_mode in all its glory 🎀

✨ NAME ✨

i3c_device_get_supported_xfer_mode — returns the supported transfer mode by connected master controller 💖

like, it literally just asks the master "hey babe, what transfer modes do you speak?" and reports back. no cap.

🌸 SYNOPSIS 🌸

u32 i3c_device_get_supported_xfer_mode (struct i3c_device *dev );

that's it. one function, one argument, returns a u32. simple, clean, iconic 👑

🦋 ARGUMENTS 🦋

  • dev — the I3C device 🫶 (yes, that's the whole description. she's lowkey mysterious like that)

🌈 RETURN 🌈

returns a bit mask of the supported transfer modes 💅 — and the bit position is defined at enum i3c_hdr_mode, iykyk ⭐

so fr fr: don't just read the number, check which bits are set, because those positions are mapped out in enum i3c_hdr_mode. that's where the lore lives 🔥

🎀 SEE ALSO 🎀

kernel file ./drivers/i3c/device.c 📁 — go read her, she's the main character:

a whole friend group of functions honestly, obsessed 💜

and that's the whole vibe check bestie 🌸 this page came from ./drivers/i3c and is dated October 2026, and yeah the footer still says i3c_device_g...ed_xfer_mode(9) because the title is too long to fit and honestly? relatable 😭💀 slay, go forth and read your bit masks 🧚‍♀️💖

📦 where this page comes from