STRUCT VSC73XX_OPS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

struct vsc73xx_ops β€” the VSC73xx methods container, bestie πŸ’…

okay so this page lives in the Kernel API Manual, and the star of the show is struct vsc73xx_ops(9) β€” it's literally just a lil container holding the methods for VSC73xx. no cap, that's the whole vibe. πŸ¦‹


πŸŽ€ SYNOPSIS πŸŽ€

struct vsc73xx_ops {
    int (*read)(struct vsc73xx *vsc, u8 block, u8 subblock, u8 reg, u32
*val);
    int (*write)(struct vsc73xx *vsc, u8 block, u8 subblock, u8 reg, u32
val);
 };

like, that's it. two function pointers. main character energy fr fr. πŸ‘‘


🌸 Members 🌸

  • read β€” the method for register reading over the hardware-dependent interface πŸ“–βœ¨ (yes, "hardware-dependent", meaning it's giving "the actual hardware decides how this goes" β€” iconic but you gotta provide it)
  • write β€” the method for register writing over the hardware-dependent interface ✍️πŸ”₯ (same deal, bestie β€” hardware-dependent interface, so it's on you to fill it in)
lowkey the whole struct is just these two pointers to functions you define, and that's the vibe check: read = get the register, write = set the register. both over that hardware-dependent interface. periodt. πŸ’œ

πŸ¦‹ SEE ALSO πŸ¦‹

  • Kernel file ./drivers/net/dsa/vitesse-vsc73xx.h β€” go read it, iykyk πŸ’–
  • struct vsc73xx_portinfo(9)
  • struct vsc73xx(9)
  • struct vsc73xx_bridge_vlan(9)

all the sibling structs, obsessed fr. go click through them like it's a group chat 🌈


and that's the page, bestie 🫢 β€” brought to you by ./drivers/net/dsa, dated October 2026, and yes it's still struct vsc73xx_ops(9) at the bottom, slay πŸ’…πŸŽ€

πŸ“¦ where this page comes from