[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220111140519.1.Ie2662d6289af1e9758b14b37149703c846d5f509@changeid>
Date: Tue, 11 Jan 2022 14:05:21 -0800
From: Douglas Anderson <dianders@...omium.org>
To: Bjorn Andersson <bjorn.andersson@...aro.org>,
Linus Walleij <linus.walleij@...aro.org>,
Stephen Boyd <swboyd@...omium.org>
Cc: Matthias Kaehlcke <mka@...omium.org>,
linux-arm-msm@...r.kernel.org,
Douglas Anderson <dianders@...omium.org>,
Andy Gross <agross@...nel.org>,
Rob Herring <robh+dt@...nel.org>, devicetree@...r.kernel.org,
linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH] 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@...omium.org>
Signed-off-by: Douglas Anderson <dianders@...omium.org>
---
Documentation/devicetree/bindings/pinctrl/qcom,tlmm-common.yaml | 1 -
1 file changed, 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/pinctrl/qcom,tlmm-common.yaml b/Documentation/devicetree/bindings/pinctrl/qcom,tlmm-common.yaml
index 3b37cf102d41..dac788bc9320 100644
--- a/Documentation/devicetree/bindings/pinctrl/qcom,tlmm-common.yaml
+++ b/Documentation/devicetree/bindings/pinctrl/qcom,tlmm-common.yaml
@@ -70,7 +70,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.
--
2.34.1.575.g55b058a8bb-goog
Powered by blists - more mailing lists