drivers/net/wireless/marvell/libertas/if_spi.c

File Facts

System

Linux kernel

Corpus path

drivers/net/wireless/marvell/libertas/if_spi.c

Extension

.c

Size

31265 bytes

Lines

1290

Domain

Driver Families

Bucket

drivers/net

Inferred role

Driver Families: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/hardirq.h
• linux/interrupt.h
• linux/module.h
• linux/firmware.h
• linux/jiffies.h
• linux/list.h
• linux/netdevice.h
• linux/slab.h
• linux/spi/libertas_spi.h
• linux/spi/spi.h
• host.h
• decl.h
• defs.h
• dev.h
• if_spi.h

Detected Declarations

• struct if_spi_packet
• struct if_spi_card
• function free_if_spi_card
• function list_for_each_entry_safe
• function spu_transaction_init
• function spu_transaction_finish
• function spu_write
• function spu_write_u16
• function spu_reg_is_port_reg
• function spu_read
• function spu_read_u16
• function spu_read_u32
• function spu_wait_for_u16
• function spu_wait_for_u32
• function spu_set_interrupt_mode
• function spu_get_chip_revision
• function spu_set_bus_mode
• function spu_init
• function if_spi_prog_helper_firmware
• function if_spi_prog_main_firmware_check_len
• function if_spi_prog_main_firmware
• function if_spi_c2h_cmd
• function if_spi_c2h_data
• function if_spi_h2c
• function if_spi_e2h
• function if_spi_host_to_card_worker
• function if_spi_host_to_card
• function if_spi_host_interrupt
• function if_spi_init_card
• function if_spi_resume_worker
• function if_spi_probe
• function libertas_spi_remove
• function if_spi_suspend
• function if_spi_resume
• function if_spi_init_module
• function if_spi_exit_module
• module init if_spi_init_module

Annotated Snippet

module_init(if_spi_init_module);
module_exit(if_spi_exit_module);

MODULE_DESCRIPTION("Libertas SPI WLAN Driver");
MODULE_AUTHOR("Andrey Yurovsky <andrey@cozybit.com>, "
	      "Colin McCabe <colin@cozybit.com>");
MODULE_LICENSE("GPL");
MODULE_ALIAS("spi:libertas_spi");

Annotation

• Immediate include surface: `linux/hardirq.h`, `linux/interrupt.h`, `linux/module.h`, `linux/firmware.h`, `linux/jiffies.h`, `linux/list.h`, `linux/netdevice.h`, `linux/slab.h`.
• Detected declarations: `struct if_spi_packet`, `struct if_spi_card`, `function free_if_spi_card`, `function list_for_each_entry_safe`, `function spu_transaction_init`, `function spu_transaction_finish`, `function spu_write`, `function spu_write_u16`, `function spu_reg_is_port_reg`, `function spu_read`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.