drivers/pcmcia/yenta_socket.c

File Facts

System

Linux kernel

Corpus path

drivers/pcmcia/yenta_socket.c

Extension

.c

Size

40203 bytes

Lines

1457

Domain

Driver Families

Bucket

drivers/pcmcia

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.
• 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/init.h
• linux/pci.h
• linux/workqueue.h
• linux/interrupt.h
• linux/delay.h
• linux/module.h
• linux/io.h
• linux/slab.h
• pcmcia/ss.h
• yenta_socket.h
• i82365.h
• ti113x.h
• ricoh.h
• topic.h
• o2micro.h

Detected Declarations

• function space
• function cb_writel
• function config_readb
• function config_readw
• function config_readl
• function config_writeb
• function config_writew
• function config_writel
• function exca_readb
• function exca_readw
• function exca_writeb
• function exca_writew
• function show_yenta_registers
• function yenta_get_status
• function yenta_set_power
• function yenta_set_socket
• function yenta_set_io_map
• function yenta_set_mem_map
• function yenta_interrupt
• function yenta_interrupt_wrapper
• function yenta_clear_maps
• function yenta_interrogate
• function yenta_sock_init
• function yenta_sock_suspend
• function yenta_search_one_res
• function yenta_search_res
• function pci_bus_for_each_resource
• function yenta_allocate_res
• function yenta_free_res
• function yenta_allocate_resources
• function yenta_free_resources
• function yenta_close
• function yenta_probe_irq
• function yenta_probe_handler
• function yenta_probe_cb_irq
• function yenta_get_socket_capabilities
• function yenta_config_init
• function yenta_fixup_parent_bridge
• function yenta_probe
• function yenta_dev_suspend_noirq
• function yenta_dev_resume_noirq

Annotated Snippet

static struct pci_driver yenta_cardbus_driver = {
	.name		= "yenta_cardbus",
	.id_table	= yenta_table,
	.probe		= yenta_probe,
	.remove		= yenta_close,
	.driver.pm	= YENTA_PM_OPS,
};

module_pci_driver(yenta_cardbus_driver);

MODULE_DESCRIPTION("Driver for CardBus yenta-compatible bridges");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/init.h`, `linux/pci.h`, `linux/workqueue.h`, `linux/interrupt.h`, `linux/delay.h`, `linux/module.h`, `linux/io.h`, `linux/slab.h`.
• Detected declarations: `function space`, `function cb_writel`, `function config_readb`, `function config_readw`, `function config_readl`, `function config_writeb`, `function config_writew`, `function config_writel`, `function exca_readb`, `function exca_readw`.
• Atlas domain: Driver Families / drivers/pcmcia.
• Implementation status: pattern implementation candidate.
• 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.