aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDouglas Anderson <dianders@chromium.org>2022-01-11 14:05:21 -0800
committerLinus Walleij <linus.walleij@linaro.org>2022-01-24 01:12:54 +0100
commit768f8d8e45f9d09aa28c9ea7c3caf86ece66ea22 (patch)
tree9549d41ad251295b1ec758744debd7429179ab36
parentdrivers/pinctrl: remove redundant ret variable (diff)
downloadlinux-dev-768f8d8e45f9d09aa28c9ea7c3caf86ece66ea22.tar.xz
linux-dev-768f8d8e45f9d09aa28c9ea7c3caf86ece66ea22.zip
dt-bindings: pinctrl: drive-strength doesn't default to 2 if unspecified
If the drive-strength isn't specified in the device tree then it doesn't actually default to 2. Instead, it defaults to whatever the heck the BIOS left it at. If the BIOS doesn't touch it then that means it's whatever the heck the initial state of the pin was when the SoC booted. Reported-by: Matthias Kaehlcke <mka@chromium.org> Signed-off-by: Douglas Anderson <dianders@chromium.org> Reviewed-by: Matthias Kaehlcke <mka@chromium.org> Reviewed-by: Stephen Boyd <swboyd@chromium.org> Link: https://lore.kernel.org/r/20220111140519.1.Ie2662d6289af1e9758b14b37149703c846d5f509@changeid Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
-rw-r--r--Documentation/devicetree/bindings/pinctrl/qcom,tlmm-common.yaml1
1 files changed, 0 insertions, 1 deletions
diff --git a/Documentation/devicetree/bindings/pinctrl/qcom,tlmm-common.yaml b/Documentation/devicetree/bindings/pinctrl/qcom,tlmm-common.yaml
index be8cb0ead62f..780f15bb5e40 100644
--- a/Documentation/devicetree/bindings/pinctrl/qcom,tlmm-common.yaml
+++ b/Documentation/devicetree/bindings/pinctrl/qcom,tlmm-common.yaml
@@ -73,7 +73,6 @@ $defs:
properties:
drive-strength:
enum: [2, 4, 6, 8, 10, 12, 14, 16]
- default: 2
description:
Selects the drive strength for the specified pins, in mA.