From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: [PATCH 05/10] arm64: dts: qcom: sc8280xp: remove superfluous "input-enable"
Date: Fri, 7 Apr 2023 19:58:02 +0200 [thread overview]
Message-ID: <20230407175807.124394-5-krzysztof.kozlowski@linaro.org> (raw)
In-Reply-To: <20230407175807.124394-1-krzysztof.kozlowski@linaro.org>
Pin configuration property "input-enable" was used with the intention to
disable the output, but this is done by default by Linux drivers. Since
patch ("dt-bindings: pinctrl: qcom: tlmm should use output-disable, not
input-enable") the property is not accepted anymore.
Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
---
arch/arm64/boot/dts/qcom/sc8280xp.dtsi | 4 ----
1 file changed, 4 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/sc8280xp.dtsi b/arch/arm64/boot/dts/qcom/sc8280xp.dtsi
index 4c75da1bac2d..5632c3b8e416 100644
--- a/arch/arm64/boot/dts/qcom/sc8280xp.dtsi
+++ b/arch/arm64/boot/dts/qcom/sc8280xp.dtsi
@@ -2728,7 +2728,6 @@ data-pins {
pins = "gpio7";
function = "dmic1_data";
drive-strength = <8>;
- input-enable;
};
};
@@ -2746,7 +2745,6 @@ data-pins {
function = "dmic1_data";
drive-strength = <2>;
bias-pull-down;
- input-enable;
};
};
@@ -2762,7 +2760,6 @@ data-pins {
pins = "gpio9";
function = "dmic2_data";
drive-strength = <8>;
- input-enable;
};
};
@@ -2780,7 +2777,6 @@ data-pins {
function = "dmic2_data";
drive-strength = <2>;
bias-pull-down;
- input-enable;
};
};
--
2.34.1
next prev parent reply other threads:[~2023-04-07 17:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 17:57 [PATCH 01/10] arm64: dts: qcom: msm8994: remove superfluous "input-enable" Krzysztof Kozlowski
2023-04-07 17:57 ` [PATCH 02/10] arm64: dts: qcom: msm8996: " Krzysztof Kozlowski
2023-04-07 17:58 ` [PATCH 03/10] arm64: dts: qcom: msm8998: " Krzysztof Kozlowski
2023-04-07 17:58 ` [PATCH 04/10] arm64: dts: qcom: qcs404: " Krzysztof Kozlowski
2023-04-07 17:58 ` Krzysztof Kozlowski [this message]
2023-04-11 14:12 ` [PATCH 05/10] arm64: dts: qcom: sc8280xp: " Johan Hovold
2023-04-11 17:07 ` Krzysztof Kozlowski
2023-04-07 17:58 ` [PATCH 06/10] arm64: dts: qcom: sdm845: " Krzysztof Kozlowski
2023-04-07 17:58 ` [PATCH 07/10] arm64: dts: qcom: sm6125: " Krzysztof Kozlowski
2023-04-07 17:58 ` [PATCH 08/10] arm64: dts: qcom: sm6350: " Krzysztof Kozlowski
2023-04-07 17:58 ` [PATCH 09/10] arm64: dts: qcom: sm8250: " Krzysztof Kozlowski
2023-04-07 17:58 ` [PATCH 10/10] arm64: dts: qcom: sm8450: " Krzysztof Kozlowski
2023-04-07 18:51 ` (subset) [PATCH 01/10] arm64: dts: qcom: msm8994: " Bjorn Andersson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230407175807.124394-5-krzysztof.kozlowski@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).