phy_ethtool_get_plca_cfg(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 phy_ethtool_get_plca_cfg(9) β€” the Kernel API Manual glow-up 🌸

okay so bestie, this is phy_ethtool_get_plca_cfg(9) straight out of the Kernel API Manual, and honestly? it's a short one. a little snack. a single-purpose function that just goes and gets the PLCA RS configuration for you, no drama, no cap. let's get into it πŸ’…


πŸŽ€ NAME πŸŽ€

phy_ethtool_get_plca_cfg β€” Get PLCA RS configuration. that's it, that's the whole job. iconic minimalism fr fr ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

int phy_ethtool_get_plca_cfg (struct phy_device *phydev , struct
       phy_plca_cfg *plca_cfg );

it returns an int, it takes two pointers, it minds its own business. we love a low-maintenance signature 🫢


πŸ’– ARGUMENTS πŸ’–

  • phydev β€” the phy_device struct. your whole PHY situation lives in here, and yes she's the main character of this call 🌟
  • plca_cfg β€” where to store the retrieved configuration. this is the little basket you hand over so the function has somewhere to drop the goods πŸ§ΊπŸ’œ

✨ DESCRIPTION ✨

so what does she do? she retrieves the PLCA configuration from the PHY. that's the whole arc. you give her the phy_device struct, you give her a place to put the answer, and she comes back with the config.

return value tea β˜•:

  • 0 on success β€” slay, you got it πŸŽ‰
  • a negative value if an error occurred β€” not slay, something went sideways, check that return value bestie, do NOT ignore it 😭
ngl the golden rule of this entire function is: always check the return. 0 is your bestie, negative is your vibe check failing. periodt πŸ’€

πŸ‘‘ SEE ALSO πŸ‘‘

the whole squad, assembled, no one left behind (this is the entire lineup from the kernel file ./drivers/net/phy/phy.c, and yes i'm listing every single one because they all ate):

phy_print_status(9), phy_get_rate_matching(9), phy_config_interrupt(9), phy_restart_aneg(9), phy_aneg_done(9), phy_supported_speeds(9), phy_check_valid(9), phy_sanitize_settings(9), phy_mii_ioctl(9), phy_do_ioctl(9), phy_do_ioctl_running(9), __phy_hwtstamp_get(9), __phy_hwtstamp_set(9), phy_queue_state_machine(9), phy_trigger_machine(9), phy_ethtool_get_strings(9), phy_ethtool_get_sset_count(9), phy_ethtool_get_stats(9), __phy_ethtool_get_phy_stats(9), __phy_ethtool_get_link_ext_stats(9), plca_check_valid(9), phy_ethtool_set_plca_cfg(9), phy_ethtool_get_plca_status(9), phy_start_cable_test(9), phy_start_cable_test_tdr(9), phy_check_link_status(9), phy_inband_caps(9), phy_config_inband(9), _phy_start_aneg(9), phy_start_aneg(9), phy_speed_down(9), phy_speed_up(9), phy_start_machine(9), phy_stop_machine(9), phy_error(9), phy_write_barrier(9), phy_disable_interrupts(9), phy_interrupt(9), phy_enable_interrupts(9), phy_update_stats(9), phy_request_interrupt(9), phy_free_interrupt(9), phy_get_next_update_time(9), phy_state_machine(9), phy_stop(9), phy_start(9), phy_mac_interrupt(9), phy_loopback(9), phy_eee_tx_clock_stop_capable(9), phy_eee_rx_clock_stop(9), phy_init_eee(9), phy_get_eee_err(9), phy_ethtool_get_eee(9), phy_ethtool_set_eee_noneg(9), phy_ethtool_set_eee(9), phy_ethtool_set_wol(9), phy_ethtool_get_wol(9), phy_ethtool_nway_reset(9)

like i said. the whole squad. iykyk 🐝


πŸ’« and that's the page! brought to you by the kernel file ./drivers/net/phy, dated October 2026 β€” mwah, go read your return values, ily, bye πŸ«ΆπŸŒˆπŸŽ€
πŸ“¦ where this page comes from