hwspin_lock_...est_specific(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

hwspin_lock_...est_specific(9) πŸŽ€

okay bestie, you're in the Kernel API Manual and this page is all about hwspin_lock_...est_specific(9) β€” yes, the title is a little chopped, that's just how it's printed, no cap. It's giving β€œreserve me one very specific hwspinlock” energy. πŸ’…

NAME 🌸

hwspin_lock_request_specific β€” request for a specific hwspinlock

SYNOPSIS ✨

struct hwspinlock * hwspin_lock_request_specific (unsigned int id );

ARGUMENTS πŸ¦‹

  • id β€” index of the specific hwspinlock that is requested

DESCRIPTION πŸ’–

This function should be called by users of the hwspinlock module, in order to assign them a specific hwspinlock. Usually early board code will be calling this function in order to reserve specific hwspinlock ids for predefined purposes.

Should be called from a process context (might sleep). So yeah, process context bestie β€” it might sleep 😴.

RETURN πŸ”₯

the address of the assigned hwspinlock, or NULL on error

SEE ALSO πŸ‘‘

Kernel file ./drivers/hwspinlock/hwspinlock_core.c


okay that's the tea πŸ«– β€” from ./drivers/hwspinlock, Kernel API Manual, October 2026, hwspin_lock_...est_specific(9) out πŸ’…

πŸ“¦ where this page comes from