Documentation/devicetree/bindings/soc/cix/cix,sky1-system-control.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/soc/cix/cix,sky1-system-control.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/soc/cix/cix,sky1-system-control.yaml- Extension
.yaml- Size
- 865 bytes
- Lines
- 43
- Domain
- Support Tooling And Documentation
- Bucket
- Documentation
- 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/soc/cix/cix,sky1-system-control.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: Cix Sky1 SoC system control register region
maintainers:
- Gary Yang <gary.yang@cixtech.com>
description:
An wide assortment of registers of the system controller on Sky1 SoC,
including resets, usb, wakeup sources and so on.
properties:
compatible:
items:
- enum:
- cix,sky1-system-control
- cix,sky1-s5-system-control
- const: syscon
reg:
maxItems: 1
'#reset-cells':
const: 1
required:
- compatible
- reg
additionalProperties: false
examples:
- |
syscon@4160000 {
compatible = "cix,sky1-system-control", "syscon";
reg = <0x4160000 0x100>;
#reset-cells = <1>;
};
Annotation
- Atlas domain: Support Tooling And Documentation / Documentation.
- 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.