aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDavid Phillips <david@yeah.nah.nz>2021-05-16 19:56:55 +1200
committerDavid Phillips <david@yeah.nah.nz>2021-05-16 19:56:55 +1200
commit5ff1c42c83849fc69c8d5bad13c6c7dc1e02a481 (patch)
tree55df5e1412f56f415609cf9e4b235d3355fc66a8
parent42363803ecb23892f4aab06827e26f5f0785ba77 (diff)
downloadcds9k-5ff1c42c83849fc69c8d5bad13c6c7dc1e02a481.tar.xz
Document DT binding for simple-reset-consumer
-rw-r--r--README.md10
1 files changed, 9 insertions, 1 deletions
diff --git a/README.md b/README.md
index 3da1264..51341f3 100644
--- a/README.md
+++ b/README.md
@@ -37,7 +37,15 @@ reset. This is the quickest way I had for hackily debugging the effect of a
reset driver such as cds9k-reset, as there doesn't appear to be any sysfs or
debugfs nodes exposed for reset controllers in general.
-Usage:
+If you include a segment in your device tree like:
+
+ some_reset_consumer {
+ compatible = "david,simple-reset-consumer";
+ resets = <&some_reset>;
+ status = "okay";
+ };
+
+Then firing the resets looks like:
root@de10-nano:~# rmmod simple-reset-consumer
root@de10-nano:~# modprobe simple-reset-consumer