mii_eee_cap...nkmode_adv_t(9)

okay so bestie, this is your Kernel API Manual moment for the page mii_eee_cap...nkmode_adv_t(9) — iconic abbreviation, and the function inside is mii_eee_cap2_mod_linkmode_adv_t. Let's go 💅✨

🎀 NAME 🎀

mii_eee_cap2_mod_linkmode_adv_t -

🌸 SYNOPSIS 🌸

void mii_eee_cap2_mod_linkmode_adv_t (unsigned long *adv , u32 val );

✨ ARGUMENTS ✨

• adv — target the linkmode advertisement settings 🎯. This is the linkmode ad spot you're working with, bestie.
• val — register value 🔥. The value coming in from the register.

🦋 DESCRIPTION 🦋

A function that translates value of following registers to the linkmode:

• IEEE 802.3-2022 45.2.7.16 "EEE advertisement 2" register (7.62)
• IEEE 802.3-2022 45.2.7.17 "EEE link partner ability 2" register (7.63)

It's giving register-to-linkmode translation, and honestly? Obsessed. 🫶

💜 NOTE 💜

Currently this function is the same as mii_eee_cap2_mod_linkmode_sup_t.

For certain, not yet supported, modes however the bits differ. Therefore create separate functions already. 🫶

🌈 SEE ALSO 🌈

• Kernel file ./include/linux/mdio.h struct mdio_if_info(9)
• mdio45_ethtool_ksettings_get(9)
• mmd_eee_cap_to_ethtool_sup_t(9)
• mmd_eee_adv_to_ethtool_adv_t(9)
• ethtool_adv_to_mmd_eee_adv_t(9)
• linkmode_adv_to_mii_10gbt_adv_t(9)
• mii_10gbt_stat_mod_linkmode_lpa_t(9)
• mii_t1_adv_l_mod_linkmode_t(9)
• mii_t1_adv_m_mod_linkmode_t(9)
• linkmode_adv_to_mii_t1_adv_l_t(9)
• linkmode_adv_to_mii_t1_adv_m_t(9)
• mii_eee_cap1_mod_linkmode_t(9)
• mii_eee_cap2_mod_linkmode_sup_t(9)
• linkmode_to_mii_eee_cap1_t(9)
• linkmode_to_mii_eee_cap2_t(9)
• mii_10base_t1_adv_mod_linkmode_t(9)
• linkmode_adv_to_mii_10base_t1_t(9)
• mii_c73_mod_linkmode(9)
• mdio_module_driver(9)

That's the whole page, bestie. Source/version situation: ./include/linux, date October 2026, and the page is mii_eee_cap...nkmode_adv_t(9). Bye 💖