include/uapi/linux/virtio_gpio.h

File Facts

System

Linux kernel

Corpus path

include/uapi/linux/virtio_gpio.h

Extension

.h

Size

1714 bytes

Lines

73

Domain

Core OS

Bucket

Core Kernel Interface

Inferred role

Core OS: implementation source

Status

source implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/types.h

Detected Declarations

• struct virtio_gpio_config
• struct virtio_gpio_request
• struct virtio_gpio_response
• struct virtio_gpio_response_get_names
• struct virtio_gpio_irq_request
• struct virtio_gpio_irq_response

Annotated Snippet

struct virtio_gpio_config {
	__le16 ngpio;
	__u8 padding[2];
	__le32 gpio_names_size;
};

/* Virtio GPIO Request / Response */
struct virtio_gpio_request {
	__le16 type;
	__le16 gpio;
	__le32 value;
};

struct virtio_gpio_response {
	__u8 status;
	__u8 value;
};

struct virtio_gpio_response_get_names {
	__u8 status;
	__u8 value[];
};

/* Virtio GPIO IRQ Request / Response */
struct virtio_gpio_irq_request {
	__le16 gpio;
};

struct virtio_gpio_irq_response {
	__u8 status;
};

/* Possible values of the interrupt status field */
#define VIRTIO_GPIO_IRQ_STATUS_INVALID		0x0
#define VIRTIO_GPIO_IRQ_STATUS_VALID		0x1

#endif /* _LINUX_VIRTIO_GPIO_H */

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct virtio_gpio_config`, `struct virtio_gpio_request`, `struct virtio_gpio_response`, `struct virtio_gpio_response_get_names`, `struct virtio_gpio_irq_request`, `struct virtio_gpio_irq_response`.
• Atlas domain: Core OS / Core Kernel Interface.
• 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.