scmi_base_i...ion_list_get(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… scmi_base_implementation_list_get(9) β€” like, the Kernel API Manual but make it make sense πŸŽ€

okay so bestie, welcome to the Kernel API Manual entry for scmi_base_implementation_list_get(9). yes the title is a mouthful, no i will not be shortening it, it's iconic and it's earning its full name. sit down, hydrate, and let's get into it ✨


✨ NAME ✨

scmi_base_implementation_list_get β€” literally gets you the list of protocols that OSPM is allowed to access. that's the whole vibe. that's the gig. 🫢


🌸 SYNOPSIS 🌸

int scmi_base_implementation_list_get (const struct scmi_protocol_handle
*ph , u8 *protocols_imp );

copy it exactly like that, spacing and all, no cap. the line break is part of the aesthetic. πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • ph β€” the SCMI protocol handle. your little passport to the protocol, basically. main character energy for real.
  • protocols_imp β€” a pointer that's gonna hold the list of protocol identifiers. it's giving "empty cup, ready to be filled with knowledge" πŸ“

πŸ”₯ RETURN πŸ”₯

0 on success β€” slay, we ate, no notes πŸ’€

otherwise? you get the appropriate SCMI error. so if it's not a zero, something's up, and the error code will tell you what. periodt.


πŸ‘‘ SEE ALSO πŸ‘‘

start with the kernel file itself, bestie:

  • Kernel file ./drivers/firmware/arm_scmi/base.c

and then the whole friend group, all mutuals, all worth a follow:


ngl the function name is long enough to be a whole mood, but it does exactly what it says: you get the implementation list, you get the protocols OSPM can touch, and you move on with your life. πŸ’–

that's the page!! mwah πŸ˜­πŸ’œ

β€” xoxo, your girl, signing off from ./drivers/firmware/arm_scmi, October 2026, Kernel API Manual era. go be iconic with it 🌈⭐🧚

πŸ“¦ where this page comes from