e1000_access...ebug_regs_hv(9)

✨ NAME ✨

okay so this is the e1000_access_phy_debug_regs_hv(9) page from the Kernel API Manual — the header/footer shorten it to e1000_access...ebug_regs_hv(9), which is giving cute nickname energy. The official NAME business is: Read HV PHY vendor specific high registers. periodt.

🌸 SYNOPSIS 🌸

s32 e1000_access_phy_debug_regs_hv (struct e1000_hw *hw , u32 offset ,
u16 *data , bool read );

🫶 ARGUMENTS 🫶

• hw — pointer to the HW structure. your main-character struct, basically.
• offset — register offset to be read or written.
• data — pointer to the data to be read or written.
• read — determines if operation is read or write. read girlie or write girlie, no in-between.

💅 DESCRIPTION 💅

okay so e1000_access_phy_debug_regs_hv reads the PHY register at offset and stores the retrieved information in data. it assumes the semaphore is already acquired, bestie — noted, no cap.

also important: the procedure to access these regs uses the address port and data port to read/write. these accesses are done with PHY address 2 and without using pages. that's the whole little setup, slay. ✨

👀 SEE ALSO 👀

the kernel file is ./drivers/net/ethernet/intel/e1000e/phy.c — that's the home base, iykyk. and here's the whole cross-reference friend group, exact names only:

• e1000e_check_reset_block_generic(9), e1000e_get_phy_id(9), e1000e_phy_reset_dsp(9), e1000e_read_phy_reg_mdic(9), e1000e_write_phy_reg_mdic(9), e1000e_read_phy_reg_m88(9), e1000e_write_phy_reg_m88(9), e1000_set_page_igp(9)
• __e1000e_read_phy_reg_igp(9), e1000e_read_phy_reg_igp(9), e1000e_read_phy_reg_igp_locked(9), __e1000e_write_phy_reg_igp(9), e1000e_write_phy_reg_igp(9), e1000e_write_phy_reg_igp_locked(9)
• __e1000_read_kmrn_reg(9), e1000e_read_kmrn_reg(9), e1000e_read_kmrn_reg_locked(9), __e1000_write_kmrn_reg(9), e1000e_write_kmrn_reg(9), e1000e_write_kmrn_reg_locked(9)
• e1000_set_master_slave_mode(9), e1000_copper_link_setup_82577(9), e1000e_copper_link_setup_m88(9), e1000e_copper_link_setup_igp(9), e1000_phy_setup_autoneg(9), e1000_copper_link_autoneg(9), e1000e_setup_copper_link(9)
• e1000e_phy_force_speed_duplex_igp(9), e1000e_phy_force_speed_duplex_m88(9), e1000_phy_force_speed_duplex_ife(9), e1000e_phy_force_speed_duplex_setup(9), e1000e_set_d3_lplu_state(9), e1000e_check_downshift(9)
• e1000_check_polarity_m88(9), e1000_check_polarity_igp(9), e1000_check_polarity_ife(9), e1000_wait_autoneg(9), e1000e_phy_has_link_generic(9), e1000e_get_cable_length_m88(9), e1000e_get_cable_length_igp_2(9)
• e1000e_get_phy_info_m88(9), e1000e_get_phy_info_igp(9), e1000_get_phy_info_ife(9), e1000e_phy_sw_reset(9), e1000e_phy_hw_reset_generic(9), e1000e_get_cfg_done_generic(9), e1000e_phy_init_script_igp3(9)
• e1000e_get_phy_type_from_id(9), e1000e_determine_phy_address(9), e1000_get_phy_addr_for_bm_page(9), e1000e_write_phy_reg_bm(9), e1000e_read_phy_reg_bm(9), e1000e_read_phy_reg_bm2(9), e1000e_write_phy_reg_bm2(9)
• e1000_enable_phy_wakeup_reg_access_bm(9), e1000_disable_phy_wakeup_reg_access_bm(9), e1000_access_phy_wakeup_reg_bm(9), e1000_power_up_phy_copper(9), e1000_power_down_phy_copper(9)
• __e1000_read_phy_reg_hv(9), e1000_read_phy_reg_hv(9), e1000_read_phy_reg_hv_locked(9), e1000_read_phy_reg_page_hv(9), __e1000_write_phy_reg_hv(9), e1000_write_phy_reg_hv(9), e1000_write_phy_reg_hv_locked(9), e1000_write_phy_reg_page_hv(9)
• e1000_get_phy_addr_for_hv_page(9), e1000_link_stall_workaround_hv(9), e1000_check_polarity_82577(9), e1000_phy_force_speed_duplex_82577(9), e1000_get_phy_info_82577(9), e1000_get_cable_length_82577(9)

okay that's the whole page, bestie 🫶. the footer is serving source/version ./drivers/net/ethernet/intel/e... and date October 2026 (and it also says e1000_access...ebug_regs_hv(9) again). mwah 💋✨