ap_scan_bus(9)

✨ ap_scan_bus(9) ✨

okay so this is a page from the Kernel API Manual bestie, and we're talking about ap_scan_bus — yes it's a 9-section kernel page, yes it's giving driver-dev realness, stay with me 💅

🎀 NAME 🎀

ap_scan_bus — scan the AP bus for new devices. Always run under mutex ap_scan_bus_mutex protection which needs to get locked/unlocked by the caller! Returns true if any config change has been detected during the scan, otherwise false.

lowkey the most important sentence on this whole page: the caller is the one who has to lock and unlock ap_scan_bus_mutex. Not the function. You. Do not skip this, i'm begging 😭

✨ SYNOPSIS ✨

bool ap_scan_bus (void );

🦋 ARGUMENTS 🦋

• void — no arguments. that's it. nothing to pass, she takes zero input, queen of boundaries 👑

🌸 SEE ALSO 🌸

Kernel file ./drivers/s390/crypto/ap_bus.c — that's where she lives, go say hi 🫶

• ap_airq_ptr(9)
• ap_interrupts_available(9)
• ap_qci_available(9)
• ap_apft_available(9)
• ap_init_qci_info(9)
• ap_request_timeout(9)
• ap_poll_timeout(9)
• ap_interrupt_handler(9)
• ap_tasklet_fn(9)
• ap_poll_thread(9)
• ap_bus_match(9)
• ap_uevent(9)
• ap_owned_by_def_drv(9)
• ap_apqn_in_matrix_owned_by_def_drv(9)
• ap_select_domain(9)
• ap_get_configuration(9)
• ap_module_init(9)

and that's the whole vibe check 💖 honestly a short one but she said everything she needed to say. reminder one more time because i love you: mutex ap_scan_bus_mutex, locked and unlocked by the caller, no exceptions, periodt 🔥

this lil cutie comes to you from ./drivers/s390/crypto, dated October 2026 — go build something iconic with her, mwah 🌈⭐💜