match_device(9)

💖 NAME 💖

okay so this is match_device(9) from the Kernel API Manual, and it's giving tiny-but-mighty main character energy. its whole thing? Report whether this driver can handle this device. that's the vibe check, bestie: can this driver handle this device or not? no cap. ✨

🎀 SYNOPSIS 🎀

the signature is literally this, untouched, because we do not edit the sacred spacing:

       int match_device (const struct parisc_driver *driver , struct
       parisc_device *dev );

not me obsessing over the exact punctuation, but also yes. int is right there, and parisc_driver / parisc_device stay exactly as written. periodt. 💅

🌸 ARGUMENTS 🌸

two inputs, zero drama:

• driver — the PA-RISC driver we're trying, aka the candidate driver getting the vibe check. 🫶
• dev — the PA-RISC device we're trying, aka the device in question. the main character in this matchup. 👑

🦋 SEE ALSO 🦋

the whole related-squad, plus the kernel file, all listed here so you can go read more:

• Kernel file ./arch/parisc/kernel/drivers.c
• for_each_padev(9)
• register_parisc_driver(9)
• count_parisc_driver(9)
• unregister_parisc_driver(9)
• find_pa_parent_type(9)
• print_pa_hwpath(9)
• get_pci_node_path(9)
• print_pci_hwpath(9)
• alloc_tree_node(9)
• register_parisc_device(9)
• match_pci_device(9)
• match_parisc_device(9)
• parse_tree_node(9)
• hwpath_to_device(9)
• device_to_hwpath(9)
• walk_native_bus(9)
• walk_central_bus(9)
• init_parisc_bus(9)
• print_parisc_devices(9)

iykyk, that's the whole friend group. 🍓

mwah 💋 this page came from ./arch/parisc/kernel and is dated October 2026 — that's the source/version and date from the footer, bestie. stay slay, read your man pages, and may your drivers always match. 💖✨