ksz_parent_mdio_write(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ksz_parent_mdio_write(9) β€” like, the Kernel API Manual bestie ✨

okay so bestie, welcome to the Kernel API Manual page for ksz_parent_mdio_write β€” yes that whole name, we're saying it with our chest 🫢


🌸 NAME 🌸

ksz_parent_mdio_write β€” literally just writes data to a PHY register on the parent MDIO bus. that's the whole vibe, no cap πŸ’…


✨ SYNOPSIS ✨

int ksz_parent_mdio_write (struct mii_bus *bus , int addr , int regnum ,
u16 val );

πŸŽ€ ARGUMENTS πŸŽ€

  • bus β€” the MDIO bus structure. the actual bus, the main character 🌈
  • addr β€” PHY address on the parent MDIO bus. where we're headed, iykyk
  • regnum β€” the register number you're writing to. pick your fave πŸ”₯
  • val β€” the value going into that PHY register. the payload, the moment πŸ’–

πŸ¦‹ DESCRIPTION πŸ¦‹

so this function is giving direct write operation on the parent MDIO bus for accessing PHY registers. and the way it does it? it bypasses SPI or I2C entirely β€” not me skipping the whole middleman 😭 β€” and uses the parent MDIO bus to modify the PHY register values at the specified address. lowkey iconic, highkey efficient ✨


⭐ RETURN ⭐

0 on success, or a negative error code on failure. slay when it works, and when it doesn't... well, negative error code. we move πŸ₯²


πŸ‘‘ SEE ALSO πŸ‘‘

bestie go look at the Kernel file ./drivers/net/dsa/microchip/ksz_common.c β€” that's the source, the origin story 🫢

and then the whole friend group of related functions, in order, because we do not skip anyone:


ngl, that's a long SEE ALSO and every single one of them ate πŸ’€πŸ’…

and that's the page, bestie!! πŸŽ€ sourced from ./drivers/net/dsa/microchip, stamped October 2026 β€” so go forth, write that PHY register at that address, and remember: SPI and I2C did not get an invite πŸ¦‹βœ¨πŸ’– periodt.

πŸ“¦ where this page comes from