While a ripple counter can not usually be interfaced with (directly) from software, it may still be a crucial component in a board layout. To prevent its input clock from being disabled by the clock core because it apparently has no consumer, one needs to be able to represent that consumer in DT. Signed-off-by: Rasmus Villemoes <linux@xxxxxxxxxxxxxxxxxx> --- Documentation/devicetree/bindings/misc/ripple-ctr.txt | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 Documentation/devicetree/bindings/misc/ripple-ctr.txt diff --git a/Documentation/devicetree/bindings/misc/ripple-ctr.txt b/Documentation/devicetree/bindings/misc/ripple-ctr.txt new file mode 100644 index 000000000000..1497d3a237a7 --- /dev/null +++ b/Documentation/devicetree/bindings/misc/ripple-ctr.txt @@ -0,0 +1,8 @@ +Generic ripple counter + +A ripple counter is a simple component that can for example be used to +delay propagation of a signal. + +Required properties: +- compatible: Must be "linux,ripple-ctr". +- clocks: Input clock specifier. Refer to common clock bindings. -- 2.29.2
