__ps2_command(9)

okay so bestie, this is __ps2_command(9) from the Kernel API Manual, and it's literally the little icon that sends a command to a PS/2 device. no cap, it's giving embedded realness 🦋.

✨ NAME ✨

__ps2_command — send a command to PS/2 device 💖

🦋 SYNOPSIS 🦋

int __ps2_command (struct ps2dev *ps2dev , u8 *param , unsigned int
       command );

💅 ARGUMENTS 💅

• ps2dev — the PS/2 device that should execute the command. main character energy, fr fr 👑.
• param — a buffer containing parameters to be sent along with the command, or place where the results of the command execution will be deposited, or both. the way it's both input and output? obsessed ✨.
• command — command word that encodes the command itself, as well as number of additional parameter bytes that should be sent to the device and expected length of the command response. iykyk, it's packed with info 💅.

🌸 DESCRIPTION 🌸

🚨 Not serialized. Callers should use ps2_begin_command and ps2_end_command to ensure proper serialization for complex commands.

so like, this function is not serialized — that's the whole vibe check, bestie. if you're doing complex commands, please use ps2_begin_command and ps2_end_command to ensure proper serialization. don't skip the serialization duo and hope for the best 😭.

🎀 SEE ALSO 🎀

go peek at the Kernel file ./drivers/input/serio/libps2.c, and also these absolute icons:

• ps2_sendbyte(9)
• ps2_begin_command(9)
• ps2_end_command(9)
• ps2_drain(9)
• ps2_is_keyboard_id(9)
• ps2_command(9)
• ps2_sliced_command(9)
• ps2_init(9)
• ps2_interrupt(9)

made with 💖 from the source path ./drivers/input/serio, dated October 2026, for __ps2_command(9) — slay and read the source, bestie 🫶.