cdns_i2c_func(9)

📦 version 7.3.1, in nixpkgs unstable

💅 cdns_i2c_func — from the Kernel API Manual, bestie

okay so real talk, this is a page from the Kernel API Manual and it's about one lil function called cdns_i2c_func. it's not a whole essay, it's literally one job: you hand it an adapter, it tells you what the driver can do. that's it. that's the whole vibe. 🦋

✨ NAME ✨

cdns_i2c_func — returns the supported features of the I2C driver

like, it's giving "capability report." you ask, it answers in bits. no cap. 🔥

🌸 SYNOPSIS 🌸

u32 cdns_i2c_func (struct i2c_adapter *adap );

bestie look at the return type: u32. that's a 32 bit value, which means up to 32 lil feature flags could theoretically live in there. iconic bit-packing behavior honestly. 👑

🎀 ARGUMENTS 🎀

  • adap — pointer to the i2c_adapter structure. that's the thing you're asking about. hand it over and it'll do its thing. 🫶

⭐ RETURN ⭐

a 32 bit value, where each bit corresponds to a feature. so like… bit 0 is one thing, bit 1 is another thing, and you check them individually. don't read it as a plain number, read it as a vibe check of features. iykyk. 💫

ngl, the manpage doesn't spell out which bit is which — it just says each bit = a feature. so don't go inventing meanings, bestie. 🙈

🌈 SEE ALSO 🌈

so many friends in the same neighborhood, all living in the kernel file ./drivers/i2c/busses/i2c-cadence.c 💖

and that's the whole page, bestie!! go forth and read your feature bits 💅✨

sign-off time 🎀 this one lives in ./drivers/i2c/busses, dated October 2026, and the page itself is cdns_i2c_func(9). mwah. 💜

📦 where this page comes from