drivers/of/unittest-data/testcases.dtso
Source file repositories/reference/linux-study-clean/drivers/of/unittest-data/testcases.dtso
File Facts
- System
- Linux kernel
- Corpus path
drivers/of/unittest-data/testcases.dtso- Extension
.dtso- Size
- 468 bytes
- Lines
- 22
- Domain
- Driver Families
- Bucket
- drivers/of
- Inferred role
- Driver Families: drivers/of
- Status
- atlas-only
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.
Dependency Surface
testcases_common.dtsi
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
/dts-v1/;
/plugin/;
#include "testcases_common.dtsi"
/ {
/*
* testcase data that intentionally results in an error is located here
* instead of in testcases_common.dtsi so that the static overlay apply
* tests will not include the error.
*/
testcase-data {
testcase-device2 {
compatible = "testcase-device";
interrupt-parent = <&test_intc2>;
interrupts = <1>; /* invalid specifier - too short */
};
};
};
Annotation
- Immediate include surface: `testcases_common.dtsi`.
- Atlas domain: Driver Families / drivers/of.
- Implementation status: atlas-only.
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.