fsl_guts_lane_validate(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… fsl_guts_lane_validate β€” a Kernel API Manual moment

okay so bestie, welcome to fsl_guts_lane_validate(9) from the Kernel API Manual β€” yes it's a section 9 page, yes it's a function, yes we're gonna stan it πŸŽ€

It's the vibe-check function: it validates that a SerDes protocol is actually implemented and supported on the current SoC. No cap. ✨


✨ SYNOPSIS ✨

int fsl_guts_lane_validate (int serdes_idx , int lane , enum
       lynx_lane_mode lane_mode );

literally just three args and an int back. iconic. 🫢


🌸 ARGUMENTS 🌸

  • serdes_idx β€” the SerDes block index, and it's one-based (so like, counting starts at 1, not 0 β€” she's quirky like that πŸ™ˆ)
  • lane β€” the lane index within that SerDes, and this one is zero-based (back to normal counting, thank god 😭)
  • lane_mode β€” the SerDes protocol you're asking for, typed as enum lynx_lane_mode

πŸ¦‹ DESCRIPTION πŸ¦‹

The whole point: call this before you actually request the RCW override procedure to be applied via fsl_guts_lane_set_mode. Like, check first, then commit. main character energy only. πŸ’…

not me emphasizing this: validate first, override second. the order matters fr fr.

⭐ RETURN ⭐

  • 0 β€” the RCW override to that protocol is possible, slay βœ…
  • negative error β€” nope, not possible, and it comes back as a negative error value πŸ’€

πŸ”₯ SEE ALSO πŸ”₯


aaaand that's the page! 🧚 source lives in ./drivers/soc/fsl, dated October 2026, and it's fsl_guts_lane_validate(9) all the way down β€” periodt. πŸ’–πŸŒˆπŸ‘‘

πŸ“¦ where this page comes from