vme_irq_request(9)
πΈ NAME πΈ
okay so bestie, welcome to the vme_irq_request(9) page from the Kernel API Manual π
vme_irq_request β Request a specific VME interrupt. π
β¨ SYNOPSIS β¨
lowkey here's the exact signature, no cap:
int vme_irq_request (struct vme_dev *vdev , int level , int statid ,
void (*callback)(int level, int statid, void *priv_data) , void
*priv_data );
π ARGUMENTS π
vdevβ Pointer to VME device structvme_devassigned to driver instance. like, this is your device's whole identity bestie π«Άlevelβ Interrupt priority being requested. the priority vibe check βstatidβ Interrupt vector being requested. the vector in question, periodt πcallbackβ Pointer to callback function called when VME interrupt/vector received. this is the function that gets pinged when the interrupt/vector shows up πpriv_dataβ Generic pointer that will be passed to the callback function. your lil extra data package, hand-delivered to the callback π
π DESCRIPTION π
Request callback to be attached as a handler for VME interrupts with provided level and statid.
so the whole vibe is: you're asking for your callback to be attached as the handler for VME interrupts that match the level and statid you gave. it's giving "put me on the interrupt guest list" β¨
π«Ά RETURN π«Ά
0β Zero on success. slay, it worked π-EINVALβ on invalid vme device, level or if the function is not supported. not it π-EBUSYβ if the level/statid combination is already in use. occupied, bestie, try another combo π- Hardware specific errors also possible. yeah, hardware can absolutely do its own thing π
π SEE ALSO π
Kernel file: ./drivers/staging/vme_user/vme.c
the whole friend group roll call, iykyk:
vme_alloc_consistent(9),vme_free_consistent(9),vme_get_size(9),vme_slave_request(9),vme_slave_set(9),vme_slave_get(9),vme_slave_free(9)vme_master_request(9),vme_master_set(9),vme_master_get(9),vme_master_read(9),vme_master_write(9),vme_master_rmw(9),vme_master_mmap_prepare(9),vme_master_free(9)vme_dma_request(9),vme_new_dma_list(9),vme_dma_pattern_attribute(9),vme_dma_pci_attribute(9),vme_dma_vme_attribute(9),vme_dma_free_attribute(9),vme_dma_list_add(9),vme_dma_list_exec(9),vme_dma_list_free(9),vme_dma_free(9)vme_irq_free(9),vme_irq_generate(9)vme_lm_request(9),vme_lm_count(9),vme_lm_set(9),vme_lm_get(9),vme_lm_attach(9),vme_lm_detach(9),vme_lm_free(9)vme_slot_num(9),vme_bus_num(9),vme_register_driver(9),vme_unregister_driver(9)
okay that's the whole page, mwah π β source/version: ./drivers/staging/vme_user; date: October 2026; page: vme_irq_request(9). bye bestie π¦
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms