drivers/net/wireless/broadcom/brcm80211/brcmfmac/usb.c

File Facts

System

Linux kernel

Corpus path

drivers/net/wireless/broadcom/brcm80211/brcmfmac/usb.c

Extension

.c

Size

39631 bytes

Lines

1605

Domain

Driver Families

Bucket

drivers/net

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern 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.
• Defines an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• 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/kernel.h
• linux/module.h
• linux/firmware.h
• linux/usb.h
• linux/vmalloc.h
• brcmu_utils.h
• brcm_hw_ids.h
• brcmu_wifi.h
• bus.h
• debug.h
• firmware.h
• usb.h
• core.h
• common.h
• bcdc.h

Detected Declarations

• struct trx_header_le
• struct rdl_state_le
• struct bootrom_id_le
• struct brcmf_usbdev_info
• function brcmf_usb_ioctl_resp_wait
• function brcmf_usb_ioctl_resp_wake
• function brcmf_usb_ctl_complete
• function brcmf_usb_ctlread_complete
• function brcmf_usb_ctlwrite_complete
• function brcmf_usb_send_ctl
• function brcmf_usb_recv_ctl
• function brcmf_usb_tx_ctlpkt
• function brcmf_usb_rx_ctlpkt
• function brcmf_usb_enq
• function brcmf_usbdev_qinit
• function brcmf_usb_free_q
• function list_for_each_entry_safe
• function brcmf_usb_del_fromq
• function brcmf_usb_tx_complete
• function brcmf_usb_rx_complete
• function brcmf_usb_rx_refill
• function brcmf_usb_rx_fill_all
• function brcmf_usb_state_change
• function brcmf_usb_tx
• function brcmf_usb_up
• function brcmf_cancel_all_urbs
• function brcmf_usb_down
• function brcmf_usb_sync_complete
• function brcmf_usb_dl_cmd
• function brcmf_usb_dlneeded
• function brcmf_usb_resetcfg
• function brcmf_usb_dl_send_bulk
• function brcmf_usb_dl_writeimage
• function brcmf_usb_dlstart
• function brcmf_usb_dlrun
• function brcmf_usb_fw_download
• function brcmf_usb_detach
• function check_file
• function brcmf_usb_get_blob
• function brcmf_usb_probe_phase2
• function brcmf_usb_prepare_fw_request
• function brcmf_usb_probe_cb
• function brcmf_usb_disconnect_cb
• function brcmf_usb_probe
• function brcmf_usb_disconnect
• function brcmf_usb_suspend
• function brcmf_usb_resume
• function brcmf_usb_reset_resume

Annotated Snippet

struct device_driver *drv = &brcmf_usbdrvr.driver;
	int ret;

	brcmf_dbg(USB, "Enter\n");
	ret = driver_for_each_device(drv, NULL, NULL,
				     brcmf_usb_reset_device);
	if (ret)
		brcmf_err("failed to reset all usb devices %d\n", ret);

	usb_deregister(&brcmf_usbdrvr);
}

int brcmf_usb_register(void)
{
	brcmf_dbg(USB, "Enter\n");
	return usb_register(&brcmf_usbdrvr);
}

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/firmware.h`, `linux/usb.h`, `linux/vmalloc.h`, `brcmu_utils.h`, `brcm_hw_ids.h`, `brcmu_wifi.h`.
• Detected declarations: `struct trx_header_le`, `struct rdl_state_le`, `struct bootrom_id_le`, `struct brcmf_usbdev_info`, `function brcmf_usb_ioctl_resp_wait`, `function brcmf_usb_ioctl_resp_wake`, `function brcmf_usb_ctl_complete`, `function brcmf_usb_ctlread_complete`, `function brcmf_usb_ctlwrite_complete`, `function brcmf_usb_send_ctl`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: pattern implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.