scripts/dtc/dt-style-selftest/good/yaml-tricky-parsing.yaml
Source file repositories/reference/linux-study-clean/scripts/dtc/dt-style-selftest/good/yaml-tricky-parsing.yaml
File Facts
- System
- Linux kernel
- Corpus path
scripts/dtc/dt-style-selftest/good/yaml-tricky-parsing.yaml- Extension
.yaml- Size
- 1384 bytes
- Lines
- 58
- Domain
- Support Tooling And Documentation
- Bucket
- scripts
- Inferred role
- Support Tooling And Documentation: configuration, schema, or hardware description
- Status
- atlas-only
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
%YAML 1.2
---
$id: http://devicetree.org/schemas/test-good-tricky-parsing.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: Test fixture exercising parser corner cases
description: |
Covers patterns that previously broke the classifier:
- "/* ... */ code;" with code following the closing of a one-line
block comment must still parse the code.
- a label on a node whose name starts with a digit (1wire@10).
- a multi-line C preprocessor macro using backslash continuations
must not be parsed as DTS lines.
- a /* comment that opens and closes on the same code line must
not leave the parser in block-comment state.
maintainers:
- Test User <test@example.com>
properties:
compatible:
const: example,test-tricky-parsing
reg:
maxItems: 1
required:
- compatible
- reg
additionalProperties: false
examples:
- |
#define MY_REG(a, b) \
((a) << 16 | \
(b) << 0)
one_wire: 1wire@10 {
compatible = "example,test-tricky-parsing";
reg = <MY_REG(0x10, 0)>;
/* inline-closed */ status = "okay";
};
other: device@20 {
compatible = "example,test-tricky-parsing";
reg = <0x20 0x10>;
};
&one_wire {
status = "okay";
};
&other {
status = "okay";
};
Annotation
- Atlas domain: Support Tooling And Documentation / scripts.
- 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.