drivers/s390/cio/qdio_debug.h
Source file repositories/reference/linux-study-clean/drivers/s390/cio/qdio_debug.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/s390/cio/qdio_debug.h- Extension
.h- Size
- 1843 bytes
- Lines
- 74
- Domain
- Driver Families
- Bucket
- drivers/s390
- 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
asm/debug.hasm/qdio.hqdio.h
Detected Declarations
function DBF_HEXfunction DBF_ERROR_HEXfunction DBF_DEV_HEX
Annotated Snippet
if (debug_level_enabled(device->debug_area, level)) { \
snprintf(debug_buffer, QDIO_DBF_LEN, text); \
debug_text_event(device->debug_area, level, debug_buffer); \
} \
} while (0)
static inline void DBF_DEV_HEX(struct qdio_irq *dev, void *addr,
int len, int level)
{
debug_event(dev->debug_area, level, addr, len);
}
int qdio_allocate_dbf(struct qdio_irq *irq_ptr);
void qdio_setup_debug_entries(struct qdio_irq *irq_ptr);
void qdio_shutdown_debug_entries(struct qdio_irq *irq_ptr);
int qdio_debug_init(void);
void qdio_debug_exit(void);
#endif
Annotation
- Immediate include surface: `asm/debug.h`, `asm/qdio.h`, `qdio.h`.
- Detected declarations: `function DBF_HEX`, `function DBF_ERROR_HEX`, `function DBF_DEV_HEX`.
- Atlas domain: Driver Families / drivers/s390.
- 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.