phy_notify_connect(9)
π« phy_notify_connect(9) π«
ok so we're in the Kernel API Manual bestie, and today's main character is phy_notify_connect β the little function that tells your phy "hey, somebody plugged in" π
πΈ NAME πΈ
phy_notify_connect β phy connect notification. that's it, that's the vibe β¨
π¦ SYNOPSIS π¦
int phy_notify_connect (struct phy *phy , int port );
π ARGUMENTS π
phyβ the phy. which phy? the one you got back fromphy_getπ like, that exact one, don't be out here guessing.portβ the port index for connect π that's the number that tells it which port we're talking about.
π DESCRIPTION π
okay so here's the tea β β if the phy needs to get its connection status, this callback is the thing you reach for. that's it. that's the whole description. iconic of it honestly π
β RETURN β
0 if it slayed (successful) β
β otherwise a negative error code, which is the kernel's way of saying "nope π" π
π₯ SEE ALSO π₯
the whole friend group, fr fr β plus the kernel file ./drivers/phy/phy-core.c where it all lives π«Ά
phy_create_lookup(9)phy_remove_lookup(9)phy_init(9)phy_exit(9)phy_power_on(9)phy_power_off(9)phy_calibrate(9)phy_notify_disconnect(9)phy_notify_state(9)phy_configure(9)phy_validate(9)_of_phy_get(9)of_phy_get(9)of_phy_put(9)phy_put(9)devm_phy_put(9)of_phy_simple_xlate(9)phy_get(9)devm_phy_get(9)devm_phy_optional_get(9)devm_of_phy_get(9)devm_of_phy_optional_get(9)devm_of_phy_get_by_index(9)phy_create(9)devm_phy_create(9)phy_destroy(9)devm_phy_destroy(9)__of_phy_provider_register(9)__devm_of_phy_provider_register(9)of_phy_provider_unregister(9)devm_of_phy_provider_unregister(9)phy_release(9)
ok that's the whole page, go touch some grass (or a phy) π±π
sign-off szn: this lil beauty comes from ./drivers/phy and it's dated October 2026 β no cap, put it in your calendar πβ¨
π¦ 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