icss_iep_get_ptp_clock_idx(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… icss_iep_get_ptp_clock_idx(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual β€” yes, the actual kernel API manual, and yes, you're gonna understand this one, i promise 🫢 this page is literally about icss_iep_get_ptp_clock_idx, and no cap it's a tiny little function that just tells you which PTP clock you're working with. it's giving "one job, does it well" energy ✨


✨ NAME ✨

icss_iep_get_ptp_clock_idx β€” the function that gets you the PTP clock index, using the IEP driver πŸ’–

like, that's it. that's the whole vibe. she asks the IEP driver "hey, which PTP clock is this?" and the driver answers. iconic behavior honestly.


🌸 SYNOPSIS 🌸

int icss_iep_get_ptp_clock_idx (struct icss_iep *iep );

so it returns an int, and it takes exactly one thing: a struct icss_iep * that's literally named iep. short, sweet, slays πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • iep β€” a pointer to the structure that represents the IEP. that's the whole argument. one pointer, no drama, no surprises. you hand her the IEP struct and she's off πŸ¦‹

⭐ RETURN ⭐

the PTP clock index πŸŽ‰ β€” that's your answer, that's what you came for.

and if it's not registered? she returns -1. yep. not registered = -1, no exceptions, don't @ me 😭


🌈 SEE ALSO 🌈

the whole IEP friend group fr fr β€” go say hi to the rest of them 🧚


ok genuine heads up: if that index comes back as -1, that's the "not registered" signal. don't go treating -1 like a valid clock index, that's the trap πŸ™ˆ

and that's the page!! mwah πŸ’‹ this little love letter lives under ./drivers/net/ethernet/ti/icssg, dated October 2026, straight from the Kernel API Manual β€” go off, you now know icss_iep_get_ptp_clock_idx. periodt. πŸ‘‘πŸ’œ

πŸ“¦ where this page comes from