get_set_conduit_method(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ get_set_conduit_method(9) ✨

okay so this is a page from the Kernel API Manual, section 9 β€” yes it's a real manpage name and yes the parentheses-and-number thing is the vibe, just roll with it bestie πŸ’…


🌸 NAME 🌸

get_set_conduit_method β€” the little function that picks whether you're talking to EL2/EL3 over SMC or over HVC. choose-your-own-adventure but for firmware calls πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

int get_set_conduit_method (struct device_node *np );

like, that's it. one arg, one int coming back. clean. minimal. iconic. ✨


πŸ’– ARGUMENTS πŸ’–

  • np β€” a pointer to the device_node structure. that's the whole description, she's brief and she's confident 🫢

πŸ‘‘ DESCRIPTION πŸ‘‘

so the whole point of this one: it uses SMC-based functions or HVC-based functions to communicate with EL2/EL3. that's the entire description fr fr β€” it decides which flavour of firmware chat you're doing, and then you just vibe with it πŸ’€


🌈 RETURN 🌈

  • returns 0 on success πŸŽ‰
  • or an error code 😭 (which one? the page does not say, and I'm not out here inventing lore no cap)

πŸ”₯ SEE ALSO πŸ”₯

okay this is the part where the page absolutely goes off β€” the entire ZynqMP power-management friend group is tagged in the group chat πŸ‘‘πŸ’…

like I said. everyone is here. seventy-three whole cross-references and not one of them skipped, bestie, we do not leave the homies out πŸ’œ


and that's the page!! 🧚 she lives in ./drivers/firmware/xilinx, she's dated October 2026, and she's part of the Kernel API Manual gang β€” take care of her, mwah πŸ’‹πŸ“

πŸ“¦ where this page comes from