drivers/net/wireless/rsi/rsi_91x_usb_ops.c

File Facts

System

Linux kernel

Corpus path

drivers/net/wireless/rsi/rsi_91x_usb_ops.c

Extension

.c

Size

1784 bytes

Lines

62

Domain

Driver Families

Bucket

drivers/net

Inferred role

Driver Families: implementation source

Status

source 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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/firmware.h
• rsi_usb.h

Detected Declarations

• function Copyright

Annotated Snippet

while (true) {
			if (atomic_read(&dev->rx_thread.thread_done))
				goto out;

			skb = skb_dequeue(&dev->rx_q);
			if (!skb)
				break;
			status = rsi_read_pkt(common, skb->data, 0);
			if (status) {
				rsi_dbg(ERR_ZONE, "%s: Failed To read data",
					__func__);
				break;
			}
			dev_kfree_skb(skb);
		}
	} while (1);

out:
	rsi_dbg(INFO_ZONE, "%s: Terminated thread\n", __func__);
	skb_queue_purge(&dev->rx_q);
	kthread_complete_and_exit(&dev->rx_thread.completion, 0);
}

Annotation

• Immediate include surface: `linux/firmware.h`, `rsi_usb.h`.
• Detected declarations: `function Copyright`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: source 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.