arm64: dts: qcom: sdm845: Remove superfluous "input-enable"s from cheza
authorDouglas Anderson <dianders@chromium.org>
Thu, 23 Mar 2023 17:30:15 +0000 (10:30 -0700)
committerBjorn Andersson <andersson@kernel.org>
Fri, 7 Apr 2023 17:54:09 +0000 (10:54 -0700)
As talked about in the patch ("dt-bindings: pinctrl: qcom: tlmm should
use output-disable, not input-enable"), using "input-enable" in
pinctrl states for Qualcomm TLMM pinctrl devices was either
superfluous or there to disable a pin's output.

Looking at cheza
* ec_ap_int_l, h1_ap_int_odl: Superfluous. The pins will be configured
  as inputs automatically by the Linux GPIO subsystem (presumably the
  reference for other OSes using these device trees).
* bios_flash_wp_l: Superfluous. This pin is exposed to userspace
  through the kernel's GPIO API and will be configured automatically.

That means that in none of the cases for cheza did we need to change
"input-enable" to "output-disable" and we can just remove these
superfluous properties.

Signed-off-by: Douglas Anderson <dianders@chromium.org>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Bjorn Andersson <andersson@kernel.org>
Link: https://lore.kernel.org/r/20230323102605.11.Ia439c29517b1c0625325a54387b047f099d16425@changeid
arch/arm64/boot/dts/qcom/sdm845-cheza.dtsi

index 59ad6a8..e1bab53 100644 (file)
@@ -1153,14 +1153,12 @@ ap_ts_i2c: &i2c14 {
        bios_flash_wp_r_l: bios-flash-wp-r-l-state {
                pins = "gpio128";
                function = "gpio";
-               input-enable;
                bias-disable;
        };
 
        ec_ap_int_l: ec-ap-int-l-state {
               pins = "gpio122";
               function = "gpio";
-              input-enable;
               bias-pull-up;
        };
 
@@ -1188,7 +1186,6 @@ ap_ts_i2c: &i2c14 {
        h1_ap_int_odl: h1-ap-int-odl-state {
                pins = "gpio129";
                function = "gpio";
-               input-enable;
                bias-pull-up;
        };