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: [RFT PATCH 02/14] ARM: dts: qcom: sdx65: correct TLMM gpio-ranges
Date: Wed, 1 Feb 2023 16:50:53 +0100 [thread overview]
Message-ID: <20230201155105.282708-3-krzysztof.kozlowski@linaro.org> (raw)
In-Reply-To: <20230201155105.282708-1-krzysztof.kozlowski@linaro.org>
Correct the number of GPIOs in TLMM pin controller.
Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
---
arch/arm/boot/dts/qcom-sdx65.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/qcom-sdx65.dtsi b/arch/arm/boot/dts/qcom-sdx65.dtsi
index 619cafb6d9b3..13f98197141d 100644
--- a/arch/arm/boot/dts/qcom-sdx65.dtsi
+++ b/arch/arm/boot/dts/qcom-sdx65.dtsi
@@ -427,7 +427,7 @@ tlmm: pinctrl@f100000 {
interrupts = <GIC_SPI 212 IRQ_TYPE_LEVEL_HIGH>;
gpio-controller;
#gpio-cells = <2>;
- gpio-ranges = <&tlmm 0 0 109>;
+ gpio-ranges = <&tlmm 0 0 108>;
interrupt-controller;
interrupt-parent = <&intc>;
#interrupt-cells = <2>;
--
2.34.1
next prev parent reply other threads:[~2023-02-01 15:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 15:50 [RFT PATCH 00/14] ARM/arm64: dts: qcom: correct TLMM gpio-ranges Krzysztof Kozlowski
2023-02-01 15:50 ` [RFT PATCH 01/14] ARM: dts: qcom: sdx55: " Krzysztof Kozlowski
2023-02-01 15:50 ` Krzysztof Kozlowski [this message]
2023-02-01 15:50 ` [RFT PATCH 03/14] arm64: dts: qcom: msm8953: " Krzysztof Kozlowski
2023-02-01 15:50 ` [RFT PATCH 04/14] arm64: dts: qcom: sc7180: " Krzysztof Kozlowski
2023-02-01 15:50 ` [RFT PATCH 05/14] arm64: dts: qcom: sc8280xp: " Krzysztof Kozlowski
2023-02-02 22:58 ` Brian Masney
2023-02-02 23:45 ` Konrad Dybcio
2023-02-02 23:59 ` Brian Masney
2023-02-03 0:05 ` Konrad Dybcio
2023-02-03 0:15 ` Brian Masney
2023-02-03 7:10 ` Krzysztof Kozlowski
2023-02-01 15:50 ` [RFT PATCH 06/14] arm64: dts: qcom: sdm670: " Krzysztof Kozlowski
2023-02-01 15:50 ` [RFT PATCH 07/14] arm64: dts: qcom: sdm845: " Krzysztof Kozlowski
2023-02-01 15:50 ` [RFT PATCH 08/14] arm64: dts: qcom: sm6115: " Krzysztof Kozlowski
2023-02-01 15:51 ` [RFT PATCH 09/14] arm64: dts: qcom: sm6125: " Krzysztof Kozlowski
2023-02-01 15:51 ` [RFT PATCH 10/14] arm64: dts: qcom: sm6350: " Krzysztof Kozlowski
2023-02-01 15:51 ` [RFT PATCH 11/14] arm64: dts: qcom: sm6375: " Krzysztof Kozlowski
2023-02-01 15:51 ` [RFT PATCH 12/14] arm64: dts: qcom: sm8150: " Krzysztof Kozlowski
2023-02-01 15:51 ` [RFT PATCH 13/14] arm64: dts: qcom: sm8450: " Krzysztof Kozlowski
2023-02-01 15:51 ` [RFT PATCH 14/14] arm64: dts: qcom: sm8550: " Krzysztof Kozlowski
2023-02-02 10:39 ` [RFT PATCH 00/14] ARM/arm64: dts: qcom: " Krzysztof Kozlowski
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=20230201155105.282708-3-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).