include/acpi/acrestyp.h
Source file repositories/reference/linux-study-clean/include/acpi/acrestyp.h
File Facts
- System
- Linux kernel
- Corpus path
include/acpi/acrestyp.h- Extension
.h- Size
- 19981 bytes
- Lines
- 710
- Domain
- Repository Root And Misc
- Bucket
- include
- Inferred role
- Repository Root And Misc: implementation source
- Status
- source implementation candidate
Why This File Exists
Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.
- Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.
- 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 acpi_uuidstruct acpi_vendor_uuidstruct acpi_resource_irqstruct acpi_resource_dmastruct acpi_resource_start_dependentstruct acpi_resource_iostruct acpi_resource_fixed_iostruct acpi_resource_fixed_dmastruct acpi_resource_vendorstruct acpi_resource_vendor_typedstruct acpi_resource_end_tagstruct acpi_resource_memory24struct acpi_resource_memory32struct acpi_resource_fixed_memory32struct acpi_memory_attributestruct acpi_io_attributestruct acpi_resource_labelstruct acpi_resource_sourcestruct acpi_address16_attributestruct acpi_address32_attributestruct acpi_address64_attributestruct acpi_resource_addressstruct acpi_resource_address16struct acpi_resource_address32struct acpi_resource_address64struct acpi_resource_extended_address64struct acpi_resource_extended_irqstruct acpi_resource_generic_registerstruct acpi_resource_gpiostruct acpi_resource_common_serialbusstruct acpi_resource_i2c_serialbusstruct acpi_resource_spi_serialbusstruct acpi_resource_uart_serialbusstruct acpi_resource_csi2_serialbusstruct acpi_resource_pin_functionstruct acpi_resource_pin_configstruct acpi_resource_clock_inputstruct acpi_resource_pin_groupstruct acpi_resource_pin_group_functionstruct acpi_resource_pin_group_configstruct acpi_resourcestruct acpi_pci_routing_table
Annotated Snippet
struct acpi_uuid {
u8 data[ACPI_UUID_LENGTH];
};
struct acpi_vendor_uuid {
u8 subtype;
u8 data[ACPI_UUID_LENGTH];
};
/*
* Structures used to describe device resources
*/
struct acpi_resource_irq {
u8 descriptor_length;
u8 triggering;
u8 polarity;
u8 shareable;
u8 wake_capable;
u8 interrupt_count;
union {
u8 interrupt;
ACPI_FLEX_ARRAY(u8, interrupts);
};
};
struct acpi_resource_dma {
u8 type;
u8 bus_master;
u8 transfer;
u8 channel_count;
union {
u8 channel;
ACPI_FLEX_ARRAY(u8, channels);
};
};
struct acpi_resource_start_dependent {
u8 descriptor_length;
u8 compatibility_priority;
u8 performance_robustness;
};
/*
* The END_DEPENDENT_FUNCTIONS_RESOURCE struct is not
* needed because it has no fields
*/
struct acpi_resource_io {
u8 io_decode;
u8 alignment;
u8 address_length;
u16 minimum;
u16 maximum;
};
struct acpi_resource_fixed_io {
u16 address;
u8 address_length;
};
struct acpi_resource_fixed_dma {
u16 request_lines;
u16 channels;
u8 width;
};
/* Values for Width field above */
#define ACPI_DMA_WIDTH8 0
#define ACPI_DMA_WIDTH16 1
#define ACPI_DMA_WIDTH32 2
#define ACPI_DMA_WIDTH64 3
#define ACPI_DMA_WIDTH128 4
#define ACPI_DMA_WIDTH256 5
struct acpi_resource_vendor {
u16 byte_length;
u8 byte_data[];
};
/* Vendor resource with UUID info (introduced in ACPI 3.0) */
struct acpi_resource_vendor_typed {
u16 byte_length;
u8 uuid_subtype;
u8 uuid[ACPI_UUID_LENGTH];
u8 byte_data[];
};
struct acpi_resource_end_tag {
Annotation
- Detected declarations: `struct acpi_uuid`, `struct acpi_vendor_uuid`, `struct acpi_resource_irq`, `struct acpi_resource_dma`, `struct acpi_resource_start_dependent`, `struct acpi_resource_io`, `struct acpi_resource_fixed_io`, `struct acpi_resource_fixed_dma`, `struct acpi_resource_vendor`, `struct acpi_resource_vendor_typed`.
- Atlas domain: Repository Root And Misc / include.
- 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.