ap_bus_match(9)

💅 ap_bus_match(9)

okay so this is a page straight out of the Kernel API Manual bestie, and we're talking about ap_bus_match — yes the (9) means it's a kernel-internals kinda situation, very grown-up, very main character 💅

---

✨ NAME ✨

ap_bus_match —

and honestly? the description is literally empty in the source. iconique of it to leave us on read like that 😭 no cap, that's just how the page ships.

---

🌸 SYNOPSIS 🌸

int ap_bus_match (struct device *dev , const struct device_driver *drv );

that's the whole vibe: it takes a device and a driver pointer and hands you back an int. periodt.

---

🎀 ARGUMENTS 🎀

• dev — a pointer to a device 🫶 that's it, that's the whole note
• drv — a pointer to a device_driver ✨ same energy

---

🦋 DESCRIPTION 🦋

So what does it do? The page tells us, in its one singular sentence, that this is about AP bus driver registration/unregistration. That's the entire description. Short, sweet, and absolutely refusing to elaborate 💀

ngl bestie, if you came here looking for a novel — this is a haiku. Take the sentence and go, that's all the page gives us 🙈

---

👑 SEE ALSO 👑

The kernel file lives at ./drivers/s390/crypto/ap_bus.c — go touch grass in that directory if you want the real tea 🍓 and while you're at it, the page points you at all these siblings:

• 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_uevent(9)
• ap_owned_by_def_drv(9)
• ap_apqn_in_matrix_owned_by_def_drv(9) (say that one three times fast, I dare you 😭)
• ap_select_domain(9)
• ap_get_configuration(9)
• ap_scan_bus(9)
• ap_module_init(9)

---

that's the whole page, bestie 🌈

sign-off szn: source path ./drivers/s390/crypto, dated October 2026, and the page itself is ap_bus_match(9). mwah 💖