__mdiobus_c4...dify_changed(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… __mdiobus_c45_modify_changed β€” Kernel API Manual ✨

okay so bestie, welcome to the Kernel API Manual entry for __mdiobus_c45_modify_changed(9) πŸ‘‘ this is the unlocked version of the mdiobus_modify function, and yes she has main character energy but she also has rules, so let's get into it 🫢


✨ NAME ✨

__mdiobus_c45_modify_changed β€” the Unlocked version of the mdiobus_modify function πŸ”“πŸ’–


🌸 SYNOPSIS 🌸

int __mdiobus_c45_modify_changed (struct mii_bus *bus , int addr , int
devad , u32 regnum , u16 mask , u16 set );

πŸŽ€ ARGUMENTS πŸŽ€

  • bus β€” the mii_bus struct, she's the whole vibe holder fr
  • addr β€” the phy address
  • devad β€” device address to read
  • regnum β€” register number to modify, like the exact little spot we're messing with
  • mask β€” bit mask of bits to clear 🧹
  • set β€” bit mask of bits to set πŸͺ„

πŸ¦‹ RETURN πŸ¦‹

  • Returns 1 if the register was modified πŸ”₯
  • Returns 0 if no change was needed (respect, lowkey)
  • Returns a negative value on any error condition 😭

🌈 DESCRIPTION 🌈

So the way this works is: read, modify, and if there's any change, write the register value back to the device. That's literally the whole loop, she ate πŸ’…

Any error returns a negative number 🫢


πŸ’€ NOTE πŸ’€

MUST NOT be called from interrupt context. not me stressing this, but please, bestie, do not do it πŸ™ˆ

⭐ SEE ALSO ⭐

Kernel file ./drivers/net/phy/mdio_bus.c πŸ“ and all her friends:


okay that's the whole page, ily, go forth and modify responsibly πŸ§šπŸ’œ

source: ./drivers/net/phy Β· October 2026 Β· __mdiobus_c4...dify_changed(9) β€” mwah, see u in the next manpage bestie πŸ’‹πŸŽ€

πŸ“¦ where this page comes from