ksz_handle_wake_reason(9)
π ksz_handle_wake_reason(9) β Kernel API Manual π
πΈ NAME πΈ
ksz_handle_wake_reason β literally handles the wake reason on a specified port, bestie. π
β¨ SYNOPSIS β¨
int ksz_handle_wake_reason (struct ksz_device *dev , int port );
π§ ARGUMENTS π§
devβ the device structure, obvi.portβ the port number, periodt.
π¦ DESCRIPTION π¦
okay so picture this: ksz_handle_wake_reason reads the PME (Power Management Event) status register of the port you picked, all to figure out the wake reason. If thereβs no wake event, it returns early and dips out. If there is one, it logs the wake reason β which could be due to a "Magic Packet", a "Link Up", or an "Energy Detect" event. Then the PME status register gets cleared to acknowledge that the wake event has been handled. iconic behavior, ngl. π
π₯ RETURN π₯
0 on success, or an error code on failure. thatβs the whole return vibe, no cap. π
π SEE ALSO π
- Kernel file
./drivers/net/dsa/microchip/ksz_common.c ksz_phylink_mac_disable_tx_lpi(9)ksz_phylink_mac_enable_tx_lpi(9)ksz_update_port_member(9)ksz_parent_mdio_read(9)ksz_parent_mdio_write(9)ksz_phy_addr_to_port(9)ksz_irq_phy_setup(9)ksz_irq_phy_free(9)ksz_parse_dt_phy_config(9)ksz_mdio_register(9)ksz_is_port_mac_global_usable(9)ksz_get_wol(9)ksz_set_wol(9)ksz_wol_pre_shutdown(9)ksz_switch_macaddr_get(9)ksz_switch_shutdown(9)ksz_drive_strength_to_reg(9)ksz_drive_strength_error(9)ksz_drive_strength_write(9)
π«Ά source/version vibe check: this page lives under./drivers/net/dsa/microchip, dated October 2026, and the manual tag isksz_handle_wake_reason(9). mwah, bye bestie! π
π¦ 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