ti_sci_msg_c...uery_fw_caps(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ ti_sci_msg_cmd_query_fw_caps(9) ✨

okay bestie, welcome to the Kernel API Manual πŸ’– β€” this is the page for ti_sci_msg_cmd_query_fw_caps, and yes the header truncates her as ti_sci_msg_c...uery_fw_caps(9) (iconic, honestly). She’s here to get the FW/SoC capabilities, and she is not doing it quietly. πŸŽ€

🌸 NAME 🌸

ti_sci_msg_cmd_query_fw_caps β€” Get the FW/SoC capabilities. πŸ’…

✨ SYNOPSIS ✨

int ti_sci_msg_cmd_query_fw_caps (const struct ti_sci_handle *handle ,
       u64 *fw_caps );

πŸŽ€ ARGUMENTS πŸŽ€

  • handle β€” Pointer to TI SCI handle. That’s your entry ticket to the TI SCI situation, bestie. 🫢
  • fw_caps β€” Each bit in fw_caps indicating one FW/SOC capability. So every bit is a little capability flag doing its thing. ✨

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so this function checks if the firmware supports any optional low power modes. That’s the vibe check. Old revisions of TIFS (< 08.04) will NACK the request, which results in -ENODEV being returned. Not a drill, bestie β€” old TIFS said no and you get that error. 😭

πŸ’… RETURN πŸ’…

0 if all went well, else returns appropriate error value. Slay when it’s zero, investigate when it’s not. πŸ’–

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/firmware/ti_sci.c β€” plus the whole ti_sci cinematic universe, no cap:


πŸ’– signed off from ./drivers/firmware, October 2026, in the Kernel API Manual. ti_sci_msg_c...uery_fw_caps(9) out. 🫢
πŸ“¦ where this page comes from