drivers/gpio/gpio-tps6586x.c
Source file repositories/reference/linux-study-clean/drivers/gpio/gpio-tps6586x.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpio/gpio-tps6586x.c- Extension
.c- Size
- 3245 bytes
- Lines
- 124
- Domain
- Driver Families
- Bucket
- drivers/gpio
- Inferred role
- Driver Families: exported/initcall integration point
- Status
- integration 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.
- Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
- 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/errno.hlinux/gpio/driver.hlinux/kernel.hlinux/init.hlinux/mfd/tps6586x.hlinux/of.hlinux/platform_device.h
Detected Declarations
struct tps6586x_gpiofunction tps6586x_gpio_getfunction tps6586x_gpio_setfunction tps6586x_gpio_outputfunction tps6586x_gpio_to_irqfunction tps6586x_gpio_probefunction tps6586x_gpio_initmodule init tps6586x_gpio_init
Annotated Snippet
subsys_initcall(tps6586x_gpio_init);Annotation
- Immediate include surface: `linux/errno.h`, `linux/gpio/driver.h`, `linux/kernel.h`, `linux/init.h`, `linux/mfd/tps6586x.h`, `linux/of.h`, `linux/platform_device.h`.
- Detected declarations: `struct tps6586x_gpio`, `function tps6586x_gpio_get`, `function tps6586x_gpio_set`, `function tps6586x_gpio_output`, `function tps6586x_gpio_to_irq`, `function tps6586x_gpio_probe`, `function tps6586x_gpio_init`, `module init tps6586x_gpio_init`.
- Atlas domain: Driver Families / drivers/gpio.
- Implementation status: integration implementation candidate.
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.