Documentation: mfd/max77686 devicetree bindings update

This change documents the enable/disable-low-jitter
bindings for the mfd/max77686.

Signed-off-by: Will Drewry <wad@chromium.org>
TEST=none
BUG=chrome-os-partner:15785

Change-Id: I0c980d5a2fa730c8d8681041a5627d84c3f1f4bb
Reviewed-on: https://gerrit.chromium.org/gerrit/38238
Reviewed-by: Vincent Palatin <vpalatin@chromium.org>
Reviewed-by: Olof Johansson <olofj@chromium.org>
Reviewed-by: Doug Anderson <dianders@chromium.org>
Commit-Ready: Will Drewry <wad@chromium.org>
Tested-by: Will Drewry <wad@chromium.org>

diff --git a/Documentation/devicetree/bindings/mfd/max77686.txt b/Documentation/devicetree/bindings/mfd/max77686.txt
index 9d710b16629cb0f070fa92f61c37db11eae27e18..408e55f84a837d194f440ca14a44c40131cc07e5 100644 (file)
--- a/Documentation/devicetree/bindings/mfd/max77686.txt
+++ b/Documentation/devicetree/bindings/mfd/max77686.txt
@@ -28,6 +28,13 @@ Optional node:
   capabilities such as low power mode, standby mode (controlled by PWRREQ
   signal) etc. Check the regulator CTRL register for the bits setting these
   modes.
+- max77686,enable-low-jitter : If present, bit 3 of the 32KHZ register will be
+  set.  This enables low jitter mode which can offset flaky clock
+  signals during updates of the RTC.
+- max77686,disable-low-jitter : If present, bit 3 of the 32KHZ register
+  will be cleared. If both enable and disable are present, then enable
+  will be favored.  If neither are set, the register will not be modified.
+
 
 The regulator-compatible property of regulator should initialized with
 string to get matched with their hardware counterparts as follow:
@@ -45,6 +52,7 @@ Example:
                interrupts = <26 0>;
                reg = <0x09>;
                max77686,buck_ramp_delay = <1>;
+               max77686,enable-low-jitter;
 
                voltage-regulators {
                        ldo11_reg {