drivers/mtd/nand/raw/r852.c

File Facts

System

Linux kernel

Corpus path

drivers/mtd/nand/raw/r852.c

Extension

.c

Size

25592 bytes

Lines

1095

Domain

Driver Families

Bucket

drivers/mtd

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.
• 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/kernel.h
• linux/module.h
• linux/jiffies.h
• linux/workqueue.h
• linux/interrupt.h
• linux/pci.h
• linux/pci_ids.h
• linux/delay.h
• linux/slab.h
• asm/byteorder.h
• linux/sched.h
• sm_common.h
• r852.h

Detected Declarations

• function r852_read_reg
• function r852_write_reg
• function r852_read_reg_dword
• function r852_write_reg_dword
• function r852_dma_test
• function r852_dma_enable
• function r852_dma_done
• function r852_dma_wait
• function r852_do_dma
• function r852_write_buf
• function r852_read_buf
• function r852_read_byte
• function r852_cmdctl
• function r852_wait
• function r852_ready
• function r852_ecc_hwctl
• function r852_ecc_calculate
• function r852_ecc_correct
• function r852_read_oob
• function r852_engine_enable
• function r852_engine_disable
• function r852_card_update_present
• function r852_update_card_detect
• function media_type_show
• function r852_update_media_status
• function r852_register_nand_device
• function r852_unregister_nand_device
• function r852_card_detect_work
• function r852_disable_irqs
• function r852_irq
• function r852_attach_chip
• function r852_probe
• function r852_remove
• function r852_shutdown
• function r852_suspend
• function r852_resume

Annotated Snippet

static struct pci_driver r852_pci_driver = {
	.name		= DRV_NAME,
	.id_table	= r852_pci_id_tbl,
	.probe		= r852_probe,
	.remove		= r852_remove,
	.shutdown	= r852_shutdown,
	.driver.pm	= &r852_pm_ops,
};

module_pci_driver(r852_pci_driver);

MODULE_LICENSE("GPL");
MODULE_AUTHOR("Maxim Levitsky <maximlevitsky@gmail.com>");
MODULE_DESCRIPTION("Ricoh 85xx xD/smartmedia card reader driver");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/jiffies.h`, `linux/workqueue.h`, `linux/interrupt.h`, `linux/pci.h`, `linux/pci_ids.h`, `linux/delay.h`.
• Detected declarations: `function r852_read_reg`, `function r852_write_reg`, `function r852_read_reg_dword`, `function r852_write_reg_dword`, `function r852_dma_test`, `function r852_dma_enable`, `function r852_dma_done`, `function r852_dma_wait`, `function r852_do_dma`, `function r852_write_buf`.
• Atlas domain: Driver Families / drivers/mtd.
• Implementation status: pattern 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.