drivers/i2c/busses/i2c-mchp-pci1xxxx.c

File Facts

System

Linux kernel

Corpus path

drivers/i2c/busses/i2c-mchp-pci1xxxx.c

Extension

.c

Size

33780 bytes

Lines

1213

Domain

Driver Families

Bucket

drivers/i2c

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/bits.h
• linux/delay.h
• linux/i2c.h
• linux/i2c-smbus.h
• linux/interrupt.h
• linux/kernel.h
• linux/module.h
• linux/pci.h
• linux/types.h

Detected Declarations

• struct pci1xxxx_i2c
• function set_sys_lock
• function release_sys_lock
• function pci1xxxx_ack_high_level_intr
• function pci1xxxx_i2c_configure_smbalert_pin
• function pci1xxxx_i2c_send_start_stop
• function pci1xxxx_i2c_set_clear_FW_ACK
• function pci1xxxx_i2c_buffer_write
• function pci1xxxx_i2c_enable_ESO
• function pci1xxxx_i2c_reset_counters
• function pci1xxxx_i2c_set_transfer_dir
• function pci1xxxx_i2c_set_mcu_count
• function pci1xxxx_i2c_set_read_count
• function pci1xxxx_i2c_set_write_count
• function pci1xxxx_i2c_set_DMA_run
• function pci1xxxx_i2c_set_mrun_proceed
• function pci1xxxx_i2c_start_DMA
• function pci1xxxx_i2c_config_asr
• function pci1xxxx_i2c_isr
• function pci1xxxx_i2c_set_count
• function pci1xxxx_i2c_set_readm
• function pci1xxxx_ack_nw_layer_intr
• function pci1xxxx_config_nw_layer_intr
• function pci1xxxx_i2c_config_padctrl
• function pci1xxxx_i2c_set_mode
• function pci1xxxx_i2c_config_high_level_intr
• function pci1xxxx_i2c_configure_core_reg
• function pci1xxxx_i2c_set_freq
• function pci1xxxx_i2c_init
• function pci1xxxx_i2c_clear_flags
• function pci1xxxx_i2c_read
• function pci1xxxx_i2c_write
• function pci1xxxx_i2c_xfer
• function pci1xxxx_i2c_get_funcs
• function pci1xxxx_i2c_suspend
• function pci1xxxx_i2c_resume
• function pci1xxxx_i2c_shutdown
• function pci1xxxx_i2c_probe_pci

Annotated Snippet

static struct pci_driver pci1xxxx_i2c_pci_driver = {
	.name		= "i2c-mchp-pci1xxxx",
	.id_table	= pci1xxxx_i2c_pci_id_table,
	.probe		= pci1xxxx_i2c_probe_pci,
	.driver = {
		.pm = pm_sleep_ptr(&pci1xxxx_i2c_pm_ops),
	},
};
module_pci_driver(pci1xxxx_i2c_pci_driver);

MODULE_LICENSE("GPL");
MODULE_AUTHOR("Tharun Kumar P<tharunkumar.pasumarthi@microchip.com>");
MODULE_AUTHOR("Kumaravel Thiagarajan <kumaravel.thiagarajan@microchip.com>");
MODULE_DESCRIPTION("Microchip Technology Inc. pci1xxxx I2C bus driver");

Annotation

• Immediate include surface: `linux/bits.h`, `linux/delay.h`, `linux/i2c.h`, `linux/i2c-smbus.h`, `linux/interrupt.h`, `linux/kernel.h`, `linux/module.h`, `linux/pci.h`.
• Detected declarations: `struct pci1xxxx_i2c`, `function set_sys_lock`, `function release_sys_lock`, `function pci1xxxx_ack_high_level_intr`, `function pci1xxxx_i2c_configure_smbalert_pin`, `function pci1xxxx_i2c_send_start_stop`, `function pci1xxxx_i2c_set_clear_FW_ACK`, `function pci1xxxx_i2c_buffer_write`, `function pci1xxxx_i2c_enable_ESO`, `function pci1xxxx_i2c_reset_counters`.
• Atlas domain: Driver Families / drivers/i2c.
• 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.