Documentation/devicetree/bindings/watchdog/andestech,ae350-wdt.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/watchdog/andestech,ae350-wdt.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/watchdog/andestech,ae350-wdt.yaml- Extension
.yaml- Size
- 1051 bytes
- Lines
- 54
- 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/watchdog/andestech,ae350-wdt.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: Andes ATCWDT200 Watchdog Timer
maintainers:
- CL Wang <cl634@andestech.com>
allOf:
- $ref: watchdog.yaml#
properties:
compatible:
oneOf:
- items:
- enum:
- andestech,qilai-wdt
- const: andestech,ae350-wdt
- const: andestech,ae350-wdt
reg:
maxItems: 1
clocks:
maxItems: 1
andestech,clock-source:
$ref: /schemas/types.yaml#/definitions/uint32
enum: [0, 1]
description: |
Select the clock source for the watchdog timer.
0 - External clock
1 - P clock
required:
- compatible
- reg
- clocks
- andestech,clock-source
unevaluatedProperties: false
examples:
- |
watchdog@f0500000 {
compatible = "andestech,ae350-wdt";
reg = <0xf0500000 0x20>;
clocks = <&clk_wdt>;
andestech,clock-source = <0>;
};
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.