xpcs_create_fwnode(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ xpcs_create_fwnode ✨

okay so this is a page from the Kernel API Manual bestie β€” it's xpcs_create_fwnode(9), and it's literally the "make me a DW xPCS out of this fwnode" moment πŸŽ€


πŸ’– NAME

xpcs_create_fwnode β€” spin up a DW xPCS instance from @fwnode ✨


πŸ¦‹ SYNOPSIS

struct dw_xpcs * xpcs_create_fwnode (struct fwnode_handle *fwnode );

like... one function, one argument, one iconic struct pointer πŸ’…


🌸 ARGUMENTS

  • fwnode β€” the fwnode handle that's pointing at the DW XPCS device 🫢 that's it, that's the whole input, she's low maintenance

πŸ‘‘ RETURN

so here's the vibe check on what you get back 🌈

  • a pointer to the DW XPCS handle if successful β€” slay, you're done πŸ’–
  • -ENODEV if the fwnode device is unavailable, or if the PCS device couldn't be found on the bus 😭
  • -EPROBE_DEFER if the respective MDIO-device instance couldn't be found β€” not a no, just a "not yet" bestie ⭐
  • other negative errno values related to the data allocations and MDIO-bus communications πŸ’€
ngl the negative errno ones are giving "something went sideways in the plumbing" β€” allocations and MDIO-bus comms are where they come from, no cap πŸ™ˆ

πŸ”₯ SEE ALSO


and that's the whole page, bestie β€” main character energy from the ./drivers/net/pcs directory, dated October 2026 πŸ’œ go forth and probe ur PCS devices responsibly ✨🧚

πŸ“¦ where this page comes from