drivers/gpio/gpiolib-sysfs.h

File Facts

System

Linux kernel

Corpus path

drivers/gpio/gpiolib-sysfs.h

Extension

.h

Size

462 bytes

Lines

27

Domain

Driver Families

Bucket

drivers/gpio

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• struct gpio_device
• function gpiochip_sysfs_register
• function gpiochip_sysfs_unregister

Annotated Snippet

#ifndef GPIOLIB_SYSFS_H
#define GPIOLIB_SYSFS_H

struct gpio_device;

#ifdef CONFIG_GPIO_SYSFS

int gpiochip_sysfs_register(struct gpio_chip *gc);
void gpiochip_sysfs_unregister(struct gpio_chip *gc);

#else

static inline int gpiochip_sysfs_register(struct gpio_chip *gc)
{
	return 0;
}

static inline void gpiochip_sysfs_unregister(struct gpio_chip *gc)
{
}

#endif /* CONFIG_GPIO_SYSFS */

#endif /* GPIOLIB_SYSFS_H */

Annotation

• Detected declarations: `struct gpio_device`, `function gpiochip_sysfs_register`, `function gpiochip_sysfs_unregister`.
• Atlas domain: Driver Families / drivers/gpio.
• Implementation status: source 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.