qcom_scm_set_warm_boot_addr(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– qcom_scm_set_warm_boot_addr β€” the Kernel API Manual, bestie edition πŸ’–

okay so welcome to the qcom_scm lore, specifically the part where we tell the secure world where to send the CPUs when they wake back up 😴➑️✨ this is a kernel API manual page (9 = kernel API section, iykyk), and we're gonna get into it.


✨ NAME ✨

qcom_scm_set_warm_boot_addr β€” literally just: set the warm boot address for all the cpus, no cap 🫢


πŸŽ€ SYNOPSIS πŸŽ€

int qcom_scm_set_warm_boot_addr (void *entry );

that's it. one argument. one int coming back. main character energy fr πŸ’…


🌸 ARGUMENTS 🌸

  • entry β€” the entry point function for the cpus πŸ‘‘ like, this is the address the cpus should jump to. it's a void *, so... yeah, it's a pointer, we don't ask questions.

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so here's the vibe: this sets the Linux entry point that SCM will transfer control to when coming out of a power down πŸ”₯

and like, "CPU power down" here? that can happen on cpuidle or on hotplug β€” both of those can trigger it, so this address is doing a lot of heavy lifting ngl. it's the "welcome back, go here" sign for your cpus πŸ’œ

no seriously bestie, this is the handoff point β€” SCM wakes the cpu and sends it to your entry. make sure it's a real one πŸ™ˆ

⭐ SEE ALSO ⭐

the whole extended universe, bestie β€” go read these:

that's the whole friend group right there 🌈


and that's the page!! πŸ’– this slay was served up from the ./drivers/firmware/qcom corner of the tree, dated October 2026, and titled qcom_scm_set_warm_boot_addr(9) β€” go warm-boot those cpus responsibly, bestie πŸ§šβœ¨πŸ“

πŸ“¦ where this page comes from