scmi_channels_setup(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ scmi_channels_setup(9) β€” Kernel API Manual ✨

Okay bestie, welcome to the page for scmi_channels_setup(9), straight out of the Kernel API Manual. It’s giving β€œkernel helper with main character energy,” and we’re gonna get into all of it πŸ’….

🌸 NAME 🌸

scmi_channels_setup β€” the helper that initializes all required channels. Periodt.

πŸ› οΈ SYNOPSIS πŸ› οΈ

int scmi_channels_setup (struct scmi_info *info );

πŸŽ€ ARGUMENTS πŸŽ€

  • info β€” the SCMI instance descriptor. That’s the whole vibe check for this call, no cap.

πŸ’– DESCRIPTION πŸ’–

Okay so this function initializes all the channels found described in the DT against the underlying configured transport, using custom defined dedicated devices instead of borrowing devices from the SCMI drivers. The way that works is: channels are initialized upfront during core SCMI stack probing, and they are no more coupled with SCMI devices used by SCMI drivers. Slay for decoupling, honestly πŸ¦‹.

🫢 Note time, bestie: even though a pair of TX/RX channels is associated to each protocol defined in the DT, a distinct freshly initialized channel is created only if the DT node for the protocol at hand describes a dedicated channel. In all the other cases, the common BASE protocol channel is reused. That’s the rule, and it’s lowkey important.

🌈 RETURN 🌈

  • 0 on Success. That’s the good ending ✨.

πŸ‘€ SEE ALSO πŸ‘€

No cap, here’s the whole SEE ALSO squad β€” every single one, in order:


This cutie lives in source/version ./drivers/firmware/arm_scmi, dated October 2026, and it’s literally the scmi_channels_setup(9) page β€” slay and goodbye πŸ’…πŸŽ€

πŸ“¦ where this page comes from