pch_gbe_phy_write_reg_miic(9)
β¨ NAME β¨
pch_gbe_phy_write_reg_miic β bestie, it writes the MII control register π
This is from the Kernel API Manual, and honestly? It's a whole little moment in the networking world πΈ
π¦ SYNOPSIS π¦
s32 pch_gbe_phy_write_reg_miic (struct pch_gbe_hw *hw , u32 offset , u16 data );
That's the whole vibe check right there β one call, three args, returns an s32 β¨
π ARGUMENTS π
hwβ Pointer to the HW structure π«Ά like, the hardware's whole personality lives in there.offsetβ Register offset to be read. (Yes, the page literally says "to be read" on a write function β I'm just the messenger, don't come for me ππ)dataβ data to write to register at offset Returns0: Successful.-EINVAL: Invalid argument. π
So yeah, the return story got folded into the data line on this page, but we keep the receipts: returns 0 when it's a slay β
and -EINVAL when someone handed over an invalid argument π
π SEE ALSO π
- Kernel file
./drivers/net/ethernet/oki-semi/pch_gbe/pch_gbe_phy.cβ the main character source file, iykyk
And the whole PHY friend group, fr fr:
pch_gbe_phy_get_id(9)pch_gbe_phy_read_reg_miic(9)pch_gbe_phy_sw_reset(9)pch_gbe_phy_hw_reset(9)pch_gbe_phy_power_up(9)pch_gbe_phy_power_down(9)pch_gbe_phy_set_rgmii(9)pch_gbe_phy_tx_clk_delay(9)pch_gbe_phy_init_setting(9)pch_gbe_phy_disable_hibernate(9)
π lowkey iconic thatpch_gbe_phy_read_reg_miic(9)is sitting right there in SEE ALSO whileoffsetswears it's "to be read" β the group chat is thriving, no notes π₯
alright bestie that's the whole page, mwah π this gem comes from ./drivers/net/ethernet/oki-sem... and it's dated October 2026 β go forth and write those MII control registers, periodt ππ¦β¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms