Based on kernel version 6.11
. Page generated on 2024-09-24 08:21 EST
.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 | # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) %YAML 1.2 --- $id: http://devicetree.org/schemas/watchdog/starfive,jh7100-wdt.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# title: StarFive Watchdog for JH7100 and JH7110 SoC maintainers: - Xingyu Wu <xingyu.wu@starfivetech.com> - Samin Guo <samin.guo@starfivetech.com> description: The JH7100 and JH7110 watchdog both are 32 bit counters. JH7100 watchdog has only one timeout phase and reboots. And JH7110 watchdog has two timeout phases. At the first phase, the signal of watchdog interrupt output(WDOGINT) will rise when counter is 0. The counter will reload the timeout value. And then, if counter decreases to 0 again and WDOGINT isn't cleared, the watchdog will reset the system unless the watchdog reset is disabled. properties: compatible: oneOf: - enum: - starfive,jh7100-wdt - starfive,jh7110-wdt - items: - enum: - starfive,jh8100-wdt - const: starfive,jh7110-wdt reg: maxItems: 1 interrupts: maxItems: 1 clocks: items: - description: APB clock - description: Core clock clock-names: items: - const: apb - const: core resets: minItems: 1 maxItems: 2 required: - compatible - reg - clocks - clock-names - resets allOf: - $ref: watchdog.yaml# - if: properties: compatible: contains: enum: - starfive,jh8100-wdt then: properties: resets: items: - description: Core reset else: properties: resets: items: - description: APB reset - description: Core reset unevaluatedProperties: false examples: - | watchdog@12480000 { compatible = "starfive,jh7100-wdt"; reg = <0x12480000 0x10000>; clocks = <&clk 171>, <&clk 172>; clock-names = "apb", "core"; resets = <&rst 99>, <&rst 100>; }; |